Feisty Fawn: ntfs-3g ceased to work after software update

Bug #120643 reported by val.kotlarov.hoffman
36
Affects Status Importance Assigned to Milestone
ntfs-config (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After last update,

hda1 has changed to sda1, and became unvisible in Gnome Commander, Nautilus (Places) etc.

The solution given in this thread - http://ubuntuforums.org/showthread.php?p=2852364#post2852364

was:

Move the ntfs-3g lines in the fstab to the end of the file. Ntfs-config inserted them into the wrong place. This bug is fixed in the latest ntfs-config release.

After reboot, problem was solved.

Revision history for this message
Szabolcs Szakacsits (szaka) wrote :

The NTFS-3G and the FUSE binaries need to be installed with ---exec-prefix=/ onto the root file system to always ensure successful automounts during boots. The "Write Support for NTFS" specification also mentions this at https://wiki.ubuntu.com/WriteSupportForNTFS

Revision history for this message
Kaptain Chaos (kaptain-chaos) wrote :
Download full text (3.3 KiB)

I have a separate /usr partition and confirm the comment by Szabolcs above.

After having scoured the forums for the past two days, I finally stumbled upon the simple solution he gives above. The default locations written into /etc/fstab seem to generally follow the partition structure of the hard drive.

My original fstab:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda9
UUID=98451ab9-d323-4a09-96a2-91b5ea58035c / ext3 defaults,errors=remount-ro 0 1
# /dev/sda3
UUID=09f8e063-64d5-4b20-a97b-26cfb7b08989 /boot ext3 defaults 0 2
# /dev/sda11
UUID=7b0fce56-2eb6-4e39-b428-4fe45eef5f21 /home ext3 defaults 0 2
# /dev/sda1
UUID=68084A9E084A6B60 /media/sda1 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sda12
UUID=28FEE8554059CE0D /media/sda12 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sda4
UUID=AA7822D77822A255 /media/sda4 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sda5
UUID=2F6501F233246281 /media/sda5 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sda6
UUID=C4E03110E0310A66 /media/sda6 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sda7
UUID=4D6F777224E88C3C /media/sda7 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sda8
UUID=2D483064170999E1 /media/sda8 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sdb2
UUID=33D844931ACC31F3 /media/sdb2 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sdb5
UUID=3B99AAAF69B58B76 /media/sdb5 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sdb6
UUID=38C6CB6F37C3CF40 /media/sdb6 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sdb7
UUID=21F8B67017160C87 /media/sdb7 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sda13
UUID=ec8a8c6e-f9fb-4af6-839e-4ed5da28cd92 /tmp ext3 defaults 0 2
# /dev/sda14
UUID=6763b394-2cd8-4830-8cb7-a4cd4b45fa41 /usr ext3 defaults 0 2
# /dev/sda15
UUID=e53c0925-18a0-415c-8786-615b3b195c8f /var ext3 defaults 0 2
# /dev/sda10
UUID=8971139c-2640-2782-0df0-7de7c429c55a none swap sw 0 0
# /dev/sdb1
UUID=582a25db-c088-427c-9279-48af84695c7b none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/scd1 /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

Installing and running the ntfs-3g configure tool simply pre-pended fstab with:

# /etc/fstab: static file system information.
#
# -- This file has been automaticly generated by ntfs-config --
#
# <file system> <mount point> <type> <options> <dump> <pass>

Everything else followed the same as above.

One other note - I did not get the pop-up 'select mount point' box with this either - possibly something to do with the fstab structure?

Once I cut and pasted the ntfs partition infor...

Read more...

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

@vhof, you say "This bug is fixed in the latest ntfs-config release.". Can you please provide a reference ? In the future please do not file bugs for issues that have been solved.

Marking incomplete until we get that reference.

Thank you.

Changed in ntfs-config:
assignee: nobody → magicfab
status: Confirmed → Incomplete
Revision history for this message
Fabián Rodríguez (magicfab) wrote :

Apparently not fixed in 7.10 - see Bug #151433 which is being marked as dupliucate of this one.

Also discussed in this forum thread:
http://forum.ntfs-3g.org/viewtopic.php?p=1574&sid=e2c543482c542f7fe83e616cc0c6f2c0

Revision history for this message
val.kotlarov.hoffman (val-hoffman) wrote :

Not fixed.
Moreover, the problem reappeared here.

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

Adam, I am subcribing you to this bug as you've worked with this package in the past.

I am cleaning up older bugs I was subscribed to, if anyone has new information about this please comment the bug. I'd suggest upgrading to a later Ubuntu release as there have been a good number of updates and fixes since this was filed, as evidenced by th echangelog:
http://changelogs.ubuntu.com/changelogs/pool/main/n/ntfs-3g/ntfs-3g_1.2506-1ubuntu2/changelog

Changed in ntfs-config:
assignee: magicfab → nobody
Revision history for this message
Connor Imes (ckimes) wrote :

Please note that this bug as a mention on https://help.ubuntu.com/community/MountingWindowsPartitions/ThirdPartyNTFS3G
I am subscribing to this bug and will update the community wiki page when appropriate.

Revision history for this message
Christopher Griffiths (chris) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in ntfs-config (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.