Disk Write Error for Steam Linux Runtime 3.0 (sniper)
I'm unable to launch any games on steam due to a disk write error.
I've tried using ujust fix-reset-steam and this is on a btrfs drive.
136 Replies
hmmmmm
maybe running Steam from the terminal
& try installing sniper
unfortunately the disk write error is when trying to update sniper

oh
what if you remove/reinstall it
how would i go about that? i tried uninstalling from steam client but it didn't work
yeah but that preserved apps weren't they?
the runtime is just a Steam app
not anything too special
you just search for it like a regular app
ok I can see it in the library now. it doesn't uninstall. verifying integrity gives the same disk write error
oh
the obky soecuak thing about the runtime is that every other Steam app on Linux uses it
either directly or indirectly
hmm... maybe there's a way to do a full uninstall/reinstall of steam?
i think just getting rid of the runtime & reinstalling it should work but apparently we have to do that manually
it should be where every other app on the internal drive is
i see it in the common folder, but can't delete it
oh yeah
that may be related to the problem
if you can't touch it Steam can't either
if Steam can't touch it Steam can't update it
might be a permission issue
should be simple enough to fix
sudo chown -R ~/.steam $USER:$USER
this'll give you access to everything in the Steam folder
which is normal to have
this gives you the right to change permissions as well
so if you can't delete it stillsorry, i'm new to linux. why is this giving invalid user?
oh my bad
i flipped around the user & folder
ah there we go it worked now
sudo chown -R $USER:$USER ~/.steam
this was correctty
can you delete it now?
no :BibleThump:
oh
gotta give yourself write permission then
making progress tho. i put it in trash, and it gives a specific file I can't delete. i spam delete that until it disappears, rinse and repeat
or that, write permissions XD

owner needs to be view & modify
sure thing. it's showing me as owner, and can view and modify. i checked apply changes to subfolders as well just in case.
Steam operates as you
looks like even rm -rf doesn't work. it's a read only file system
hmm
naje extra sure you're targetting the right thing
though bazzite won't let you delete anything too important
Configuration file "/var/home/User/.config/dolphinrc" not writable.
Please contact your system administrator.
now i get this when opening dolphin :monkaS:
i think my OS might be borked
might just be time to reinstall from scratch
or rebase to earlier version at least
hnnnn
what happens if you
sudo ostree fsck
should verify the bazzite files themselveserror: Remounting /sysroot read-write: Invalid argument
what if you cd to
/ostree/repo
& do it againsame
yeeeeeeah
this does seem like a filesystem problem
sudo btrfs check
might help
you need to give it the drive to check i thinkit's saying currently mounted, use --force
with that said, I can screenshot the disk if that helps

does filesystem parition 1 and 2 also need to be btrfs?

