Initial Remark:Warning! Ntfs writing support is still experimental! You should not enable it on production machines and/or volumes you don't have backups of. Proceed at your own risk!End of Initial Remark.

That being said, it is quite safe and if it fails to write something, will not corrupt your disk (unless there's a bug somewhere).

This initial part is for Breezy only, Dapper users already have the required packages
---- I - Install the necessary dependencies

Code:

bash:~$ sudo apt-get install libfuse2 fuse-utils

II - Get the latest ntfsprogs package

Note: You will be downloading these directly from the Dapper repositories, so they are safe to install.

Dapper and Breezy instructions from here on:Note: you can replace the "gksudo gedit" commands with your preferred editor (ex: "sudo nano", for instance)

1 - Add fuse to the list of modules to load

Code:

bash:~$ echo fuse | sudo tee -a /etc/modules

2 - Create a user group to access the ntfs disks

Code:

bash:~$ sudo addgroup ntfs

The output should look something like this:

Code:

Adding group `ntfs' (1002)...
Done.

Take notice of your group GID (the number printed after the group name), as it can differ for you and we will need it.

3 - Edit the fstab file to mount the disks

Make a backup of your current settings:

Code:

bash:~$ sudo cp /etc/fstab /etc/fstab.bak

Edit the fstab file:

Code:

bash:~$ gksudo gedit /etc/fstab

Find the line that currently mounts your ntfs partitons, and change them to look like this:

Code:

/dev/hda1 /media/hda1 ntfs-fuse auto,gid=1002,umask=0002 0 0

Notice the use of the group's GID from before, and the umask to allow write access just to owner (root) and group (ntfs), and read access to everyone.
You could also use an umask=0007 to block all access for users not on the ntfs group.

4 - Add users to the ntfs group

Code:

bash:~$ sudo adduser username ntfs

Where username stands for the user you whish to add (replace it with a real username). Do this for all the users you want to be able to write to ntfs disks.

If you reboot now, the disk will be writable to the selected users when they logon.

If you want the changes to take effect immediately without rebooting, execute these commands:

Code:

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

(Ignore errors about "/" and others not being unmounted, it doesn't matter)
You'll have to logout from all your user sessions for the new group to be acknowledged (usually a logout from your graphical session and login back again will do it).

TROUBLESHOOT
1) If you get this error:

Code:

Couldn't mount device '/dev/hda1': Operation not supported
Windows did not shut down properly. Try to mount volume in windows, shut down and try again.
Mount failed.

You will have to boot into your Windows OS and do a "chkdsk /f" (aka. scandisk) on the partiton that you are trying to mount. Currently, ntfsprogs can't check/fix the integrity of the partitions and will refuse to mount them if they are marked as dirty (ie. needing to be checked), so you'll have to do it from Windows.

2) You can't access the ntfs partitions from Nautilus anymore from the computer:/// places. This is a bug of Nautilus I think. You'll get an error like this:

Code:

Unable to mount the selected volume mount: according to mtab, /dev/hda1 is already mounted on /media/hda1

A workaround is manually creating a link from the mountpoint to your desktop for easy access.

Re: HOWTO: Mount NTFS volumes with write support

I also cannot find libntfs.so.9 - I assume this is a Breezy thing. Although a quick hunt shows me that Dapper has libntfs.so.8, so I may be wrong.

Still, I would love to be able to get write access on my NTFS partition. It has a buggered install of XP, but too much data which I cannot backup (30+ GB) for me to format. But if I can use it like a normal hard drive (or at least write to it), then I would feel much happier

If anyone feels like enlightening us on this problem, don't hesitate

Steve

EDIT -- Well as soon as I wrote this one of my housemates wandered in - and aftr a brief conversation he's lending me his 30GB iPod to sort the problem out. Oh well. Still, for other user it would be a very useful tool!