Bug 65785

Summary: Some USB drives can't be mounted after udisks update 2.0.1 → 2.1.0
Product: udisks Reporter: senjin
Component: detectionAssignee: 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

Description senjin 2013-06-15 10:44:47 UTC
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).
Comment 1 senjin 2013-06-15 10:45:22 UTC
Created attachment 80845 [details]
bad_fstab
Comment 2 senjin 2013-06-15 10:46:00 UTC
Created attachment 80846 [details]
bad_gvfs-mount
Comment 3 senjin 2013-06-15 10:46:22 UTC
Created attachment 80847 [details]
bad_gvfs_mount_oi
Comment 4 senjin 2013-06-15 10:46:41 UTC
Created attachment 80848 [details]
bad_mountinfo
Comment 5 senjin 2013-06-15 10:47:10 UTC
Created attachment 80849 [details]
bad_udevadm_info_export_db
Comment 6 senjin 2013-06-15 10:47:35 UTC
Created attachment 80850 [details]
bad_udevadm_monitor_udev_property
Comment 7 senjin 2013-06-15 10:48:00 UTC
Created attachment 80851 [details]
bad_udisksctl_dump
Comment 8 senjin 2013-06-15 10:48:19 UTC
Created attachment 80852 [details]
bad_udisksctl_monitor
Comment 9 senjin 2013-06-15 10:48:40 UTC
Created attachment 80853 [details]
bad_versions
Comment 10 senjin 2013-06-15 10:49:32 UTC
Created attachment 80854 [details]
good_dmesg
Comment 11 senjin 2013-06-15 10:49:50 UTC
Created attachment 80855 [details]
good_fstab
Comment 12 senjin 2013-06-15 10:50:09 UTC
Created attachment 80856 [details]
good_gvfs-mount
Comment 13 senjin 2013-06-15 10:50:35 UTC
Created attachment 80857 [details]
good_gvfs_mount_oi
Comment 14 senjin 2013-06-15 10:51:03 UTC
Created attachment 80858 [details]
good_mountinfo
Comment 15 senjin 2013-06-15 10:52:35 UTC
Created attachment 80859 [details]
good_udevadm_info_export_db
Comment 16 senjin 2013-06-15 10:53:06 UTC
Created attachment 80860 [details]
good_udevadm_monitor_udev_property
Comment 17 senjin 2013-06-15 10:53:28 UTC
Created attachment 80861 [details]
good_udisksctl_dump
Comment 18 senjin 2013-06-15 10:53:51 UTC
Created attachment 80862 [details]
good_udisksctl_monitor
Comment 19 senjin 2013-06-15 10:54:14 UTC
Created attachment 80863 [details]
good_versions
Comment 20 senjin 2013-06-15 10:55:49 UTC
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
Comment 21 Tomas Bzatek 2013-07-25 09:23:20 UTC
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.
Comment 22 David Zeuthen (not reading bugmail) 2013-07-25 16:35:41 UTC
Doesn't seem to be an udisks problem (seems to be a kernel problem). Closing.
Comment 23 senjin 2013-09-12 20:03:48 UTC
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.