Steam for Linux > Discusiones generales > Detalles del tema
How to fly as Spooder Man? 28 de Jul, 2013 a las 3:12
''New Steam library folder must be on a filesystem mounted with execute permissions''
I got the following error trying to install a new steam library folder on an external usb hard drive. I tried different external hard drives as well as flash drives, but they all get the same error. I have succeeded in installing steam games on external hard drives on windows, however my steam games need to be installed on linux in this situation.

How can I bypass this error code? Must I give execute permissions to the external drive? If this is so, how will it happen?
Mostrando 1-10 de 10 comentarios
< >
vodik 28 de Jul, 2013 a las 3:43 
What filesystem is on the usb drive? Is it mounted with noexec? UIf Steam is complaining it can't set executable flag on the filesystem, that filesystme is likely fat and you can't chmod on fat.

Is this drive for linux only? Reformat it to ext4 or something else.
Yoyosan 28 de Jul, 2013 a las 3:48 
Hello.

By presuming you have Ubuntu installed, I've fixed this problem by adding this line in the /etc/fstab file:
/dev/sda6 /media/MEDIA7 ntfs-3g defaults,user,locale=en_US.utf8,exec,uid=1000,gid=1000 0 0

Presuming that your external disk is formatted AS NTFS, replace /dev/sda6 with your disk path(you can find it out using "fdisk -l"). The /media/MEDIA7 is the mount point. Make sure that you replace the integer values of uid and gid with your own(you can get them by using "id").

Note that the exec flag is what is fixing your problem.
Última edición por Yoyosan; 28 de Jul, 2013 a las 4:28
vodik 28 de Jul, 2013 a las 8:51 
Thats assuming NTFS. Its an external usb, my bets is on fat32.
Lord Easpada 24 de Oct, 2013 a las 0:24 
what i did was i clicked on Files, went down to my hard drive right clicked went to permissions and then changed it so i had read write permissions for my group which included me and that fixed it.
reznor 27 de Jun a las 15:38 
For Linux users who are using decent file systems:
If you are using the directive "user(s)" in your /etc/fstab, you must specify "exec" afterwards. "user(s)" implies "noexec", that's an security feature. The directives are processed in order, specifying "exec" after "user(s)" solves this problem.
Última edición por reznor; 27 de Jun a las 15:40
GranadaFEUP 14 de Sep a las 14:38 
@reznor

Thank you, your solution worked for me.
(`O_O!) 19 de Dic a las 3:29 
my system:arch+openbox
I have mounted my disk with"mount -o default,exec,umask=0"
But it still showed wrong message.
LOLCAT 19 de Dic a las 4:50 
Publicado originalmente por (``o_o!):
my system:arch+openbox
I have mounted my disk with"mount -o default,exec,umask=0"
But it still showed wrong message.
The error message is faulty, it doesn't actually show the real issue. You just have to rename SteamApps to steamapps (lowercase). One of the recent updates started using the new directory name.
Tömer 23 de Dic a las 10:25 
Thats it, that fixed the error for me
Ancu 25 de Dic a las 7:45 
Publicado originalmente por LOLCAT:
Publicado originalmente por (``o_o!):
my system:arch+openbox
I have mounted my disk with"mount -o default,exec,umask=0"
But it still showed wrong message.
The error message is faulty, it doesn't actually show the real issue. You just have to rename SteamApps to steamapps (lowercase). One of the recent updates started using the new directory name.

Holy ♥♥♥♥ thanks so much dude, I was freaking out because my ext4 partition had always worked before and it suddenly disappeared from steam.
Mostrando 1-10 de 10 comentarios
< >
Por página: 15 30 50