Bugzilla – Bug 544199
USB Drive not mounted on hotplug "unknown filesystem ntfs"
Last modified: 2016-04-15 09:56:45 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-1.3 Firefox/3.5.3 When plugging a Fujitsu-Siemens Storage Bird 500GB formatted ntfs, a message box is stating "Unable to mount FSC-500GB-T Error mounting: mount exited with exit code 32: mount: unknown filesystem type 'ntfs'" The ntfs partitions present on the built in fixed disk are mounted and accessible without problem. Trying to mount manually as root returns workstation6l:~ # mkdir /media/500gb workstation6l:~ # mount /dev/sdb1 /media/500gb mount: unknown filesystem type 'ntfs' Reproducible: Always Steps to Reproduce: 1. 2. 3.
Mounting with yast2 partitioner works.
Limited :-( Actually yast2 partitioner sets up a line in /etc/fstab for the device. /dev/disk/by-id/usb-Ext_Hard_Disk_S07F1601A00000210520-0:0-part1 /media/500GB ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0 which lets me read access, but, try what I might, not write access, except for root. Only when I change the line to /dev/disk/by-id/usb-Ext_Hard_Disk_S07F1601A00000210520-0:0-part1 /media/500GB ntfs-3g defaults can I then make full use (r/w) of the device. The locale part makes me think twice: how is this derived ? From the drive itself, or just by assuming the locale of the workstation ?
http://www.tuxera.com/community/ntfs-3g-faq/#useroption2 Why don’t the ‘user’ and ‘users’ options work in /etc/fstab? The ‘mount’ command doesn’t invoke the ntfs-3g binary with the needed privilege after it has checked and approved the user is entitled to mount a given device on a specified mount point, hereby the user can’t open the device he got the approval in /etc/fstab. This is a problem in the ‘mount’ utility. Solution: Use at least NTFS-3G 1.2506 with setuid-root set and make sure the user has access rights to the volume and mount point.
Actually #mount -t ntfs-3g /dev/sdb1 /media/500GB works nicely as well. (Information from ntfs-3g.org)
Try changing fmask to 113 instead of 133 in fstab.
Create a symlink in /sbin/ from "mount.ntfs-3g" to "mount.ntfs": # sudo ln -s -T /sbin/mount.ntfs-3g mount.ntfs For whatever reason 11.2 does not create the symlink which is needed for the desktop chain to work with ntfs properly. Perhaps someone should verify the ntfs-3g package.
(In reply to comment #6) > Create a symlink in /sbin/ from "mount.ntfs-3g" to "mount.ntfs": > > # sudo ln -s -T /sbin/mount.ntfs-3g mount.ntfs > > For whatever reason 11.2 does not create the symlink which is needed for the > desktop chain to work with ntfs properly. Perhaps someone should verify the > ntfs-3g package. The symlink is created by a post install script, which is a litle buggy, fixed in sr #23456
This is broken for me again in RC2. Can mount directly, but the hotplug desktop integration is broken again. Device entries are created in /dev/disk just fine. These can be manually mounted. Integration with desktop in Gnome now returns "unknown filesystem type ntfs"
(In reply to comment #8) > This is broken for me again in RC2. The fix for the post install script has not been checked in yet, and will appear first in GNOME:Factory.
I got the fix late yesterday and it now works fine. Thanks. This is resolved from my perspective.
This is broken in 11.2 RC2 for me too. I'm test driving the KDE 4 LiveCD Build 0339 on my system. It is installed on an enternal USB drive formatted with ext4 so that my current setup is unaffected. When I plug in an external USB drive formatted with NTFS, I get no response from KDE's device notifier, the new drive does not appear in device notifier, no dialogue box pops up and the drive does not appear in the "My Computer" konqueror screen. However, the drive does appear as /dev/sdc on connection. Creating the symlink as described in comment #7 does not remedy the situation. Automounting external media formatted with NTFS worked in 10.3 (although if memory serves, it was read-only) but it has been broken since 11.0. Please can we have this fixed by 11.2 GM? In 11.0 GM (my current setup) and in 11.2 RC2, I can still manually mount NTFS drives in the command line by doing the following: su mkdir /media/DriveName ntfs-3g /dev/sdc1 /media/DriveName I'm not a linux expert but I'm not new to it either so if you want help on this and it is something I can do, just ask, as I'd like to get involved. My System: PC: HP Compaq NX6110 CPU: Intel Celeron M 1.4 GHz RAM: 512 MiB Graphics: Intel 915 GM WiFi: Intel PRO 2200BG Lan: Broadcom BCM4401 Test OS: Linux 2.6.31.5-0.1-default i686 System: openSUSE 11.2 RC2 (i586) 32 bit KDE: 4.3.1 "release 6" Main OS: Linux 2.6.25.20-0.5-pae i686 System: openSUSE 11.0 GM (i586) 32 bit KDE: 3.5.9 "release 49.1"
Additionally, I've just been checking read/write to the NTFS partition (/windows/D/) on my system's internal drive. I can read all the files without problem, copy them across to /home/user/ but I cannot write files to the NTFS partition by drag and drop in dolphin (I get an "access denied" dialogue box). I can only write files to the NTFS partition as root from the command line. This partition was set up to be mounted at installation. Here are the fstab options the partition is mounted with are as follows: original: users,gid=users,fmask=133,dmask=022,locale=en_GB.UTF-8 modified as per comment #5 above: users,gid=users,fmask=113,dmask=022,locale=en_GB.UTF-8 Neither option allows write access as user to the NTFS partition. The check box on the YaST/partitioner/fstab options screen "Mount read-only" was not ticked when trying either option above.
http://en.opensuse.org/Bugs/Definitions#Bug_Priorities
OK, apologies for breaking bugzilla etiquette. As per comment #13, I disagree with the priority of this bug being set to "P5 - None". If all external USB storage devices were not automatically mounted on hot-plugging, I'm sure everyone would consider this a major problem. However, as this problem seems to be restricted only to storage devices using the NTFS file-system, I do not think it is any less severe. It amounts to the same thing for owners of NTFS formatted storage media. Many storage devices are supplied pre-formatted with NTFS. Many people also use microsoft operating systems in addition to linux operating systems and will have storage devices formatted with NTFS and want these devices to be inter-operable with these OSes. If this bug is not fixed prior to final release, it will prevent many non-technical users of Suse from using their computing equipment as they require. The facilities to resolve this already exist in Suse (ntfs-3g) and indeed it used to work without problem in 10.3 but has been broken since 11.0. In addition, I for one find this bug extremely annoying, it should just work. On installation, dual booters can configure their Suse system to mount any NTFS partitions in their internal drives, so it is a poor situation that they cannot auto-mount external NTFS drives. If you need any assistance with resolving this, please say and I'll be right here for you. However, I am only slightly technical, so I would know where to start in trying to resolve this myself, I'd need a hint on where to start looking but may be able to compare the code from 10.3 and 11.2 relating to this problem to see where the problem is. As per info on the link in comment #13, I'll be setting SHIP_STOPPER flag on this bug to "?" as I feel very strongly that it needs attention.
I have done some additional testing on x86_64 platforms and this only occurs under Gnome in my testing. If I logout and open Dolphin in KDE. I can mount the drive under dolphin and log back into Gnome, one can see the drives under Gnome. I am thinking this is a Gnome integration problem. I think it is a problem for people using this as a desktop. It is a regression bug.
OK, but my tests reported in comment #11 and comment #12 were on 32 bit, x86 hardware in KDE. I'll try mounting from dolphin but drives with other file systems just mount on connection, no dolphin required. Looks like this problem is not restricted to x86_64 hardware as per the platform selection of this report.
No, the solution proposed in comment #15 does not work on the test system detailed in comment #11. Therefore the hardware platform should be changed to "All" for this bug.
I can reproduce this bug too, adding the symlink to mount.ntfs doesn't fix the problem.
(In reply to comment #18) > I can reproduce this bug too, adding the symlink to mount.ntfs doesn't fix the > problem. Because the symlink issue is a different bug somewhat related bug.
I don't know if this helps (sorry i don't have time to help on this bug) but if i plug the usb hard drive right after kernel loading, it mounts and appears on GNOME. So i think this might be a GNOME problem.
This is the nautilus dialog error: Error mounting: mount exited with exit code 1: helper failed with: mount: only root can mount /dev/sdb1 on /media/Iomega_HDD
Ok, i removed the line on fstab corresponding to this media now nautilus mounts it RW fine. I'm sure it's ntfs-config fault since it was this application who added that line to fstab
Maintenance team: this is caused by a bug in packaging. This affects ntfs-3g, but also gobby04, gobby, rarian and scrollkeeper. I've put packages that should fix this in home:vuntz:11.2-testing. Can this go into the updates?
I prefer an update here. +1
+1 for updating
The SWAMPID for this issue is 29444. Please submit the patch and patchinfo file using this ID. (https://swamp.suse.de/webswamp/wf/29444)
update process started
Packages submitted, patchinfo filled => closing.
*** Bug 552567 has been marked as a duplicate of this bug. ***
This is an autogenerated message for OBS integration: This bug (544199) was mentioned in https://build.opensuse.org/request/show/26075 11.2:Test / gobby https://build.opensuse.org/request/show/26076 11.2:Test / gobby04 https://build.opensuse.org/request/show/26077 11.2:Test / ntfs-3g https://build.opensuse.org/request/show/26078 11.2:Test / rarian https://build.opensuse.org/request/show/26079 11.2:Test / scrollkeeper