Hello, since applying one week of upgrades yesterday, I have to new kernel 6.17.4 in Fedora 42, but it cannot boot. It immediately goes to emergency mode, but it does not even allow me to open an emergency terminal, as it fails to load “system manager configuration”.
Fortunately, I can still boot with the previous kernel 6.16.11. Do you have any hint on what could cause this, or how to get some more useful debug information, as there is nothing in the logs.
Here is a picture of the message (after I press enter, the message repeats) and the list of available kernels.
6.17.* runs w/o issues on many systems. 6.17.5 should be available, try to update the system.
also, please post output of ls -lh /boot/initram* , df -h /boot and inxi -Fxxz as preformatted ‘</>’ text.
If 6.17.5 fails to boot, then reboot with 6.16 and see whether output of journalctl -b-1 (-b-1 means the previous boot) begins with a line containing the string Linux version 6.17.5-200.fc42.x86_64
if so, then save output of journalctl -b-1 --no-hostname --no-pager > a_file_name and post it here.
It was the case of a missing comma in /etc/ftab causing /home to not mount. I do not know how it worked before, nor why it crashes so catastrophically without giving a recovery terminal…
the recovery console requires an unlocked root account. If you run into a similar situation again, then boot with another kernel (if possible) and unlock root with sudo passwd and set a password for the root account.
I see, I had no idea that “root account is locked” just meant that no root password is set. I guess I could have read the manual (to be fair, the manpage of sulogin is not particularly clear either).
I assume you didn’t enable root. If you can boot a Live USB installer you can use journalctl to view the journal on the failing system. Fedora has an introductory tutorial for journalctl , and there are other good online tutorials. Always check the journalctl man page to verify commands found online.
-l, --lock
Lock the password of the named account. This option disables a password by changing it to a value which matches no possible encrypted value (it adds a ´!´ at the beginning of
the password).
-u, --unlock
Unlock the password of the named account. This option re-enables a password by changing the password back to its previous value (to the value before using the -l option).
-S, --status
Display account status information. ......
Thank you for this and the thread; my issue was different, but had some BTRFS subvolumes originally from old Fedora installs, and apparently added compression manually.
Not sure how I managed it, but ...compress=zstd... had a hanging : and no level specified. Adding the default level of 1 to make it compress=zstd:1 no allows me to boot into 6.17 kernels.
I am also not clear what differs there for 6.16 kernels by comparison, but it was also related to an FSTAB entry issue for me.