Bazzite boot error
2 mornings ago I attempted to boot bazzite and found it booting into emergency mode. I was directed to the pin to fix tree corruption using gparted. I followed it (with help from a user here, thank you @biebel!) but it did not fix my issue. After this, I was directed to use the liveISO bootloader fixing tool, which I did. It also has not solved my error.
It is worth noting: If I boot from the liveISO, I can clearly see all my bazzite partition files. I can see them and look through them, they are all there and just fine as far as I can tell.
Is there a way to fix this error? To be clear the error message I receive on boot is as follows:
"You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, systemctl reboot" to reboot, or "exit" to continue bootup.
Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.
Press enter to continue."
Then I press enter and:
"Reloading system manager configuration.
Starting default.target"
Then it just reprints the previous message or sometimes it'll say "starting default.target" and just hang for awhile.
My system for reference:
MOBO: MSI MAG B550 TOMAHAWK
CPU: AMD RYZEN 7 5800X
GPU: NVIDIA RTX 3070 8GB
RAM: 2x16GB DDR4
STORAGE: BAZZITE PARTITION - SABRENT ROCKET Q 2TB
WINDOWS PARTITION - SABRENT ROCKET 4.0 1TB
3 Replies
Did you add any custom drives to your /etc/fstab file (via editing the file, or gnome disks or kde partition manage)? If you format a partition, or remove the drive, and you missing the nofail flag you can get stuck in emergency mode.
If that is your issue, I do have a video for solving it https://youtu.be/-2wca_0CpXY. If not, then I'm not certain why you are getting emergency mode
Mike's Tech Tips
YouTube
How to get your Linux system out of emergency mode
In this video we'll look at the scenarios that get Linux into emergency mode and the process of fixing your fstab file to get it out of emergency mode
timestamps
00:00 Introduction
00:31 Scenarios that cause Linux to go into emergency mode
00:54 The current issue
01:12 Summary of the solution
01:35 Getting into Grub
02:13 Editing Grub at boot t...
this may solve your issue?
https://discord.com/channels/1072614816579063828/1392630488241410191/1392682408544829470
check the end of the output of
journalctl however
see if you see something mentioning "log replay"