Steam Library-Must be on a filesystem mounted with execute permissions
I've looked at various questions and threads and forums on this and nothing has worked.
I've been trying to mount a HDD that I have my linux games installed to. This drive worked flawlessly in the past but now Steam needs to find it again to say these games are installed. But when I try to add the appropriate folder I get this error:
New Steam library folder must be on a filesystem mounted with execute
permissions
I've tried changing the folder name as suggested here and I've tried the solution here but run into a permission denied. Therefore I followed the steps here but am still running into permission is denied.
My question is what am I doing wrong and am I going about this correctly? How can I make steam see my games folder again? Any help is really appreciated.
I am running Ubuntu 14.04 and the drive location is /media/alkarin/Volume11
/dev/sdb2 is indeed ntfs
mount permissions hard-drive games steam
asked Dec 22 '15 at 17:08
AlkarinAlkarin
831615
add a comment |
I've looked at various questions and threads and forums on this and nothing has worked.
I've been trying to mount a HDD that I have my linux games installed to. This drive worked flawlessly in the past but now Steam needs to find it again to say these games are installed. But when I try to add the appropriate folder I get this error:
New Steam library folder must be on a filesystem mounted with execute
permissions
I've tried changing the folder name as suggested here and I've tried the solution here but run into a permission denied. Therefore I followed the steps here but am still running into permission is denied.
My question is what am I doing wrong and am I going about this correctly? How can I make steam see my games folder again? Any help is really appreciated.
I am running Ubuntu 14.04 and the drive location is /media/alkarin/Volume11
/dev/sdb2 is indeed ntfs
mount permissions hard-drive games steam
asked Dec 22 '15 at 17:08
AlkarinAlkarin
831615
Just a wild guess: perhaps the external drive have NTFS or FAT file system, thus executable rights not supported?
– Hi-Angel
Dec 22 '15 at 17:30
/dev/sdb2 is indeed ntfs.
– Alkarin
Dec 22 '15 at 17:47
okay, I won't post as an answer as it needs some time to research, but I can give you advice for what to do*(or perhaps anybody else could elaborate)*. So, the NTFS filesystem does actually support unix-permissions. You just need to remount it with some option, and that's where you perhaps need to do some research. When you find that, and if that indeed solve the problem with Steam — you can modify the/etc/fstabto mount NTFS every time with the option.
– Hi-Angel
Dec 22 '15 at 17:58
add a comment |
I've looked at various questions and threads and forums on this and nothing has worked.
I've been trying to mount a HDD that I have my linux games installed to. This drive worked flawlessly in the past but now Steam needs to find it again to say these games are installed. But when I try to add the appropriate folder I get this error:
New Steam library folder must be on a filesystem mounted with execute
permissions
I've tried changing the folder name as suggested here and I've tried the solution here but run into a permission denied. Therefore I followed the steps here but am still running into permission is denied.
My question is what am I doing wrong and am I going about this correctly? How can I make steam see my games folder again? Any help is really appreciated.
I am running Ubuntu 14.04 and the drive location is /media/alkarin/Volume11
/dev/sdb2 is indeed ntfs
mount permissions hard-drive games steam
asked Dec 22 '15 at 17:08
AlkarinAlkarin
831615
I've looked at various questions and threads and forums on this and nothing has worked.
I've been trying to mount a HDD that I have my linux games installed to. This drive worked flawlessly in the past but now Steam needs to find it again to say these games are installed. But when I try to add the appropriate folder I get this error:
New Steam library folder must be on a filesystem mounted with execute
permissions
I've tried changing the folder name as suggested here and I've tried the solution here but run into a permission denied. Therefore I followed the steps here but am still running into permission is denied.
My question is what am I doing wrong and am I going about this correctly? How can I make steam see my games folder again? Any help is really appreciated.
I am running Ubuntu 14.04 and the drive location is /media/alkarin/Volume11
/dev/sdb2 is indeed ntfs
mount permissions hard-drive games steam
mount permissions hard-drive games steam
asked Dec 22 '15 at 17:08
AlkarinAlkarin
831615
asked Dec 22 '15 at 17:08
AlkarinAlkarin
831615
edited Oct 12 '18 at 23:26
Alkarin
asked Dec 22 '15 at 17:08
AlkarinAlkarin
831615
asked Dec 22 '15 at 17:08
AlkarinAlkarin
831615
asked Dec 22 '15 at 17:08
AlkarinAlkarin
831615
831615
Just a wild guess: perhaps the external drive have NTFS or FAT file system, thus executable rights not supported?
– Hi-Angel
Dec 22 '15 at 17:30
/dev/sdb2 is indeed ntfs.
– Alkarin
Dec 22 '15 at 17:47
okay, I won't post as an answer as it needs some time to research, but I can give you advice for what to do*(or perhaps anybody else could elaborate)*. So, the NTFS filesystem does actually support unix-permissions. You just need to remount it with some option, and that's where you perhaps need to do some research. When you find that, and if that indeed solve the problem with Steam — you can modify the/etc/fstabto mount NTFS every time with the option.
– Hi-Angel
Dec 22 '15 at 17:58
add a comment |
Just a wild guess: perhaps the external drive have NTFS or FAT file system, thus executable rights not supported?
– Hi-Angel
Dec 22 '15 at 17:30
/dev/sdb2 is indeed ntfs.
– Alkarin
Dec 22 '15 at 17:47
okay, I won't post as an answer as it needs some time to research, but I can give you advice for what to do*(or perhaps anybody else could elaborate)*. So, the NTFS filesystem does actually support unix-permissions. You just need to remount it with some option, and that's where you perhaps need to do some research. When you find that, and if that indeed solve the problem with Steam — you can modify the/etc/fstabto mount NTFS every time with the option.
– Hi-Angel
Dec 22 '15 at 17:58
Just a wild guess: perhaps the external drive have NTFS or FAT file system, thus executable rights not supported?
– Hi-Angel
Dec 22 '15 at 17:30
Just a wild guess: perhaps the external drive have NTFS or FAT file system, thus executable rights not supported?
– Hi-Angel
Dec 22 '15 at 17:30
/dev/sdb2 is indeed ntfs.
– Alkarin
Dec 22 '15 at 17:47
/dev/sdb2 is indeed ntfs.
– Alkarin
Dec 22 '15 at 17:47
okay, I won't post as an answer as it needs some time to research, but I can give you advice for what to do*(or perhaps anybody else could elaborate)*. So, the NTFS filesystem does actually support unix-permissions. You just need to remount it with some option, and that's where you perhaps need to do some research. When you find that, and if that indeed solve the problem with Steam — you can modify the
/etc/fstab to mount NTFS every time with the option.– Hi-Angel
Dec 22 '15 at 17:58
okay, I won't post as an answer as it needs some time to research, but I can give you advice for what to do*(or perhaps anybody else could elaborate)*. So, the NTFS filesystem does actually support unix-permissions. You just need to remount it with some option, and that's where you perhaps need to do some research. When you find that, and if that indeed solve the problem with Steam — you can modify the
/etc/fstab to mount NTFS every time with the option.– Hi-Angel
Dec 22 '15 at 17:58
add a comment |
2 Answers
2
active
oldest
votes
This Steam error occurs because your drive is mounted by root and you don't have execute permissions on the drive (I think). You can use the disks app to change this.
Search disks in the dash, highlight your drive and under the usage image is a small cog icon, click this and edit mount options, now make your settings look like this
Leave the rest as it is and reboot. Now your drive can be found in /mnt and is auto mounted as your user at boot.
This is how I fix this error in 14.04, NTFS drive.
answered Dec 22 '15 at 18:11
Mark KirbyMark Kirby
14k146298
2
That did it. Thank you! And thank you for explaining why its not working as well.
– Alkarin
Dec 22 '15 at 19:53
5
This solution doesn't seem work in Ubuntu GNOME 17.04.
– Jesse
May 1 '17 at 4:25
add a comment |
For the logs: using ntfs-3g driver, the following minimalistic fstab did the trick for me
/dev/sdaX /media/target-mountpoint ntfs-3g defaults,x-gvfs-show 0 0
Hope that helps anyone :) Before i had forced uid and gid (to the user i was actually logged in with) and that didnt worked for some reason (i could create folders and files on the drive from a shell though, not sure what the problem was).
So the options that didnt worked:
defaults,permissions,users,uid=1000,gid=33
(Yes, my host user has www-data as primary group)
answered Jan 6 at 14:00
delfdelf
1284
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f712451%2fsteam-library-must-be-on-a-filesystem-mounted-with-execute-permissions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
This Steam error occurs because your drive is mounted by root and you don't have execute permissions on the drive (I think). You can use the disks app to change this.
Search disks in the dash, highlight your drive and under the usage image is a small cog icon, click this and edit mount options, now make your settings look like this
Leave the rest as it is and reboot. Now your drive can be found in /mnt and is auto mounted as your user at boot.
This is how I fix this error in 14.04, NTFS drive.
answered Dec 22 '15 at 18:11
Mark KirbyMark Kirby
14k146298
2
That did it. Thank you! And thank you for explaining why its not working as well.
– Alkarin
Dec 22 '15 at 19:53
5
This solution doesn't seem work in Ubuntu GNOME 17.04.
– Jesse
May 1 '17 at 4:25
add a comment |
This Steam error occurs because your drive is mounted by root and you don't have execute permissions on the drive (I think). You can use the disks app to change this.
Search disks in the dash, highlight your drive and under the usage image is a small cog icon, click this and edit mount options, now make your settings look like this
Leave the rest as it is and reboot. Now your drive can be found in /mnt and is auto mounted as your user at boot.
This is how I fix this error in 14.04, NTFS drive.
answered Dec 22 '15 at 18:11
Mark KirbyMark Kirby
14k146298
2
That did it. Thank you! And thank you for explaining why its not working as well.
– Alkarin
Dec 22 '15 at 19:53
5
This solution doesn't seem work in Ubuntu GNOME 17.04.
– Jesse
May 1 '17 at 4:25
add a comment |
This Steam error occurs because your drive is mounted by root and you don't have execute permissions on the drive (I think). You can use the disks app to change this.
Search disks in the dash, highlight your drive and under the usage image is a small cog icon, click this and edit mount options, now make your settings look like this
Leave the rest as it is and reboot. Now your drive can be found in /mnt and is auto mounted as your user at boot.
This is how I fix this error in 14.04, NTFS drive.
answered Dec 22 '15 at 18:11
Mark KirbyMark Kirby
14k146298
This Steam error occurs because your drive is mounted by root and you don't have execute permissions on the drive (I think). You can use the disks app to change this.
Search disks in the dash, highlight your drive and under the usage image is a small cog icon, click this and edit mount options, now make your settings look like this
Leave the rest as it is and reboot. Now your drive can be found in /mnt and is auto mounted as your user at boot.
This is how I fix this error in 14.04, NTFS drive.
answered Dec 22 '15 at 18:11
Mark KirbyMark Kirby
14k146298
edited Dec 22 '15 at 18:51
answered Dec 22 '15 at 18:11
Mark KirbyMark Kirby
14k146298
answered Dec 22 '15 at 18:11
Mark KirbyMark Kirby
14k146298
answered Dec 22 '15 at 18:11
Mark KirbyMark Kirby
14k146298
14k146298
2
That did it. Thank you! And thank you for explaining why its not working as well.
– Alkarin
Dec 22 '15 at 19:53
5
This solution doesn't seem work in Ubuntu GNOME 17.04.
– Jesse
May 1 '17 at 4:25
add a comment |
2
That did it. Thank you! And thank you for explaining why its not working as well.
– Alkarin
Dec 22 '15 at 19:53
5
This solution doesn't seem work in Ubuntu GNOME 17.04.
– Jesse
May 1 '17 at 4:25
2
2
That did it. Thank you! And thank you for explaining why its not working as well.
– Alkarin
Dec 22 '15 at 19:53
That did it. Thank you! And thank you for explaining why its not working as well.
– Alkarin
Dec 22 '15 at 19:53
5
5
This solution doesn't seem work in Ubuntu GNOME 17.04.
– Jesse
May 1 '17 at 4:25
This solution doesn't seem work in Ubuntu GNOME 17.04.
– Jesse
May 1 '17 at 4:25
add a comment |
For the logs: using ntfs-3g driver, the following minimalistic fstab did the trick for me
/dev/sdaX /media/target-mountpoint ntfs-3g defaults,x-gvfs-show 0 0
Hope that helps anyone :) Before i had forced uid and gid (to the user i was actually logged in with) and that didnt worked for some reason (i could create folders and files on the drive from a shell though, not sure what the problem was).
So the options that didnt worked:
defaults,permissions,users,uid=1000,gid=33
(Yes, my host user has www-data as primary group)
answered Jan 6 at 14:00
delfdelf
1284
add a comment |
For the logs: using ntfs-3g driver, the following minimalistic fstab did the trick for me
/dev/sdaX /media/target-mountpoint ntfs-3g defaults,x-gvfs-show 0 0
Hope that helps anyone :) Before i had forced uid and gid (to the user i was actually logged in with) and that didnt worked for some reason (i could create folders and files on the drive from a shell though, not sure what the problem was).
So the options that didnt worked:
defaults,permissions,users,uid=1000,gid=33
(Yes, my host user has www-data as primary group)
answered Jan 6 at 14:00
delfdelf
1284
add a comment |
For the logs: using ntfs-3g driver, the following minimalistic fstab did the trick for me
/dev/sdaX /media/target-mountpoint ntfs-3g defaults,x-gvfs-show 0 0
Hope that helps anyone :) Before i had forced uid and gid (to the user i was actually logged in with) and that didnt worked for some reason (i could create folders and files on the drive from a shell though, not sure what the problem was).
So the options that didnt worked:
defaults,permissions,users,uid=1000,gid=33
(Yes, my host user has www-data as primary group)
answered Jan 6 at 14:00
delfdelf
1284
For the logs: using ntfs-3g driver, the following minimalistic fstab did the trick for me
/dev/sdaX /media/target-mountpoint ntfs-3g defaults,x-gvfs-show 0 0
Hope that helps anyone :) Before i had forced uid and gid (to the user i was actually logged in with) and that didnt worked for some reason (i could create folders and files on the drive from a shell though, not sure what the problem was).
So the options that didnt worked:
defaults,permissions,users,uid=1000,gid=33
(Yes, my host user has www-data as primary group)
answered Jan 6 at 14:00
delfdelf
1284
answered Jan 6 at 14:00
delfdelf
1284
answered Jan 6 at 14:00
delfdelf
1284
answered Jan 6 at 14:00
delfdelf
1284
1284
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f712451%2fsteam-library-must-be-on-a-filesystem-mounted-with-execute-permissions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Just a wild guess: perhaps the external drive have NTFS or FAT file system, thus executable rights not supported?
– Hi-Angel
Dec 22 '15 at 17:30
/dev/sdb2 is indeed ntfs.
– Alkarin
Dec 22 '15 at 17:47
okay, I won't post as an answer as it needs some time to research, but I can give you advice for what to do*(or perhaps anybody else could elaborate)*. So, the NTFS filesystem does actually support unix-permissions. You just need to remount it with some option, and that's where you perhaps need to do some research. When you find that, and if that indeed solve the problem with Steam — you can modify the
/etc/fstabto mount NTFS every time with the option.– Hi-Angel
Dec 22 '15 at 17:58