[Solved] NTFS-3G ignoring mount options in /etc/fstab

leiadair · 2019-09-27 03:52:24

in my /etc/fstab, I've got:

UUID=26B8E1C5600100F9 /mnt/games ntfs-3g uid=1000,gid=1000,rw,user,exec,umask=000 0 0

what actually happens when I mount it is:

/dev/sda1 on /mnt/games type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,user)

I need these options for proton to work properly.

Last edited by leiadair (2019-10-01 19:15:59)

V1del · 2019-09-27 07:22:30

Remove the user option, that will lead to the uid/gid getting reset to what the mount point parent directories owner is, which is root. You probably also don't want to explicitly set the umask option.

Last edited by V1del (2019-09-27 07:24:39)

leiadair · 2019-09-28 20:29:22

I removed the user option, the umask option is there for a reason. Regardless, no matter what options I use they always get reset to:

rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,user

Swiggles · 2019-09-28 20:50:24

Just a hunch, but are the ids actually valid?

Please check with

id

leiadair · 2019-09-29 00:26:36

uid=1000(lapis) gid=1000(lapis) groups=1000(lapis),998(wheel)

seth · 2019-09-29 06:57:19

when I mount it

Since there's no "noauto" statement: how exactly do YOU mount it?
If the drive is available during the boot, the system should already have mounted it - do you somehow attempt to mount it again (w/ a fancy GUI)?
If it's not, you'll have to mount it - and the "how" might be relevant here.

leiadair · 2019-09-29 07:02:23

It is mounted by default, and still mounts with the options

rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,user

I was speaking of further attempts to remount. Using

mount -a

to mount the drive. Also tried

mount -t ntfs-3g -o uid=1000,gid=1000,rw,user,exec,umask=000 /dev/sda1 /mnt/games

and

mount -o uid=1000,gid=1000,rw,user,exec,umask=000 /dev/sda1 /mnt/games

with

umount /mnt/games

in between each attempt.

V1del · 2019-09-29 09:00:20

FWIW I double checked on my system and the mount output also shows user_id=0,group_id=0 (probably because root is ultimately the mounter) but the actual permissions are correctly set to my user. Are your hanging yourself up on the mount output without checking the permissions being exposed on the actual mount? I don't have any issues with binding my steam library.

leiadair · 2019-09-29 15:30:24

Proton games are showing the typical signs of permission errors (immediately crashing after launch).

seth · 2019-09-29 15:36:21

Or proton is just a bunch of shitty code that crashes for all sorts of reasons…
How about just looking at the actual file stats instead?

leiadair · 2019-09-29 15:39:48

[lapis@lapis-pc ~]$ ls -l /mnt/games
total 879892
drwxrwxrwx 1 lapis lapis         0 Sep 14 07:45 '$RECYCLE.BIN'
-rwxrwxrwx 1 lapis lapis 670540498 Aug  3 21:53  Documents.7z
-rwxrwxrwx 1 lapis lapis   2560831 Aug  3 22:25  EFI.7z
drwxrwxrwx 1 lapis lapis         0 Jul 29 23:09  Enc
drwxrwxrwx 1 lapis lapis      4096 Sep 12 16:41  found.000
drwxrwxrwx 1 lapis lapis      4096 Sep 14 07:12  found.001
-rwxrwxrwx 1 lapis lapis 227836416 Aug  2 17:29  fuck
drwxrwxrwx 1 lapis lapis      4096 Sep 28 22:05  Games2
drwxrwxrwx 1 lapis lapis     40960 Jul 27 10:57 "junk i don't feel like sorting right now"
drwxrwxrwx 1 lapis lapis         0 Jun  2 23:42  Programs
drwxrwxrwx 1 lapis lapis      4096 Sep 13 04:12  steamapps
drwxrwxrwx 1 lapis lapis      4096 Sep 15 08:35 'System Volume Information'
[lapis@lapis-pc ~]$

They do appear correct, but I'd say proton is well made, after all it is a fork of wine with gaming-specific optimizations.

Swiggles · 2019-09-29 15:44:08

This is the worst case of the X-Y problem I have seen yet.

So I guess the issue is solved and you have actually another problem?

seth · 2019-09-29 15:49:01

ftr, this was less meant as actual criticism at proton and more to stress that the inference is maybe a bit flawed.
Also it's still windows games code that's being run ;-P

Open a new thread, present the actual crash logs. Tag this one as solved.

Mr.Elendig · 2019-09-29 19:17:18

permission mapping may help if it turns out that the problem is related to permissions: https://www.tuxera.com/community/ntfs-3 … rmissions/

Last edited by Mr.Elendig (2019-09-29 19:18:03)

leiadair · 2019-10-01 19:15:00

Sorry for the late reply. I've got everything working now, I just upgraded ntfs-3g and everything started working so IDK. Thanks for all the help.

Arch Linux

#1 2019-09-27 03:52:24

[Solved] NTFS-3G ignoring mount options in /etc/fstab

#2 2019-09-27 07:22:30

Re: [Solved] NTFS-3G ignoring mount options in /etc/fstab

#3 2019-09-28 20:29:22

Re: [Solved] NTFS-3G ignoring mount options in /etc/fstab

#4 2019-09-28 20:50:24

Re: [Solved] NTFS-3G ignoring mount options in /etc/fstab

#5 2019-09-29 00:26:36

Re: [Solved] NTFS-3G ignoring mount options in /etc/fstab

#6 2019-09-29 06:57:19

Re: [Solved] NTFS-3G ignoring mount options in /etc/fstab

#7 2019-09-29 07:02:23

Re: [Solved] NTFS-3G ignoring mount options in /etc/fstab

#8 2019-09-29 09:00:20

Re: [Solved] NTFS-3G ignoring mount options in /etc/fstab

#9 2019-09-29 15:30:24

Re: [Solved] NTFS-3G ignoring mount options in /etc/fstab

#10 2019-09-29 15:36:21

Re: [Solved] NTFS-3G ignoring mount options in /etc/fstab

#11 2019-09-29 15:39:48

Re: [Solved] NTFS-3G ignoring mount options in /etc/fstab

#12 2019-09-29 15:44:08

Re: [Solved] NTFS-3G ignoring mount options in /etc/fstab

#13 2019-09-29 15:49:01

Re: [Solved] NTFS-3G ignoring mount options in /etc/fstab

#14 2019-09-29 19:17:18

Re: [Solved] NTFS-3G ignoring mount options in /etc/fstab

#15 2019-10-01 19:15:00

Re: [Solved] NTFS-3G ignoring mount options in /etc/fstab

Board footer