How to fix infinitely restarting `systemd-journald` job at boot?

[rokejulianlockhart (Mr. Beedell, Roke Julian Lockhart)]

@gnwiii, many thanks for the verbose diagnostic instructions. Fortunately for me, I merely reinstalled the OS, as undermentioned:

@rokejulianlockhart

I have reinstalled the Fedora 41 KDE Spin

However, should this occur again (it may, for similar has occurred in the past, for me) I shan’t forget to provide this information.

Irrespective, for posterity:

@gnwiii

If your console is usable (e.g., using the grub editor to add <space>3 to the end of the kernel command-line, you should be able to check space (note that df is not useful on btrfs (and really should warn users who run df on a btrfs filsystem) and also do a safe shutdown or restart.

If console is not usable, you can boot a Live Installer, mount the system root drive (e.g., with Gnome Disks) and check for filesystem problems.

If, by console, you refer to the rescue kernel TTY1 CLI (rather than GRUB2’s CLI, accessible via Esc from its pre-boot TUI), then it was. I could even access journalctl, and systemctl reported that it was healthy. This is presumably as perplexing to you as it was me.