Arch Linux

Rhombert

Member

Registered: 2023-09-23

Posts: 1

Dependency errors in File System Check when booting

Dependency errors in File System Check when booting

After updating my system, the next reboot began to throw that it fails to start the File System Check, and is unable to open a terminal as the root account is locked.

Full error below:

[FAILED] Failed to start File System Check ■adae39-dd42-48d7-9b80-9c2c5f99b357.
[DEPEND] Dependency failed for /sysroot.
[DEPEND] Dependency failed for Initrd Root File System.
[DEPEND] Dependency failed for Mountpoints Configured in the Real Root.
You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, or "exit" to continue bootup.

Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.

Press Enter to continue.

I chrooted into the system through a recovery USB to try the recommended

journalctl -xb

command, and the only output was

Failed to get boot id: Function not implemented

I tried to run

mkinitcpio -P

as well, which did run through and complete, but upon rebooting into the system normally I receive the same error listed above.

loqs

Member

Registered: 2014-03-06

Posts: 18,929

Re: Dependency errors in File System Check when booting

See https://bbs.archlinux.org/viewtopic.php … 1#p2113821 to unlock the root account in the emergency shell.
Then check if /dev/disk/by-uuid/dae39-dd42-48d7-9b80-9c2c5f99b357 exists.
If it does not please post the output of the following after chrooting in:

blkid
parted -l

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,093

Re: Dependency errors in File System Check when booting

There's no journal on the iso and you're not getting that incident synced onto the journal of the installed system.

[FAILED] Failed to start File System Check ■adae39-dd42-48d7-9b80-9c2c5f99b357.

From the iso boot, WITHOUT chrooting into the system

lsblk -f | curl -F 'f:1=<-' ix.io

You effectively want to fsck the system w/ adae39-dd42-48d7-9b80-9c2c5f99b357 except if it also doesn't show up during the boot.

Running mkinitcpio won't help you here (certainly not w/o chrooting) but for the locked root account see  eg. https://bbs.archlinux.org/viewtopic.php … 1#p2113821

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc