Bazzite No Longer Boots After Update
Hi all, after performing an update the system rebooted and is now stuck at the attached picture. I can't boot into bazzite or access the grub loader it seems. I also haven't changed anything in the bios such as secure boot.
any idea what could be causing this? do i have to reinstall?
22 Replies
Hey there, I have no idea, but I would do a reinstall. Just make sure that you backup your data from the live environment or something like that. Sorry, not super helpful, but good luck anyways :)
Not a Bazzite user, but AFAIK, you can access GRUB by repeatedly pressing the Esc key (on UEFI systems) or the Shift key (on BIOS systems) right after pressing the power button to turn on your PC. I assume you've already tried that?...
I always saw immutable distros being promoted for having an easy way to rollback if the update causes any errors. Seeing you being unable to even access the GRUB menu is strange...
Try this method a few times. Maybe you can still do a rollback
@Uncle Psymon thanks i'll try that if i cant get into the grub loader as @abub described!
Tell us how it goes. I'm just curious to know if Bazzite really messed itself up sp hard that you can't even rollback via GRUB
Reinstalling should be the last resort. There must be a way to revert the update
By the way, how were you trying to access GRUB before I texted here?
just pressing ESC repeatedly
i will try with a wired keyboard today instead of wireless
Okay. You can also try searching for another methods, if there are even any
Esc or Shift keys are the only thing I've heard about
Thanks I'll try it later today and see what happens. I'll keep the thread updated
Ok I couldn't get into grub no matter what I tried. The bazzite recovery option also said no Linux partition found. The only option was to delete the existing partition and reinstall bazzite 😦
I'm not sure how this even happened from a simple update.
@abub ^
I wonder how this even happened...
You can't even mess with system files, since it's an immutable distro. Were you layering too much packages with rpm-ostree? Do you remember doing anything to your system?
Nope I had nothing extra installed and this happened after an update directly from the settings in steam mode. I'm just as baffled honestly
This looks like a corrupted grub install. Could've been caused by a Windows update, or something else. At that point its best to just go for a full reinstall, because recovering grub is a lot of work and not easy for the average user.
If you have an external drive, you can still back up your home folder though if you want to keep your games and save files. This can be done by booting any live CD and mounting the Btrfs partition and then copying over all the files to an external.
Hold up.
@VonSwoopington were you using JUST Bazzite? Or you had a dualboot setup?
I also couldn't boot since today. Gets stuck on a blinking cursor after the splash screen. However I could access the grub menu and have booted successfully by selecting
ostree:1
Sorry just realised there is another thread more relevant to what I experienced.what device?
if you updated through game mode (In steam "System Update") and were on an older version of bazzite (april) then you likely ran into the bootc bug
Yeah I think there was a hotfix. Updated again and all is well.
don't update it through steam again and you should be good
just gotta update through desktop mode "System Update" (the shortcut). It was fixed in a few versions again, so shouldn't happen again.
Non-dual boot system with only bazzite installed. It's a dedicated PC for bazzite so no windows
No windows installed. This wasn't a dual boot system
Oh. Can't even blame Windows then
:glorp:
Yeah I guess this will remain one of those weird mysteries. I literally can't pinpoint anything that could have triggered this. I ran hardware tests and benchmarks and everything is as expected
okay just to be sure: you didn't delete the ext4 partition by accident did you?
that would trigger it
Nope. All I did was tell bazzite to update from the steam UI. It downloaded the update and rebooted into that message 😔
And there was no chance you inserted some usb stick before updating that could've caused to boot to something else? Because stuff like Ventoy can cause this error too
No, nothing at all. no hardware changes were made within the last 6 months as well.