Bazzite-deck slow death until I can no longer boot
So I discovered today that HDD was enabled on deck by discovering the button combo by accident.
- I enabled the ruby (i think that's what it was called) scheduler
- over the course of the next hour or two my games and steam started get noticeably less responsive and opening the steam overlay menus would cause a lag spike.
- then the games just simply stopped loading at all at loading screens
- then they would not open at all
- then steam became unresponsive and slow even with no game open
- disabled the "ruby" scheduler because that's the only variable that changed so it was most likely that
- then desktop mode would not open
- and now when booting the login screen worked fine but the system crashed the second steam came onto the screen
- now it straight up doesn't boot at all
I rebooted about a dozen times throughout that whole process, I just don't recall where in the process
- I tried booting the previous update to see if that did anything but still just permanent black screen after grub
I was concerned that the slow rollout of problems was some sort of GPU failure as that's how it tends to look on pc hardware.
- so I then tried booting into another live OS off of my USB and everything works perfectly fine
So either bazzite shredded itself to pieces, but I wouldn't know how to diagnose that, or my SSD completely shit the bed... but then grub would also not work in theory
Thanks for reading
Solution:Jump to solution
Yeah it appears to just be that for whatever reason, steam overlay recording (or whatever it's called), just never stopped recording despite the SSD being completely full
So Ideally the solution here would be to implement some sort of disk fill limit for everything outside of the OS so that if you fill it, the OS won't stop being functional. It does warn you on desktop mode that the disk is almost full, but if you just fill it faster than you get to desktop, then this happens....
27 Replies
did you try the
ujust fix-reset-steam command from a terminal? ctrl+alt+f4 to get into a terminal sessionBazzite-deck with no current way to plug in a keyboard
hmm, do you have like a usb-c hub or something
or usb c-to A adapter
Oh duh
Iβm panicking sorry
there's lots we can poke around with
with a keyboard
I logged in successfully and I got as big warning saying low disk space
terminal appears to work perfectly fine
writelastlog failed: no space left on devicedid steam recording fill up my ssd so much that the OS stopped functioning
it technically didn't did it?
uhhmm, perhaps
fastfetchplease>cleared trash from cli
>immediate bazzite boot sound
this is something the maintainers can & should address
how did that even happen π€
please hold. Booting into desktop and running bleachbit just to reclaim as much as possible
before it fills up the last 2mb of disk
xdddd
oh wow is it that little?
left
thankfully the filesystem reserves space for itself
were you running a proton log on one of the games you were playing? those can get enormous when you play a long time
steam recording
somebody should set up cgroup disk quotas
for normal users
such that at least the login screen will load in case of a full disk
how big is the ssd in your steam deck?
1tb
I just filled it too close to the max and then recorded video
so it didn't have anything to do with the ruby scheduler in the end?
I mean the disk is full so yeah that appears to be completely unrelated
hm
The timing on that tho
was so perfect, the wrong dev was gonna get my bug report
Scariest software crashout I've ever had
Other than every time I updated ubuntu to then boot up to kernel panic
Windows isn't much better in that regard, i read a report about how Windows 11 completely blew itself up and was unusable because OneDrive decided it had to sync 280GB of files from a phone to a PC. It's a horror story. if you wanna read it: https://www.osnews.com/story/143376/dark-patterns-killed-my-wifes-windows-11-installation/
so was the SSD in the end just not SSD failure
Let me clear some space and reboot a couple times just to be sure
Solution
Yeah it appears to just be that for whatever reason, steam overlay recording (or whatever it's called), just never stopped recording despite the SSD being completely full
So Ideally the solution here would be to implement some sort of disk fill limit for everything outside of the OS so that if you fill it, the OS won't stop being functional. It does warn you on desktop mode that the disk is almost full, but if you just fill it faster than you get to desktop, then this happens.
seem this error many times even to the point where it told me i had 0% available never had it this badly full though
to where it fails to boot
well not fails to boot
but fai;s to load the login screen