HOWTO: Mount NTFS volumes with write support

[etherealbeats]

Ok thanks, I hadn't done that.

Now I am getting this error though:

paul@thumpa:~$ sudo modprobe fuse && sudo mount -a
fusermount: mount failed: Invalid argument
fuse_mount failed.
Unmounting:

It also comes up as 'failed' when i start Ubuntu up as well.

[LKRaider]

On your fstab you have a typo:

umask-0002

should be:

umask=0002

[GoBieN]

thanks, works like a charm

[stairwayoflight]

[SIZE="1"]

If you reboot now, the disk will be writable to the selected users when they logon. If you want the changes take effect imediatelly without rebooting, execute these commands and you're all set:

bash:~$ sudo modprobe fuse && sudo mount -a

hi thanks for the great tutorial!!! i love it!

one tiny quibble perhaps:
i did all instructions as req'd, but the "gksudo" commands didn't work for me.. i just used sudo and nano for an editor...
..also this command above did not allow me to properly write to the ntfs partition before reboot; i was frustrated until i realised that for some reason the ubuntu "users and groups" administration dialog from gnome recognized my user as part of the ntfs group, while if i typed "groups" with my user from the term, ntfs was definitely not listed.

perhaps you could add a comment about that situation in your tutorial?

(maybe it was just because i did what you said for ntfs to be available exclusively to the ntfs group-- "umask=0007" in fstab i think)

great howto!

[LKRaider]

Ooops, you are right about the group issue... you must logout and login back again to the group be acknowledged by the system.

I'll update the tutorial. Thanks for the report

About the gksudo... I don't know why it doesn't work... maybe you're using KDE?(don't know how it responds under KDE as I don't use it).
I prefer to use gksudo because it is more user-friendly than regular sudo... at least in Gnome.

[djpate]

hello,

I'm struggling with mounting the stuff.

here is what i got.

djpate@pepette:~/Desktop$ sudo modprobe fuse && sudo mount -a
Couldn't mount device '/dev/hda2': Opération non supportée
Windows did not shut down properly. Try to mount volume in windows, shut down and try again.
Mount failed.
Couldn't mount device '/dev/hdb1': Opération non supportée
Windows did not shut down properly. Try to mount volume in windows, shut down and try again.
Mount failed.

[LKRaider]

Hmm, yes, that is a known issue of ntfsprogs. It cannot fix the filesystem yet (ala chkdsk on windows, or fsck on linux).

If it complains the disk was not shut down properly, you'll have to boot into Windows and run chkdsk (scandisk) on the drive to mark it as clean.

You can also try forcing the mount (read ntfsprogs help), but that is not advisable, since there may be filesystem inconsistencies which need to be fixed.

[dom02]

another thing that might be important to mention is that when you create the user group the GID may not always be the same. You say it's imporant but don't mention that it may be different. This took me a while to realize.

[RRS]

I'm the sole user of my desktop.

Do I really need to create a group and then add my user name to it for this or can I simply edit my current fstab line to mount hda1 with fuse?

Here's my current fstab entry;
/dev/hda1 /media/windows ntfs nls=utf8,umask=0222 0 0

Though it lists "Root" as owner I can open it from the desktop and copy files to my fat32 while logged in as user. I'd like to write with similar ease.

Security is not an issue as I'm the only person with physical access to this computer.

Thanks.

[domino]

This how-to works fine in Breezy. In Dapper, ntfs mounts and I have w/r acces. However, drive icon doesn't show up on my desktop and I can not access the drive icon under "Computer". I have to browse to the "media" folder and access it.