"Failed to start systemd-fsck-root.service" and "Entering emergency mode" error

After some hurdles, I recently installed Qubes on an external SSD. Everything was running perfectly. While converting some PDFs in disposable vms, the OS suddenly froze, and I got some kind of error that was just a bunch of squares with no readable text that wouldn’t go away. I rebooted, and when I tried to enter my disk encryption password I got some kind of dracut error:

[    2.931246] dracut-cmdline[205]: Warning: USB in dom0 is not restricted. Consider rd.qubes/hide_all_usb or usbcore.authorized_default=0. 

Generating: "/run/initiramfs/rdsosreport.txt"

Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.

Please Enter for maintenance
(or press Control+D to continue):

I searched on the forums to see if anyone had this problem and it seemed to be a wrong password. So I rebooted and tried to enter a wrong password deliberately, but when I do this it just blanks the password and I can try again. When I enter the correct password, I get the same emergency mode screen.

I tried the troubleshooting instructions here as recommended on another relevant post: Autostart troubleshooting | Qubes OS
but the same thing happened.

When I type journalctl and scroll down to the final lines, I see the following:

I managed to fix the issue by booting into Fedora and manually checking and repairing the filesystem of each qube. But now I’m concerned - what could have caused the filesystems to be damaged like this?

Since you’re using the external disk, then maybe it was disconnected during Qubes OS usage and some data failed to write on the disk causing this error.

1 Like

Thank you! I think that might be the case, it would make the most sense to me. This put my mind at ease.