no
those are fine as they are
the fat32 one is where the BIOS looks for bootkiaders
the EXT4 one stores kernels
BTRFS stores everything else
oh
my bad
the drive would need to be unmounted
is unmounting possible for the OS drive?
yes & no usually no you have to do something at boot
to make it possible
it's tied to the ext4 partition above actually
basically Linux boots in stages
gotcha. so it goes from bios -> kernels -> everything else
BIOS > bootloader > kernel + initrd > initrd finds the rest mounts the main drive > the rest boots
we can drop into the initrd
before the real drove is mounted
& do the check/possibly a repair from there
how do I get to initrd? currently in bios
gotta change stuff from the bootloader
I got to rescue mode
didn't explain what the initrd was
it's basically a tiny Linux system
has a few programs on there
& some drivers
just enough to mount/check the actual drive
it;s just a zip file basically
the bootloader loads it for the kernel
it's meant for cases like this
Linux rescue mode?
or grub rescue mode?
grub
I'm back in the menu before that tho, I see intrd
oh you pressed E at the grub menu?
yes
grub Grand Unified BootLoader
is the bootloader
& the place you are at is where you should be
you see the
linux
lineyup I see it
that's where all the magic is
the first "word" after linux is the location of the kernel
the rest is text passed to the kernel
telling it stuff
i think you just add
rescue
in there
to make it drop you into the initrd
& ctrl + x to boot
rescus could really go anywhere after the kernel path of courseok it's in rescue mode. press enter for maintenance I assume?
yeo
now you can check the system drive
btrfs check
like before
except this time it won't complainone sec, I forgot the drive name, gonna take a pic
if you had it labelled you can do
/dev/disk/by-label/LABEL
ain't no way... drive is currently mounted, use --force
hmm
might not be in the initrd after all
if you are we can simply unmount it
with
umount NAME
ok I'll give that a try
unmount command not found
yeah people commonly make that mistake
it's
umount
oh no N
without the n
it's without the N for historical reasons
back in the day
old UNIX systems couldn't fit
unmount
still showing mounted
ok
as long as the command didn't fail
that's good
just gotta run it a few times
i think
the drive is mounted in more than 1 folder
target is busy apparently
ah dang it so not in the initrd still
I can try emergency mode instead of rescue
it wouldn't be busy if you were
i think both of those are in the actual system
doing
init=/bin/bash
may make it drop you into the initrd
we discovered this by accident
a bit agothis is from rescue menu or grub menu at the end of Linux line?
yup same as before
you can hit ctrl+e to jump to the end of a line
in grub
still mounted :coolfingergunscry:
ok
try this
rdinit=/bin/sh
no such file or directory in this one
so it's either mounted or doesn't exist...
oh there has to be a way to do this in a non jank way
gonna look that up
it's different between different Linux distros
but there's usually a supported way
btw thanks for helping. it's already been 2 and a half hours
to do it
i just like helping people
appreciate it
& this is an annoying problem to have to deal with i just can't give up trying to fix it
at least if anyone else runs into this in the future they can look here
i think
rd.systemd.debug_shell=1
is the supported way
same thing you just add this to the linux lineok
hmm. that just ended up booting the computer like normal
oh there's yet another way
this one is extra official
ooooh fancy
https://www.man7.org/linux/man-pages/man8/systemd-debug-generator.8.html
it's described here
systemd.break=pre-mount

