Difference between revisions of "NTFS-3G"

From ArchWiki
Jump to navigation Jump to search
(Troubleshooting: Adding how to fix mount error when dual booting with Windows 8.)
m (show parameter to quick format)
Line 144: Line 144:
  # mkfs.ntfs -L myCoolDiskName /dev/sdc1
  # mkfs.ntfs -L myCoolDiskName /dev/sdc1
If you dont want this to take ages on modern harddrives use:
# mkfs.ntfs -Q -L myCoolDiskName /dev/sdc1
{{Note| manpage on -Q: Perform quick (fast) format. This will skip both zeroing of the volume and bad sector checking.}}
== Resources ==
== Resources ==
* [http://www.tuxera.com/community/ntfs-3g-manual/ Official NTFS-3G Manual]
* [http://www.tuxera.com/community/ntfs-3g-manual/ Official NTFS-3G Manual]

Revision as of 12:08, 16 March 2013

zh-CN:NTFS-3G zh-TW:NTFS-3G NTFS-3G is an open source implementation of Microsoft's NTFS file system that includes read and write support. Because it is considered to be easier to configure and developed write support earlier, users generally prefer NTFS-3G over ntfsprogs ntfsmount. NTFS-3G developers use the FUSE file system to facilitate development and to help with portability. This document will describe how to setup NTFS-3G to work on your computer.


Install the ntfs-3g package from the official repositories.

Manual mounting

Two options exist for manually mounting NTFS partitions. The traditional:

# mount -t ntfs-3g /dev/<your-NTFS-partition> /{mnt,...}/<folder>

Mount type ntfs-3g does not need to be explicitly specified in Arch. The mount command by default will use /sbin/mount.ntfs which is symlinked to /bin/ntfs-3g after the ntfs-3g package is installed.

The second option is to call ntfs-3g directly:

# ntfs-3g /dev/<your-NTFS-partition> /<mount-location>


Your NTFS partition(s) can be setup to mount automatically, or pre-configured to be able to mount in a certain way when you would like them to be mounted. This configuration can be done in the static filesystem configuration (fstab) or by the use of udev rules.

Default settings

Using the default settings will mount the NTFS partition(s) at boot. With this method, if the parent folder that it is mounted upon has the proper user or group permissions, then that user or group will be able to read and write on that partition(s).

Put this in /etc/fstab:

# <file system>   <dir>		<type>    <options>             <dump>  <pass>
/dev/<NTFS-part>  /mnt/windows  ntfs-3g   defaults		  0       0

Linux compatible permissions

Permissions on a Linux system are normally set to 755 for folders and 644 for files. It is recommended to keep these permissions in use for the NTFS partition as well if you use the partition on a regular basis. The following example assigns the above permissions to a normal user:

# Mount internal windows partition with linux compatible permissions, i.e. 755 for directories (dmask=022) and 644 for files (fmask=133)
UUID=01CD2ABB65E17DE0 /run/media/user1/Windows ntfs-3g uid=user1,gid=users,dmask=022,fmask=133 0 0

Allowing Group/User

You can also tell /etc/fstab (the NTFS-3G driver) other options like those who are allowed to access (read) the partition. For example, for you to allow people in the users group to have access:

/dev/<NTFS-part>  /mnt/windows  ntfs-3g   gid=users,umask=0022    0       0

By default, the above line will enable write support for root only. To enable user writing, you have to specify the user who should be granted write permissions. Use the uid parameter together with your username to enable user writing:

/dev/<NTFS-part>  /mnt/windows  ntfs-3g   uid=username,gid=users,umask=0022    0       0

If you are running on a single user machine, you may like to own the file system yourself and grant all possible permissions:

/dev/<NTFS-part>  /mnt/windows  ntfs-3g   uid=USERNAME,gid=users    0       0

Basic NTFS-3G options

For most, the above settings should suffice. Here are a few other options that are general common options for various Linux filesystems. For a complete list, see this

umask is a built-in shell command which automatically sets file permissions on newly created files. For Arch Linux, the default umask for root and user is 0022. With 0022 new folders have the directory permissions of 755 and new files have permissions of 644. You can read more about umask permissions here.
If noauto is set, NTFS entries in /etc/fstab do not get mounted automatically at boot.
The user id number. This allows a specific user to have full access to the partition. Your uid can be found with the id command.
fmask and dmask
Like umask but defining file and directory respectively individually.
(deprecated as of 2009.1.1) - some locales will need to specify their region for local characters to display properly.

Allowing user to mount

By default, ntfs-3g requires root rights to mount the filesystem, even with the "user" option in /etc/fstab, the reason why can be found here. The user option in the fstab is still required. To be able to mount as user, a few tweaks need to be made:

First, check that you have access to the mount block you want to use, the easiest way to do that is to be in the disk groups with the following command:

# gpasswd -a username disk
Note: groups rights sometimes requires rebooting to kick in

You also need acces right to the mount point you want to use, since we're going to mount something as user on this mountpoint, we might as well own it:

# chown <user> /mnt/<mountpoint>

Second is having a ntfs-3g driver compiled with integrated FUSE support, the ntfs-3g package from extra doesn't, but there is one on AUR.

Third, we need to setuid root the driver. It is done by issuing these two commands as root:

# chown root $(which ntfs-3g)
# chmod 4755 $(which ntfs-3g) 

You should now be able to mount your NTFS partition without root rights.

Note: There seems to be an issue with unmounting rights, so you will still need root rights if you need to unmount the filesystem


ntfs-configAUR is a program that may be able to help configure your NTFS partition(s) if other methods do not work.


Some ideas for troubleshooting common problems.

Damaged NTFS Filesystems

If an NTFS filesystem has errors on it, NTFS-3G will mount it as read-only. To fix an NTFS filesystem, load Windows and run its disk checking program, chkdsk. Take in account that ntfsfix can only repair some errors. If it fails, chkdsk will probably succeed.

To repair the file system without booting windows, install the ntfsprogs package available in the official repositories.

To fix the NTFS file system, the device must already be unmounted. For example, to fix an NTFS partition residing in /dev/sda2:

# umount /dev/sda2
# ntfsfix /dev/sda2
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
NTFS volume version is 3.1.
NTFS partition /dev/sda2 was processed successfully.
# mount /dev/sda2

If all went well, the volume will now be writable.

"Metadata kept in Windows cache, refused to mount"

When dual booting with Windows 8, trying to mount a partition that is visible to Windows may yield the following error:

 The disk contains an unclean file system (0, 0).
 Metadata kept in Windows cache, refused to mount.
 Failed to mount '/dev/sdc1': Operation not permitted
 The NTFS partition is in an unsafe state. Please resume and shutdown
 Windows fully (no hibernation or fast restarting), or mount the volume
 read-only with the 'ro' mount option.

The problem is due to the new Windows 8 feature called "fast startup". When fast startup is enabled, part of the metadata of all mounted partitions are restored to the state they were at the previous closing down. As a consequence, changes made on Linux may be lost. This can happen on any partition of an internal disk when leaving Windows 8 by selecting "Shut down" or "Hibernate". Leaving Windows 8 by selecting "Restart", however, is apparently safe.

To enable writing to the partitions on other operating systems, be sure the fast restarting of Windows 8 is disabled. This can be achieved by issuing as an administrator the command:

 powercfg /h off

You can check the current settings on Control Panel > Hardware and Sound > Power Options > System Setting > Choose what the power buttons do. The box "Turn on fast startup" should either be disabled or missing.

Mount Failure

If you cannot mount your NTFS partition even when following this guide, try using the UUID instead of device name in /etc/fstab for all NTFS partitions. Here's an fstab example.

Format NTFS

Install ntfsprogs.

Warning: As always, double check the device path.
# mkfs.ntfs -L myCoolDiskName /dev/sdc1

If you dont want this to take ages on modern harddrives use:

# mkfs.ntfs -Q -L myCoolDiskName /dev/sdc1
Note: manpage on -Q: Perform quick (fast) format. This will skip both zeroing of the volume and bad sector checking.