this post was submitted on 13 Feb 2026
20 points (95.5% liked)

Linux Gaming

24525 readers
223 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

No memes/shitposts/low-effort posts, please.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 2 years ago
MODERATORS
monolalia@lemmy.world
20
Issues with games on secondary drive (lemmy.org)
submitted 1 week ago* (last edited 1 week ago) by ui3bg4r@lemmy.org to c/linux_gaming@lemmy.world
17 comments fedilink hide all child comments
 

Both primary and secondary ssd (internal both) are formatted Ext4 (linux mint)

I am facing this weird issue: Some games, they play flawless when installed in the secondary drive. Some others however, they don't launch. I have to move them to the primary drive for them to launch and then they work perfect.

How come some games are ok on the secondary drive, while others aren't? Have you experience this?

Everything I find online points to a drive being NFTS format, but mine are both Ext4, default settings and automounting.

Games that gave problems on secondary drive, but are perfect on primary driver; Ghost of Tsushima, Resident evil 4 and Witcher 3. They don't launch, and in the case of RE4 it even said my computer had a virus :D or was tampered when launched from the secondary drive (non-sense)

you are viewing a single comment's thread
view the rest of the comments
[–] RamRabbit@lemmy.world 2 points 1 week ago* (last edited 1 week ago) (7 children)

Try using a folder symlink that encompasses the game's folder, so that the game thinks it is on the main drive, but is actually on the secondary drive. Might work around whatever issue is here.

Steps:

  1. Create a folder for the game: /home/Games/SpecificGameWithAnIssue

  2. Create a symlink from /home/Games/SpecificGameWithAnIssue to /mnt/DriveTwo/WhereTheGameNowLives

  3. Install game to /home/Games/SpecifcGameWithAnIssue

  4. Run game

[–] ui3bg4r@lemmy.org 1 points 1 week ago (6 children)

Thanks for the explanation, i will try. On Step 3, shouldn't the game be installed in /mnt isntead of home?

[–] RamRabbit@lemmy.world 1 points 1 week ago* (last edited 1 week ago) (5 children)

shouldn’t the game be installed in /mnt isntead of home

No.

The symlink creates a link between /home/Games/SpecificGameWithAnIssue (dir1) and /mnt/DriveTwo/WhereTheGameNowLives (dir2). Anything you put in dir1 will actually live in dir2. However, you can access all the files as if they are in dir1 (you can also access them directly from dir2, but we aren't going to do that here).

By installing it on the main drive (dir1), you are telling the game it is actually in dir1, and it should look at dir1 for its files. The fact they happen to be elsewhere is immaterial to the game, it's looking at dir1 for the files. Think of it like a magic portal, you step through a door and suddenly you are in neverland. The way to get to neverland is through that door.

I'm thinking this will workaround your issue as, for all intents and purposes, everything is on the main drive (they just happen to be stored elsewhere via the symlink).

[–] turbowafflz@lemmy.world 2 points 1 week ago

If they're launched through steam the sandboxing will likely prevent access to the place the symlink points to, I've encountered that before trying to do similar things

load more comments (4 replies)
load more comments (4 replies)
load more comments (4 replies)