My filesystem was acting up: could not apply VSCodium settings because “No space left on device” although I still had 11 GB. Could not install fix software because DNF complained the space is lacking. Decided to reboot. Booting is getting stuck here.
From rescue option of GRUB:
None of the posted photos help understand what’s going on. We need to see a full journal, which is not exactly the easiest thing to get when things start to misbehave.
I suggest editing the GRUB entry, remove rhgb quiet and then take video of the boot process. By the time we at startup failure complaints, the cause is long scrolled by so screenshots won’t help.
It’s vaguely possible booting with the following options will also help:
remove rhgb quiet per above, and also add fstab=no systemd.volatile=overlay
This will cause fstab to be ignored, therefore assembly will not be normal, including the user home. All modifications are redirected to a volatile (in-memory) overlay. In effect the root file system is mounted read-only, like a Live USB stick.
At least we might get access to the full text journal via journalctl and see if this works or fails and where. And you also have access to older journal entries via the journal database located at /var/log/journal to see what might have done wrong in a prior boot, using journalctl -b with -1, -2, -3, etc, to go back to prior boots.
Due to aforementioned problem of filesystem thinking it’s full, no entries were written on May 26th boot attempts. Right after May 25 shutdown follows May 30 boot when I deleted some files and clicked “fix filesystem” from boot image.
