[SOLVED]Steam unable to use a NTFS drive due to lack of execute perms

Irets · 2020-01-24 13:34:22

Today after launching Steam I noticed that my installed games weren't showing as installed anymore, so I went to check the current Steam Libraries from Steam's settings.
My second SSD drive that I have wasn't there anymore.

Because my game files and games are still present on the drive I went and tried to add the library folder again to Steam.
Upon selecting my folder which is /mnt/ssd2/linux, Steam prompts me this message; "New Steam library folder must be on a filesystem mounted with execute permissions".

I initially had a some problems mounting this new SSD a few months ago but that was solved by adding my UID and GID to fstab, which currently looks like this:

UUID=88c4f4a1-239e-4c83-9144-2e7daeab8e2e	/         	ext4      	rw,relatime	0 1
/dev/sdc1					/mnt/ssd2	ntfs-3g		uid=1000,gid=1000	0 0

Output of the command "mount":

proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=8175084k,nr_inodes=2043771,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sdb1 on / type ext4 (rw,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=11705)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1636540k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sdc1 on /mnt/ssd2 type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)

Output of "id":

uid=1000(irets) gid=1000(irets) groups=1000(irets)

The folder and files should all have execute permissions as seen from doing "ls -l" at /mnt/ssd2.

total 12
drwxrwxrwx 1 irets irets    0 Jan  2 08:38 '$RECYCLE.BIN'
drwxrwxrwx 1 irets irets    0 Jan 23 05:41  linux
drwxrwxrwx 1 irets irets    0 Jan 19 08:50 'New folder'
drwxrwxrwx 1 irets irets 4096 Jan 20 05:48 'Stalker Anomaly 1.5.0'
-rwxrwxrwx 1 irets irets 5578 Jan 16 01:22 'stalker anomaly 1.5.ltx'
drwxrwxrwx 1 irets irets    0 Jan 20 07:27 'System Volume Information'
drwxrwxrwx 1 irets irets    0 Jan  2 08:38  windows

Don't mind the other folders, the folder called "linux" is the one that I used for Steam and contains my gamefiles.
This problem started very recently and I'm not quite sure what has caused it.

Am I missing something very obvious?

Last edited by Irets (2020-01-24 14:12:34)

WorMzy · 2020-01-24 13:47:16

Does the system journal tell you why it's mounted read-only and ignoring the uid and gid options?

If I had to hazard a guess, I'd say that the filesystem is damaged: https://wiki.archlinux.org/index.php/NT … ilesystems

Irets · 2020-01-24 14:09:42

I skimmed through the journal but nothing jumped at me, but your hazard guess was enough, running

ntfsfix /dev/sdc1

found something and apparently fixed what it found.

Mounting volume... The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
FAILED
Attempting to correct errors...
Processing $MFT and $MFTMirr...
Reading $MFT... OK
Reading $MFTMirr... OK
Comparing $MFTMirr to $MFT... OK
Processing of $MFT and $MFTMirr completed successfully.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sdc1 was processed successfully.

After that I tried adding the Steam Library folder again and it worked!
I can see and launch all my games now.

Would you happen to know what could have caused this and if there's anything that I could do to prevent this from happening again in the future?
This computer is set up to dualboot Windows 10 and Arch Linux.

Marking the thread as solved.

Last edited by Irets (2020-01-24 14:09:56)

WorMzy · 2020-01-24 14:30:46

lrets wrote:

Would you happen to know what could have caused this

Check the next section in the link.

Irets · 2020-01-24 14:43:34

Ah, I see.
Thank you!

Arch Linux

#1 2020-01-24 13:34:22

[SOLVED]Steam unable to use a NTFS drive due to lack of execute perms

#2 2020-01-24 13:47:16

Re: [SOLVED]Steam unable to use a NTFS drive due to lack of execute perms

#3 2020-01-24 14:09:42

Re: [SOLVED]Steam unable to use a NTFS drive due to lack of execute perms

#4 2020-01-24 14:30:46

Re: [SOLVED]Steam unable to use a NTFS drive due to lack of execute perms

#5 2020-01-24 14:43:34

Re: [SOLVED]Steam unable to use a NTFS drive due to lack of execute perms

Board footer