In the options column add permissions
and auto
(and probably user
or users
)
nls=iso8859-1,permissions,users,auto
permissions
: (NTFS-3G option) Set standard permissions on created files and use standard access control.
auto
: Will be mounted at boot and from mount -a
user
: Allow an ordinary user to mount the filesystem
users
: Allow every user to mount and unmount the filesystem
Then change ownership of the filesystem:
sudo chown -R thomas:thomas /media/data
My line in /etc/fstab
/dev/sda5 /media/ntfs ntfs-3g users,permissions,auto 0 0
Mount and list permissions
sudo mount /media/ntfs
Using default user mapping
bodhi@ufbt:~$ ls -l /media
drwxr-xr-x 1 root root 4096 2012-01-04 17:08 ntfs
Change ownership and list new permissions
bodhi@ufbt:~$ sudo chown bodhi:bodhi /media/ntfs
bodhi@ufbt:~$ ls -l /media
drwxr-xr-x 1 bodhi bodhi 4096 2012-01-04 17:10 ntfs
By default, ntfs-3g mounts the partition noexec, nosuid, and nodev.
noexec
: Do not allow direct execution of any binaries on the mounted filesystem.
nosuid
: Do not allow set-user-identifier or set-group-identifier bits to take effect.
nodev
: Do not interpret character or block special devices on the file system.
To override this and allow executing files, use exec
/dev/sda5 /media/ntfs ntfs-3g exec,permissions,auto 0 0
Now we get
bodhi@ufbt:~$ ls -l /media/ntfs
-rwx------ 1 bodhi bodhi 28 2012-01-04 17:16 file
bodhi@ufbt:~$ /media/ntfs/file
It works
You should add the partitions in question to your /etc/fstab
. The following line will automatically mount /dev/hda2
at boot (that's hidden in the flag default).
/dev/hda2 / ext2 defaults 1 1
If you don't want to mount, you would issue noauto
amongst your options. In your question you appear to be using uuids to address your partitions. You should probably write something like:
UUID=A2E6A54AE6A52011 /mnt/somedisk auto defaults 0 0
Using man fstab
you can learn the specifics of the file's syntax.
Update after you posted your fstab and so on.
You really did screw up the mounting. I am surprised you can boot with four devices mounted into the same mount point /. Presumably, it mounts the first (your all important root partiation /dev/sda8) and then fails with mount point not empty
when it tries the others (or some other error dependent on the type of file systems involved)
At any rate, you need to learn about fstab. Have a look at some of the first google hits for understanding fstab.
So here is what you should do:
First create the mountpoints:
sudo mkdir /mnt/sda2 /mnt/sda3 /mnt/sda5 /mnt/sda7
If you wish you can be more creative with the names. You can also put them somewhere other than /mnt. Your choice.
Next edit your /etc/fstab and put in lines for each of them
/dev/sda2 /mnt/sda2 auto defaults 0 0
/dev/sda3 /mnt/sda3 auto defaults 0 0
/dev/sda5 /mnt/sda5 auto defaults 0 0
/dev/sda7 /mnt/sda7 auto defaults 0 0
I think you had a spare whitespace between the slash and the mnt/sda. These things matter since you broke the mount point into two.
Then, do not reboot. You should be able to test it saying:
sudo mount /mnt/sda2 # and so on for the other partitions
If that works, on next boot they should all come up. If you wish you can replace /dev/sda2 and so on with their respective UUID
footnote instead of screenshots, simple text would have made it possible for me to copy and paste your fstab. As it is, it's pretty but uses more bandwidth and conveys less usable information.
Best Answer
Permissions for ntfs and vfat file systems must be set with the
dmask
,fmask
andumask
options.dmask
controls permissions for directories,fmask
controls permissions for files, andumask
controls both. Since these options set masks, they should be the complement of the permissions you want. For example, rwx for the owner and rx for others is 022 rather than 755.To set the owner, use the
uid
andgid
options for user and group, respectively. You can find your UID with the commandid -u
. To find your GID, useid -g
. These values are both usually 1000.A common set of mount options for ntfs is
uid=1000,gid=1000,dmask=027,fmask=137
. This sets you as the owner of the drive, and sets the permissions todrwxr-x---
.Here are two lines from my /etc/fstab working
If you get no visible error after rebooting and partitions stay readonly or you get an error similar to:
This is because Windows 8 and 10 offer a "Fast Startup" option that depends on a "non-complete" shutdown. You can disable fast startup by following these steps under "Power Options".