Moved games to different partition, now games won't launch.
I used steams built in move feature to move all my games, proton, steam files to a partition on a different drive. It is formatted as EXT4. Games launched perfectly fine prior to moving them to different drive. If it matters I do have windows on another partition of that drive.
258 Replies
for some reason it isn't letting me send my log
there
out of all my games all but left 4 dead don't launch
I suppose Left4Dead is using native binaries and isn't running through Proton?
I'm kind of working through similar issues, so brainstorming might help
Can you check if your account is the owner of the files in the SteamLibrary on the other drive?
Wdym?
I believe Steam is picky and won't run the game if the owner of the files isn't the same as the one trying to run the game.
hrm
how do I go about checking that
Browse to the directory of a game under SteamLibrary/steamapps and check the permissions tab in the properties
new to linux and deep diving into this stuff
Yeah shared Steam libraries on Linux aren't as easy as I thought it would have been.
is the drive mounted manually or automatically?
uhh
how do I check that
i believe manually
it just confuses me that left 4 dead is the only one that runs right
did you do anything or the drive just show up
I have to mount the drive each restart
sudo lsblk -f
after mounting
so the hdd is automounted but the ssd isnt? very weird
what is
rpm -qa | grep automoyeah idk i didn't even set that up
thats very old
rpm-ostree status
Solution
ujust update
yes im assuming?
yes
reboot
ok now what
drive/partition was automounted on startup
oh wow I think its fixed now
yeah, the automounter was a bit broken before
lemme move another one and try
so it was an issue with the automounter huh
I have no clue what commands you told me to run but thank you
its basically just printing system info and updating
omg thank you it is fixed now
the auto update should also work better in the newer version
thank you
fr
yw
Well the issue came back after I changed nothing with my settings
Balatro and Left 4 dead 2 are the only games the actually boot
I tried the ujust update again and nothing changes
steam play button goes to blue cancel button for a second and goes back to play
what is
mount | grep /media/lerchjr
is the drive manually mounted?
I'm not exactly sure what you're asking. I have noticed that when I boot, the eject button is not there until I actually go into the drive.
its probably manually mounted
what is
rpm -qa | grep automo
sudo udevadm info --no-pager /dev/nvme0n1p3
if you unmount the drive then do
sudo udevadm trigger --action add /dev/nvme0n1p3 does it get mounted?nope
oops one sec
let me unmount the other partition
still nothing
what is
/usr/libexec/is_in_fstab.sh /dev/nvme0n1p3
do I need to mount drive?
its seems fine
@Zeglius idk what happen lol
label is fine, type is fine, no partname leftover
and the ujust update command you had me run the other day fixed the issue until today
I didn't run any commands in my cmd or install any new programs
yeah the automounter was broken, fixed, and maybe? broke again
changed nothing
is there any other logs I can get that would help resolve the issue?
should be enough for now, wait for the automounter author now
ok thank you
🫡
SYSTEMD_MOUNT_OPTIONS=defaults,noatime,errors=remount-ro,nofail,rw,users,exec /usr/bin/systemd-mount --no-block --collect --discover /dev/nvme0n1p3
run this to mount temporarilythanks
when I click on browse nothing happens
run this again
mount | grep /media/lerchjrpartition g is gone
uhh reboot first
ok
okay one thing to note as well, only partition g does not automount properly
huh
and everytime I reboot I have to readd storage to steam to see games
games still dont launch
/usr/bin/systemd-mount --no-block --collect --discover --options="defaults,noatime,errors=remount-ro,nofail,rw,users,exec" /dev/nvme0n1p3
unmount and run thatok
steam probably forgets a drive if not automounted
reboot?
is it mounted?
What's the issue?
drive not mounted
^
udev output
did not automount after reboot or after I ran the command
the command should mount it, its only temporary mount command
before command
after
thats weird
This might be the cause, run
sudo bash -x /usr/libexec/is_in_fstab.sh /dev/nvme0n1p3 2>&1 | fpaste
And send the linkokay so, now unmount the thing and run
SYSTEMD_LOG_LEVEL=debug systemd-mount --discover /dev/nvme0n1p3 2>&1 | fpaste and see if gets mounted
but it didn't disappear
ok so, no wonder
thats not even the partition we want to mount
?
g is the partition I have my games on
formatted on linux
oh im blind lmao
missed nvme1
wait no how tf is this nvme0
tf
uhhhhhh
ok so, is this a gnome image?
yes?
yes
LC_ALL=C gnome-disksthis is what I chose
right yea
search there the partition is not getting automounted
wdym search? anything in specific I need to look through
very new to linux
thats it, wanted to see what device was it
right, unmount and see if
sudo udevadm trigger --action add /dev/nvme1n1p3 mounts itno change
pfff okay
sudo udevadm info /dev/nvme1n1pe 2>&1 | fpasteoh fcuk mispelled
/dev/nvme1n1p3 my badno clue whats going on then
you probably will need to setup a manual mount
any documentation on that?
I'm pretty much brand new to linux
even though the automounter doesn't work, when I mount the drive through files, my steam games don't launch
so I just need to get rid of that partition and shrink it back into windows to be able to play my games?
GNOME Disks Auto Mount Guide - Bazzite Documentation
Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices.
I am stuck on these parts, not sure what I'm supposed to be changing
put this for ext4? defaults,noatime,errors=remount-ro,nofail,rw,users,exec
should be yeah
and put that into where these are? nosuid,nodev,nofail,x-gvfs-show
remove and add that or just add on?
these at the start, then you add everything of the default part
ok
rebooting
ok it automounted now
steam games still don't boot
now that I've got automounting setup should I run? ujust update
that is what fixed it for me last time
If you are on the latest update, probably does nothing
yeah it didn't do anything
mount | grep /mnt/nvm
you didnt put the mount option correctly
cat /etc/fstab
change the identify to uuid
do this again
this again
sudo systemctl daemon-reload && sudo mount -a
change the mount point to
/run/media/lerchjr/g
then do thisreplace like this? sudo systemctl daemon-reload && sudo mount /run/media/lerchjr/g
no
replace it on the gui
oh
mount point one
sudo mkdir -p /run/media/lerchjr/g && sudo chown $USER:$USER /run/media/lerchjr/g
sudo systemctl daemon-reload && sudo mount -asudo systemctl daemon-reload && sudo mount -a
?
run both
in order
yeah nothing happens after that
did the drive mount
uhhhh theres two now
reboot first
then try your game again
ok
nope
it's automounted but
still no worky
mount | grep /lerchjr/g
wut
cat /etc/fstab
So maybe is proton?
the exec flag is missing
why is fstab option not matching lol
not sure if it would make a difference but I just noticed that "g" does not have the common redistributables
cant move it
try changing the filesystem type to ext4 and removing the first nofail in mount option
the mount option is broken
try to not mess in steam for now
after this do
sudo systemctl daemon-reload && sudo mount -a againok
reboot?
mount | grep /lerchjr/g
cat /etc/fstab
very weird
copy the option somewhere and put
defaults only
sudo systemctl daemon-reload && sudo mount -a && mount | grep /lerchjr/g
this is very cursed
lol
where tf is the mount option coming from
cat /etc/fstab
ok what if we mount it manually, unmount the drive then run this
mount -o nosuid,nodev,x-gvfs-show,defaults,noatime,errors=remount-ro,nofail,rw,users,exec /dev/nvme0n1p3 /run/media/lerchjr/g
then mount | grep /lerchjr/git is mounted manually now right?
unmount run first command?
unmount it then run the command
ok
try adding sudo in front
still bad usage
oh remove space before users
huh, if you unmount and run
mount | grep /lerchjr/g
is it empty
drive did not mount either
sudo systemctl daemon-reload && sudo mount -a do this again and try steam againstill not working
must be something with proton idk
close to giving up on this and moving most my games to windows, and keeping more hardware intensive games on bazzite.
i moved my games back to my main drive and they don't launch either way
bazzite was working really good for me
but idk anymore
I would not be using Hotfix unless Valve chose that for that game, and I doubt a game from 2023 would have hotfixes like that
switch to 10 or experimental, and delete the prefix and try again
i'd also just go ahead and edit fstab with the proper options not just
defaultsidk what the proper options are or how to find them
i didn't change the compatibility option
then you should check what you have set as the default in Steam Settings, Compatibility
https://discord.com/channels/1072614816579063828/1371983373773308044/1372999604857081937
what I'm not understanding is that now after I've run all those commands, when I moved the games to the partition they were working on, nothing boots now
I didn't change any compatibility settings
didn't change any system settings
for whatever reason only balatro and left 4 dead 2 are
just like they did on the drive I was trying to fix
now neither are booting steam games, except those 2
Wait so just so I understand. These games work fine and are installed in the partition you are trying to mount?
Have you already deleted the prefixes that you presumably moved over?
no so my issue at first was my games worked on my main bazzite drive and when I moved them to my new partition they stopped booting
so we deep dove into why the automounting wasn't working
couldn't figure that out
That Arma log screams prefix problems too
mounted manually and still couldn't get it to work
I moved all the prefixs to the new partition with the games
using steams move feature
now neither partitions will boot the games
did this prior to running all the commands
Delete the prefix and attempt to run a game again. Also, are you doing any sort of symlinking across drives?
lemme switch to bazzite one min
and no I have no clue what symlinking is
Oh boy
Getting this now
Stuck in a loop
Never seen this
Wait
Reboot loads to same screen
I have the option to pick a different build before it loads into that all black one but idek what to do at this point
Okay that must be it
The thing is though that drive I was messing with was not my bazzite drive
It's the one with my windows boot
Yeah doesn't matter. If you don't use nofail to mount something and fails, this happebs
So I rollback?
Don't think that's going to solve that issue
Ooooofffff
We need to get dirty with the terminal to fix this
Ok idk about that
I'm not trying to brick my pc or something
Atp I'd rather just start with a fresh install
Wipe the drive and start over
Unfortunately
Yeah ,maybe do that, and I need to rewrite the automounting, this cannot be allowed to happen again
Idk if it was something I caused or not
Like I said I'm still brand new to Linux so
Nah, this was on us definitely
Well thanks for the help in trying to fix this folks.
I truly do like bazzite because it comes with all the stuff to help the computer run better, ubuntu doesn't. I'll give bazzite another shot when I get the chance to reinstall it.
For now I'm going to wipe that drive so it doesn't cause any issues
okay now I'm getting worried
Now when I go into my boot menu
I cannot see which drive I installed bazzite on because they are both being listed as installed on the same drive
but I know that they are not
@Zeglius
I know I installed windows on disk 2, but I don't want to wipe the drive that says windows boots from and fry my shit
sn770 is the drive that says both bazzite and windows boot from
but disk 2 says c: and boot
Uh no clue, can you try entering and check what the 900 gb partitions are by the file contents
non-openable
not showing in file explorer either
idk if I should just say fuck it and wipe both disk 0 and 1 to be safe
but I don't want to wipe 1 and it not be able to boot at all
First figure out in what partition windows setups it's UEFI
Otherwise you will end up nuking your system
oh fuck
i dont see anything about uefi
it looks like disk 0 and 1 duplicated itself idek
same file sizes everything
I have 2 nvme drives 1 ssd
this is making me worried
Nah I don't think you can see that in the partition manager
There must be a command or something
idk I've never gotten this deep into tech issues
I found it
but I have no clue why C: is split from the boot
idek if that is right
not quite sure
Well yeah, that's usually how it is
usually isn't the C: kept with the partition of windows install?
Nope, usually is the UEFI partition, C:, and the recovery one
so I would assume disk 0 is bazzite
okay I recovered disk 0 fine
disk 1 is the one I'm worried about
does anyone know if I do wipe disk 1, could I just reinstall windows on the same drive and not touch disk 2, which would keep the C: functioning properly?
also trying to understand how the C: got split from the disk it was on
.. that's an odd partition layout for Windows..
thats what I was thinking
I'm always used to seeing the c: being included with the boot
I'm just going to leave it like this for now, while it is working fine