Bug 691332

Summary: USB HDD cannot be automatically mounted after kernel update to 2.6.37.6-0.5-desktop x86_64
Product: [openSUSE] openSUSE 11.4 Reporter: Angelos Skembris <a.skembris>
Component: BasesystemAssignee: Kay Sievers <kasievers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P2 - High CC: forgotten_--EoyBps8f, forgotten_xnWyJO8MVA, hernan.grecco, iceman, Martin.Seidler, puzel
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.4   
See Also: https://bugs.kde.org/show_bug.cgi?id=270689
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Angelos Skembris 2011-05-03 02:17:13 UTC
User-Agent:       Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.8.131 Version/11.10

The device notifier reports an error when
trying to mount my external ntfs drive:

org.freedesktop.UDisks.Error.Failed: Requested filesystem type is neither
well-known nor in /proc/filesystems nor in /etc/filesystems

The drive worked fine before the update to kernel 2.6.37.6-0.5-desktop x86_64.


Reproducible: Always

Steps to Reproduce:
1.Insert a NTFS USB drive
2.
3.
Actual Results:  
Device is not mounted.

Expected Results:  
Device should be mounted and accessible through dolphin or other file browsers.

Adding "ntfs" to /etc/filesystems seems to fix the problem. This bug is also reported in KDE's bugzilla: https://bugs.kde.org/show_bug.cgi?id=270689
Comment 1 Martin Seidler 2011-05-03 09:55:20 UTC
See also

- on the forums:
* (de) Thread: kein Zugriff mehr auf NTFS-Partition (30-Apr-2011)
http://forums.opensuse.org/deutsch-german/hilfe-und-helfen/anwendungen/458977-kein-zugriff-mehr-auf-ntfs-partition.html
* (de) Thread: USB-Festplatte nach Update nicht zu öffnen (30-Apr-2011)
http://forums.opensuse.org/deutsch-german/hilfe-und-helfen/installation-administration/458993-usb-festplatte-nach-update-nicht-zu-oeffnen.html
* (en) Thread: Mounting ntfs formatted usb external hdd in Tumbleweed (01-May-201)
http://forums.opensuse.org/english/get-technical-help-here/tumbleweed/459088-mounting-ntfs-formatted-usb-external-hdd-tumbleweed.html

- on archlinux.org > bugs:
* FS#23701 - [udisks] udisks 1.0.3 fails to mount ntfs drive with kde (11 April 2011)
https://bugs.archlinux.org/task/23701
Comment 2 Tim Edwards 2011-05-03 21:14:24 UTC
I've seen the problem on my laptop after the update to the kernel contained in the package kernel-desktop-2.6.37.6-0.5.1.x86_64

The workaround of adding ntfs to /etc/filesystems worked, but the bug needs to be fixed. Not being able to mount NTFS drives (which most external USB are these days) is a big issue, and command-line workarounds are no good for non-technical users.
Comment 3 Forgotten User --EoyBps8f 2011-05-11 15:42:43 UTC
I see the same, it's a regression caused by an official kernel update and users should not be expected to edit /etc/filesystems.
Comment 4 Greg Kroah-Hartman 2011-05-11 15:48:10 UTC
/etc/filessystems comes from the util-linux package, not the kernel package, reassigning.
Comment 5 Martin Seidler 2011-05-12 12:57:01 UTC
See also:
Bug 691280 - USB hard disk formatted as NTFS is being mounted as FAT by KDE (and of course fails) in Tumbleweed
(Probably just the same issue in a bug report against openSUSE Tumbleweed instead of openSUSE 11.4)
Comment 6 Petr Uzel 2011-05-12 14:56:04 UTC
*** Bug 691280 has been marked as a duplicate of this bug. ***
Comment 7 Petr Uzel 2011-05-12 15:19:46 UTC
Hm, I can not reproduce. However, I'm quite convinced that this relates to the recent update of udisks.

Kay, there is missing comma after "exfat" and before "ntfs" in the patch that fixes bnc#653900. Assigning to you.
Comment 8 Stefan Willer 2011-05-13 19:40:39 UTC
Downgrading udisks fixes the problem for me. Could somebody take down that udisks update please, so it is not offered again and again?
Comment 9 Kay Sievers 2011-05-14 18:18:38 UTC
merge duplicate

*** This bug has been marked as a duplicate of bug 691077 ***
Comment 10 Christian Trippe 2011-06-12 16:48:30 UTC
*** Bug 699463 has been marked as a duplicate of this bug. ***