oh actually it's
rd.systemd.break=pre-mount
do I still need "rescue" in there or just as is?
no need for rescue
k
this also just ended up booting like normal
oh
perhaps fedora/bazzite doesn't use systemd as init in the initrd
i can explain what this means
basically init
is the first program the kernel starts in a system
there's one in the initrd
& one more in the real system
the first init in the initrd is the program that actually mounts the real system
& does all that stuff
the 2nd init is what starts everything else on the real system
like the login screen the networking stuff printing stuff etc
so we're trying to set a break point in that first init before it mounts the drive?
and since it doesn't use systemd it just ignores the command and proceeds as normal
yes essentially a breakpoint
well the 2nd init is systemd just maybe not the first one
though i could have swarn systemd was the first init on fedora/bazzite as well
but still post mount so it wouldn't be able to add a break point to somewhere already passed?
yes the 2bd init is on the main drive so it isn't loaded before the drive is mounted
gotcha
you're basically getting everything here
thanks to all of this initrd magic the real system could be anywhere
someone was crazy enough to set it up on google cloud
also before mounting the first init does usually check the main drive
but not in this case
since you're using btrfs
an AI summary poped up when i searched for the fedora way
it says you just add
rd.shell
ok I'll give that a shot
did a normal boot
dang it
wait i have fedora dualbooted
so i can find the proper thing
& just tell you
nice
the shell is documented here https://fedoramagazine.org/initramfs-dracut-and-the-dracut-emergency-shell/
Gregory Bartholomew
Fedora Magazine
InitRAMFS, Dracut, and the Dracut Emergency Shell - Fedora Magazine
Learn about InitRAMFS and how to use Dracut and the Dracut Emergency Shell to manage it. You will also learn some basic troubleshooting.
but it isn't really explained how to get into it
unless something fails horribly
in which case it'll drop you there after trying & failing
to mount the actual root
what about checking the partition from a live usb instead of rescue mode?
yeah i guess that works
but it requires more stuff
like a flash drive
& an ISO
in this case those probably aren't hard to get
Makes me think I should roll my own system rescue live system.
i wush dustris had a better initrd recovery mode
you could do so much fancy stuff
though fedora atomic does have
ostree
in there i think
so if push came to shove you could reinstall it using the initrd
alone
as long as you had a system image stored somewherefrom grub menu?
either locally or just get it from online
do you have a bazzite installer? kd di the drive check from there?
not atm but I have a spare USB. can put it on there and get back to u
quick question, is it normal to have a bazzite ostree 1 and 2 in grub menu?
or rather, 0 and 1
not sure but having 2 versions is normal
maybe ostree 1 will help. worth a try
it's a very famcy feature
powered by the initrd
it has stuff in there to not only mount the system drive
but also look for system files in a subfolder
thus enabling multiple systems on a single partiiton
you can technically have a system without an initrd where the kernel itself finds the system partition & runs init on there directly but you'd need filesystem & other drivers to be built into it
& bazzite's fancy boot wouldn't work without it
I think I'll just backup my files and do a fresh install.
if that doesn't work then idk
Also note its unlikely btrfs has failures - it might be your disk that is failed
the drive itself going bad?
Yes, it can happen
true
Basically:
try a live system and use gnome-disks to review the SMART data, not every disk has this available.
Btrfs scrub can verify each bit of data/metadata and if it has errors in data it means you probably have disk failure imminent. This likely has nothing to do with bazzite
was just hoping it isn't that
smart os a self diagnostics thingy
I had a buddy recently that had drive failure on his windows 11 system, he asked me to look at it. I tried some windowsy things to fix it, and nothing worked. I booted a fedora live usb and it actually popped up and said SMART shows disk failure
yeah Windows confuzzles me
My only thought about it was that windows should have seen and reported the drive failure to him too, but it didn't. It was just apps not working right that clued him in something was wrong
it kinda has this concept of hardware abstraction layers
dealing woth low level stuff like this is what the HAL does i guess
Sorry not meanign to derail your help post @Boozle 😄 please ping me if I can help you fix it if im not on the road ill see what I can do
so it's not really front & center in Windows
no worries. i'm just setting up the usb drive so i can reinstall from scratch
WMI Windows Management Instrumentation should have info about this i think
I haven't used windows since Win Vista, so im usually lost when I use it.
has there been a big influx of new users? for me, i've been using windows forever, but support is ending for 10 and i didn't want to transfer to 11.
last time i used it was when i decided to try & make a script to help with dual booting WIndows on the deck
i did mostly succeed
a few people did use it
I don't have numbers but I doubt people will migrate en-masse.\
probably not. most people don't even build a PC, so they'd just use the pre installed windows anyway
I would say Linux is better in every way except maybe app compatibility. It's a non starter if you need to use photoshop or some windows only proprietary software, or some really specific hardware. Or games that use kernel anti-cheat.
I switched from Apple, and I can say Linux is better in every way. Better looking, faster, plays more games.
I use Bluefin to run my business, so.
guys guys
i figured out hiw to drop at the initrd
read the fedira manual on it
& tested it
rd.break=pre-mount
worked
was able to check my drive no problem
so learned sinething today
i like Mac OS' recoverability
they can just boot off of wifiI did always like that feature. However, Mac OS is so sluggish.
i'm kinda disappointed general Linux doesn't have something like that
Android has it's recoveries
it's not netboot but still nice
Linux distros do tend to have ISO booting functionality which is nice & similar enough to netbooting
no need to have a drive to just boot a distro
by ISO booting i mean if you just extract the initrd & kernel load them & tell them where the ISO is & they'll just boot that
debian derivatives & Nix OS can do this
not sure about arch
yup fedora has the same thing

I figured it did. I'm not that smart any more, I leave fancy stuff to the kids
Id be using arch if I cared about any of that 😄