I can't boot my install anymore.
Hello everyone, it's my first time posting here and I'm very new to Bazzite, so I hope I'm posting in the right place.
I need help because it's no longer booting and I was wondering if there was a way to fix it without having to reinstall it all over again.
Attached images of the error screen.
Ask me for any additional info and thank you very much for the help!
Solution:Jump to solution
I see your correct UUID in there. It's just bugging out because it's trying to read from a directory that doesn't exist
25 Replies
Reupload of the second picture because I sent the blurry one by mistake
Have you tried booting into an older image via GRUB? rpm-ostree should save previous images there
Yes, I tried all of them but the error is the same
Try running
journalctl and see what it spits out
That should provide logs for what's happening
If the older images aren't working either, then it tells me it's not an update issue
Also run systemctl --failed and see if there's any units that failed
Ah, scroll down on that log with the End key on your keyboard :)
Oh sorry, I didn't realize there was more xD
No worries
Yeah, as I thought, os-tree can't find your root file system somehow. I'm wondering if the boot files still exist, or if the UUID for the root file system changed ID. That's very strange.
If your sysroot is mounted (which it looks to be), are you able to run
ls /sysroot/ostree and show me what's there?Damn, how did I manage to do that xD
It doesn't seem to be an update causing it since the old images don't work either
Okay uh, for some reason it's trying to read from the boot.1 directory when you have it listed as boot.0 instead...
Check the contents of both boot.0 or boot.0.1 and see if there's anything that matches the UUID printed
This is what I have for instance
Which command do I use to check the contents?
CD gives me a no such file or directory on boot.0
Just
ls /sysroot/ostree/boot.0.1/default should do
sry, had to retype the command, heh
If there's stuff in there, then try running
ln -s /sysroot/ostree/boot.0.1 /sysroot/ostree/boot.1
That will create a symlink from boot.1 to boot.0.1, which should hopefully fix thisSolution
I see your correct UUID in there. It's just bugging out because it's trying to read from a directory that doesn't exist
You can confirm the symlink exists by just
ls /sysroot/ostree and seeing if boot.1 exists there. :)Alright it did boot into gnome!
Thank you very much!
Glad to hear! I'm going to ping @Kyle Gospo and @EyeCantCU, as they might know why this happened better than I ever could
It's completely possible an update wasn't applied properly. I also noticed that
nvme2n0 encountered an I/O error which can be representative of a failing driveIt's strange because all of the Nvmes inside the PC are less than 6 months old, I'll check for any problems later