Steam for Linux
All Discussions Artwork Videos News Guides

Steam for Linux

Menfistofeles 9 Jun @ 6:53pm
"Disk write error" when trying to install games on a second drive in fedora 40
I want to create a new library on a second drive. What I've done is:
-Created a folder inside the mounted drive called steam
-selected said folder through steam as the new library.
Steam detects it as an external hard drive and says "the drive is not correctly connected" when trying to install to that library but it does let me select and proceed to the download. When downloading it first says "connection timed out", after retrying it says "disk write error"
so far I've checked for the following:
-the hard drive format is Ext4
-the drive has 800gb of free space according to steam. I do not have anything on the drive but the residual files when steam tries to download a game.
-I've used flatseal to give steam all permissions possible.
-I've restarted steam many times
-cleared the download cache on steam
-checked if the folder where I mounted the drive is own by my user or root, it is owned by my user.
Is it even possible to create a new library on a second drive in linux?

Edit:
What happened, as people pointed out below, is that the flatpack version of steam doesn't have access to that drive by default, you can give it access with flatseal, under system files, add the place where the drive is mounted. This also works for the Heoric launcher and other flatpacks apps.
The easier solution is to download a non Flatpack version of steam.
Last edited by Menfistofeles; 11 Jun @ 11:33pm
The author of this topic has marked a post as the answer to their question.
Click here to jump to that post.
Originally posted by Zyro:
Creating a second library on another drive is usually as easy as clicking some buttons on Linux. Either Flatpak is in your way, or the folder you created manually. I would delete the folder and try again. Steam creates what it needs on its own. If that doesn't work, I'd recommend the "native" (no Flatpak, no Snap) Steam package that comes with your distribution.
< >
Showing 1-5 of 5 comments
The author of this thread has indicated that this post answers the original topic.
Zyro 10 Jun @ 12:52am 
Creating a second library on another drive is usually as easy as clicking some buttons on Linux. Either Flatpak is in your way, or the folder you created manually. I would delete the folder and try again. Steam creates what it needs on its own. If that doesn't work, I'd recommend the "native" (no Flatpak, no Snap) Steam package that comes with your distribution.
#1
Xenophobe 10 Jun @ 6:01am 
is the second drive set to mount at boot? if steam is started before the drive is mounted it may not pick it up properly, but it's most likely flatpak having issues.
#2
Menfistofeles 10 Jun @ 10:17am 
Originally posted by Zyro:
Creating a second library on another drive is usually as easy as clicking some buttons on Linux. Either Flatpak is in your way, or the folder you created manually. I would delete the folder and try again. Steam creates what it needs on its own. If that doesn't work, I'd recommend the "native" (no Flatpak, no Snap) Steam package that comes with your distribution.
Yes, it was a the flatpack version that was causing the issues, I just didn't know exactly how flatpack works but using the "native" version of steam fixed it.
#3
Zyro 10 Jun @ 11:13pm 
Happy gaming! :signix::steamhappy:
#4
Marlock 11 Jun @ 1:33pm 
fyi:
the flatpak *can* see outside its sandbox if you let it, but it is isolated by default

you can use a terminal command or FlatSeal to change this

that being said, the native package works fine for most people, so no need to move back into the flatpak now... just keep this in mind if you ever get stuck on another issue and want to try the flatpak again as a workaround
#5
< >
Showing 1-5 of 5 comments
Per page: 1530 50

Steam for Linux > Valve Games and Steam for Linux Client > Topic Details
Date Posted: 9 Jun @ 6:53pm
Posts: 5

Discussions Rules and Guidelines