| Summary: | Some USB drives can't be mounted after udisks update 2.0.1 → 2.1.0 | ||
|---|---|---|---|
| Product: | udisks | Reporter: | senjin |
| Component: | detection | Assignee: | David Zeuthen (not reading bugmail) <zeuthen> |
| Status: | RESOLVED NOTOURBUG | QA Contact: | |
| Severity: | major | ||
| Priority: | medium | CC: | bugs, senjin |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
bad_dmesg
bad_fstab bad_gvfs-mount bad_gvfs_mount_oi bad_mountinfo bad_udevadm_info_export_db bad_udevadm_monitor_udev_property bad_udisksctl_dump bad_udisksctl_monitor bad_versions good_dmesg good_fstab good_gvfs-mount good_gvfs_mount_oi good_mountinfo good_udevadm_info_export_db good_udevadm_monitor_udev_property good_udisksctl_dump good_udisksctl_monitor good_versions |
||
Created attachment 80845 [details]
bad_fstab
Created attachment 80846 [details]
bad_gvfs-mount
Created attachment 80847 [details]
bad_gvfs_mount_oi
Created attachment 80848 [details]
bad_mountinfo
Created attachment 80849 [details]
bad_udevadm_info_export_db
Created attachment 80850 [details]
bad_udevadm_monitor_udev_property
Created attachment 80851 [details]
bad_udisksctl_dump
Created attachment 80852 [details]
bad_udisksctl_monitor
Created attachment 80853 [details]
bad_versions
Created attachment 80854 [details]
good_dmesg
Created attachment 80855 [details]
good_fstab
Created attachment 80856 [details]
good_gvfs-mount
Created attachment 80857 [details]
good_gvfs_mount_oi
Created attachment 80858 [details]
good_mountinfo
Created attachment 80859 [details]
good_udevadm_info_export_db
Created attachment 80860 [details]
good_udevadm_monitor_udev_property
Created attachment 80861 [details]
good_udisksctl_dump
Created attachment 80862 [details]
good_udisksctl_monitor
Created attachment 80863 [details]
good_versions
I attached the required logs in two versions. "good" stands for the old, working udisks2, and "bad" for the new version which causes problems. Perhaps some more info can be found here: https://bugs.archlinux.org/task/35445 https://bbs.archlinux.org/viewtopic.php?pid=1272681#p1272681 Similar issue in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=983813 In particular, the following comment gives further information: > OK, after googling a bit, this error appears for many users, on many > distributions. One common factor is the SATA bridge in use: > > Jul 12 10:22:40 dwsav.b-elab.com kernel: usb 2-1.8: Product: USB 2.0 SATA > BRIDGE > Jul 12 10:22:40 dwsav.b-elab.com kernel: usb 2-1.8: Manufacturer: Super Top > > Jul 12 10:22:40 dwsav.b-elab.com kernel: usb 2-1.8: SerialNumber: > M6116018VF16 > > Directly plugging the drive into the host SATA ports, and all is well. Doesn't seem to be an udisks problem (seems to be a kernel problem). Closing. I don't understand, why do you believe it's kernel problem, if it occurs only with udisks. And if you have strong reasons to think that it's kernel problem, could you list them, so a kernel bug can be reported? The problem is still present with kernel 3.10.10 and udisks 2.1.0. (now I realise there is 2.1.1 version released but it's still not updated in Archlinux) |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 80844 [details] bad_dmesg One of my USB drives (this is a 2.5" disk in a USB enclosure) can no longer be mounted from DM, after I udated udisks 2.0.1 → 2.1.0. I can mount the drive normally if I start the system in the text mode with 'mount', but if I start DM (tested with xfce and kde) it is no longer possible. Icon of the drive does not appear on the desktop, and it's even impossible to 'mount' it from the command line. Tested both at i686 and x86-64 (logs produced on the latter). The drive is fine, works after downgrading udisks (and gvfs).