| Summary: | with udisks 1.0.3 device notifier won't mount external ntfs drives | ||
|---|---|---|---|
| Product: | [Unmaintained] solid | Reporter: | Victor Gavrish <loonyphoenix> |
| Component: | libsolid-udisks | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | normal | CC: | a.skembris, adam.jorgensen.za, afiestas, dener.kup, emeric, ht990332, jackpatry, mortalius, ranger.linux, stuffcorpse, wilderkde |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Victor Gavrish
2011-04-11 16:26:05 UTC
Possibly related commit: http://cgit.freedesktop.org/udisks/commit/?id=c933a929f07421ec747cebb24d5e620fc2b97037 The issue can be fixed by adding ntfs-3g to /etc/filesystems. I am also experiencing this issue. The /etc/filesystems fix worked for me. OS: Sabayon Linux KDE: 4.6.2 I just experienced this issue with a USB ntfs drive after a kernel update for OpenSUSE 11.4 (current kernel is 2.6.37.6-0.5-desktop x86_64). Adding ntfs-3g to /etc/filesystems did NOT work for me. However, adding ntfs to that file did work. Is the difference between the two drivers important? Any other workarounds? Internal HDD ntfs partitions are mounted ok, although they are registered as type ntfs-3g in fstab. mount reports all ntfs partitions (including the USB ntfs drive) as "fuseblk" (don't know if that's useful or not). ntfs-3g package is installed and manually mounting the drive using -t ntfs-3g works ok. Very confused here. Hi, System: Archlinux x64 kernel: 2.6.38-ARCH kde: 4.6.2-1 1/ Adding ntfs-3g to /etc/filesystems did not work, but mount with command "udisk --mount /dev/sdc1" in console is ok. *** This bug has been confirmed by popular vote. *** (In reply to comment #5) > Hi, > > System: Archlinux x64 > kernel: 2.6.38-ARCH > kde: 4.6.2-1 > > 1/ Adding ntfs-3g to /etc/filesystems did not work, but mount with command > "udisk --mount /dev/sdc1" in console is ok. Add ntfs to /etc/filesystems, not ntfs-3g (In reply to comment #7) > (In reply to comment #5) > > Hi, > > > > System: Archlinux x64 > > kernel: 2.6.38-ARCH > > kde: 4.6.2-1 > > > > 1/ Adding ntfs-3g to /etc/filesystems did not work, but mount with command > > "udisk --mount /dev/sdc1" in console is ok. > > Add ntfs to /etc/filesystems, not ntfs-3g I don't have a /etc/filesystems (also an Archlinux user). Do I need to create one? > I don't have a /etc/filesystems (also an Archlinux user). Do I need to create > one? Yes. > $ cat /etc/filesystems > ntfs-3g > ntfs I added ntfs-3g there too, for good measure :) cp /proc/filesystems /etc nano /etc/filesystems and add ntfs (In reply to comment #4) > I just experienced this issue with a USB ntfs drive after a kernel update for > OpenSUSE 11.4 (current kernel is 2.6.37.6-0.5-desktop x86_64). Adding ntfs-3g > to /etc/filesystems did NOT work for me. However, adding ntfs to that file did > work. Is the difference between the two drivers important? Any other > workarounds? Internal HDD ntfs partitions are mounted ok, although they are > registered as type ntfs-3g in fstab. mount reports all ntfs partitions > (including the USB ntfs drive) as "fuseblk" (don't know if that's useful or > not). > > ntfs-3g package is installed and manually mounting the drive using -t ntfs-3g > works ok. > > Very confused here. You dont add driver, you add the filesystem. (In reply to comment #11) > You dont add driver, you add the filesystem. I know you add the filesystem. What I mean is, if you add ntfs and not ntfs-3g does the system use the same driver to access ntfs partitions? If you use ntfs then it probably won't work. I'm on Sabayon and I had to use ntfs-3g. (In reply to comment #12) > (In reply to comment #11) > > > You dont add driver, you add the filesystem. > > I know you add the filesystem. What I mean is, if you add ntfs and not ntfs-3g > does the system use the same driver to access ntfs partitions? Whith Arch Linux adding ntfs-3d doesnt work, only ntfs. The problem is that this way, the device is mounted using ntfs and not ntfs-3g. But when mounting it with pmount, it uses ntfs-3g, even without adding anything in /etc/filesystems. Fixed in arch linux with this patch http://projects.archlinux.org/svntogit/packages.git/tree/udisks/repos/extra-x86_64/fix_well_known_filesystems.patch please close as DOWNSTREAM After update kernel upto 2.6.37.6-0.5-default and KDE upto V4.6.3, my openSUSE 11.4 began to reject pen-drives with ntfs with next message:
"org.freedesktop.UDisks.Error.Failed: Requested filesystem type is neither well-known nor in /proc/filesystems nor in /etc/filesystems".
I followed to advice of George T. ("Add ntfs to /etc/filesystems, not ntfs-3g") and the problem was been solved.
Today my system (OpenSUSE 11.4) get update that fix this problem. Closing as downstream as indicated. |