I dont post often but I struggled to find a solution to my issue so I am trying to fix that very problem by adding a resource. Hope this helps someone.
I have moved my last windows pc to Linux Mint last weekend (I had some issues writing to my other USBs and had it lying around, technically I set out to try Fedora Silverblue but that may come later down the road now). I keep all my games and important files on secondary hdds and ssds in my machine as I’ve had data loss many times before from moving machines go Linux.
All went well, installation worked, but when I installed Steam, nothing showed up in the ‘storage’ page of the settings menu. “Hmm, it’s probably a permission issue” I thought, if it cant see the drives it’s not allowed to. So next I had to change /etc/fstab
and make sure my drives were mounted correctly (using ntfs-3g instead of ntfs etc on one drive, and adding my users name as the owner and group owner).
This took me a minute to get right because it relies on the uuid of the drive, not the /dev/sdX
identifier. It was super easy to do this through the gnome-disks utility, so I didn’t need to keep editing the fstab file with nano and could see partition names.
Okay so now I have drives and steam can see them (I did also switch from the downloaded deb file from steams website to the apt installation but I dont think I needed to).
I try to run a game, forget proton exists, retry to run the game with compatibility mode on, then get a ‘Disk Write Error’ for my /media/JoshCodes/gamedrive1/SteamLibrary/steamapps/downloading/random/file
.
Super weird I think, but it’s probably a cache issue, some dumb file from my windows machine that didnt get permissioned properly for some reason - idk it was 10pm. I clear my cache, reset steam entirely, manually remove the files, nothing works. On a fluke, a troubleshooting step led me to a solution by way of it not working: I tried to create a symlink between the downloads folder on the main drive and the drive I had the game library installed on.
Can’t remember the error but it was something like “symlinks are not able to be created as they are not compatible with this file system”. Oh dammit. This drive is on a filesystem that is different and incompatible (exFAT) with my other file systems for some reason. if anyone smarter than me can explain this I would love to know what was happening, I’m assuming it’s just ext4 no talkie to exFAT?
Unfortunately I did have to move everything to a 3rd drive, reformat (just used ext4 as its native linux) and put all my files back on. At this point it was like 1am but I could open Civ V and Rocket League! Huzzah, crashed and went to bed. That’s the first time I’ve really stuck with a problem that I wasn’t familiar with, learned a shitload about mounting drives and just thought it through. A little help from the internet at the end but good outcome.
I’ll edit this in a little bit to make sure commands are present and formatting is good.
I hope that helps someone else!
I’ll have to try on Linux but my portable disk is exFAT and I use it for Steam games on my MacBook (both native and Windows) with no issues. Though, that’s through the classic way of running Steam in Wine since there’s no Proton.
Maybe Steam tries to put the Proton prefixes on the drive along with the games and that’s the problem? Wine certainly does need symlink capable FS to work.
If there isn’t already, I’d report this on the Steam for Linux issue tracker (on GitHub for some reason).
No they don’t, any more than any other application. Video game files certainly don’t contain any symlinks usually.