Not sure what’s happened here. I was messing with the Witcher 3 and different TDPs using the HHD overlay and was getting a lot of system lock ups (probably 4-5 reboots). Now on the latest reboot it no longer boots into Bazzite. I’m not very skilled here with what to do next, but I get a “Generating /r/intramfs/rdsoreport.txt” message. Then
"Entering emergency mode. Exit the shell to continue.
Type “journalctl” to view system logs.
You might want to save “/run/intramfs/rdsoreport.txt” to a usb stick or /boot
after mounting them and attach it to a bug report.
Press Enter for maintenace
(or press Control-D to continue)"
Control-D just continues to loop to this same prompt.
DO I need to mount things again? I don’t know how to read the journalctl that shows at all, nor how to save it for anyone else to view. Really hoping my Bazzite install isn’t messed up for good.
It doesn’t look good. But it is not the /boot that is failing; it is /sysroot.
You have a bad block in there.
Maybe you could try disconnecting the external drives and reboot again. It happened to me once.
Before trying this, power off your rig, cool it down, and power it back on.
Ive done multiple reboots from cold. Left it overnight off and this still happens. Perhaps my original install was never that stable? Ive had a decent number of freezes forcing reboot so maybe I should just start over and install from a new thumb drive?
Just be sure that you wrote the ISO image to the USB drive using Fedora Writer. Also, choose to verify the media before proceeding to install.
PS. One of my installations failed because I didn’t use Fedora Writer.
PS2. The Silverblue and derivatives are pretty solid and stable once you got them installed right.
I used Rufus on the legion go itself to write the Bazzite iso to a samsung USB-C drive - the install went through without issue, so not sure what’s up. I do know one thing, performance in Bazzite is vastly better than windows for most games, so much so it’s dramatically better. It was fairly stable for a few days of use before this error. I guess I’ll give it one more try.
When it comes to writing an ISO image, we just follow procedure and recommended practices written by others, i.e., Fedora Writer. It’s been proven than burning an image with other image writers, results are unstable.
I had followed a guide by some YT account on doing the dual boot install, but I will get a fresh USB stick never used, and use Fedora write, I really want bazzite to be a stable daily driver, it felt that good to use compared to win 11.
I’ve used Fedora Writer now on 3 different machines, Including the Legion Go itself, another Win 11 desktop, and my Macbook and every time when I try to boot I’m getting a “media check failed” message at 4.8%. I’ve tired 3 different thumb drives as well. Balena Etcher is passing the tests - what gives?
Definitely, something is wrong. There is no stability. The fact that 3 thumb drives written with one software pass while none with FWriter doesn’t, tells me that an error is being bypassed, or going undetected.
Let me put it in another way: if the gold standard for stability of boot and sysroot were Fedora Writer installations, what would be your decísion?
Try downloading the Fedora ISO again
Uninstall Fedora Writer, download a fresh one, and reinstall
