At the beginning of February, I left my laptop running overnight like normal (no sleep or hibernate) and when I moved the mouse to activate the monitor for the lock screen, it stayed off. No input from keyboard or mouse could get the screen to activate (including CTRL+ALT+F2 to try to get to console). I had to hard shut down with the power button.
When I turned it back on, I couldn’t boot with a Btrfs corrupt leaf error. The same error happened when trying to boot from ostree1 instead of ostree0.
Separate posts because only one attachment per post for new user.
I booted a Fedora KDE live USB to try to mount the partition. I clicked on the drive in Dolphin file manager, entered my LUKS encryption password, and got this error.
Had a similar situation before: Kernel panic after power outage - #3 by IZ-7 but when the answer came up I had already reinstalled Bazzite from 0. Seems like many linux systems are vulnerable to forced shutdowns.
When I woke up, the power indicator on my laptop was lit, meaning the machine was running still. Even if the power went out when I was asleep, the battery wasn’t dead when I woke up.
The problem could be some form of disk corruption. Are you able to go to bios to do SMART tests (both long and short) with the drive in question? This will at least help rule out hardware failure for the disk. Depending on the bios settings some computers may power back on after temporary power loss (although that is not usually the default setting) please also check that.
Are you using the rescue mode with the live media usb?
I don’t see any SMART or power loss options in BIOS. I ran smartctl from the rescue mode Fedora KDE live USB.
This is the output for the unmounted drive containing dual boot of Windows 11 and the broken Bazzite. The Windows install seems to be working normally when I log into it.
Well, I guess the one piece of good news is that it is not likely to be a drive hardware issue based on the SMART test. I am going to ignore the temperature sensor reading from the live media which appears a bit off in one part of the GUI.
Just as an aside, what GPU is the laptop equipped with? Is it Nvidia or AMD? Nvidia has had known issues with sleep functionality…not sure about in this case as laptop was not asleep with screen just off…but you never know.
This is a hunch at this point…but perhaps an update occurred and was set to be applied for the next reboot, but then for whatever reason the system hung/became unresponsive and now unfortunately after a forced shutdown there are a bunch of errors popping up.
I have found a bit of info on the first appearing error:
Perhaps starting the d-bus service with the original installation (not live media) with the terminal might move things along a bit….
but to be honest, I really recommend filing a github issue for this one before doing anything else, and include the logs with it.
You may need to use chroot /mnt/sysimage for terminal commands to work in live media per the video below…again I would be cautious about doing anything further without more expertise from someone else.
-at 2:04 on video below (read text) this is a short guide from 2020 (I can’t say how relevant or useful on atomic this will be, but here it is anyway):
