Comment by partomniscient

I spent ages submitting the bug report with various log files, /etc/fstab that worked vs. the one that didn't. Detailed steps to reproduce, specific kernel versions, snapshots of /etc/ /usr/share/etc and so on. What the problem was, how I resolved it.

Also found someone else that had experienced the same: https://old.reddit.com/r/linuxquestions/comments/t6795f/emer...

Created an account to submit it all to Fedora(/Redhat/IBM). And it just got marked wont fix. Apparently the filesystem guy didn't think it was a filesystem problem (despite being caused by fstab) and just closed it.

Apparently getting stuck in the below loop is an acceptable response due to a typo in /etc/fstab.

Reloading system manager configuration. Starting default target. You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, or “exit” to continue booting.

Cannot open access to console, the root account is locked. See sulogin(8) to continue.

Press Enter to continue.

Cannot open access to console, the root account is locked. See sulogin(8) to continue.

Press Enter to continue.

etc.