[solved] stuck in "dependency failed for File System Check"

nenoro · 2025-03-29 22:03:22

Hello

So i have this issue on my T460 before an update it would boot properly and now when it boots, fsck checks my partitions and says "Dependency failed for File System Check".

I have checked on the forums and looks like the issue is back. (should replace systemd by something less buggy)

Also i have already tried:

- add 0 0 instead of 0 1 | 0 2
- touch fastboot

nothing works

Also i don't use grub, neither efibootmgr, i boot via the bzimage which i renamed xxx.efi and copied in /boot/efi/boot/bootx64.efi

i have used the command i have found on another post:
systemctl status systemd-fsck@dev-disk-by\\x2uuid-272d84b9\\xxxxxxx (too long to write)
Loaded : loaded (usr/lib/systemd/system/systemd-fsck@.service: static)
Active: inative (dead)
Docs: man:systemd-fsck@.service(8)

another info: boot = vfat, root and home = xfs

Last edited by nenoro (2025-03-30 11:03:29)

mackin_cheese · 2025-03-29 23:50:08

did you make changes to your FSTAB before this started happening?

nenoro · 2025-03-29 23:54:27

mackin_cheese wrote:

did you make changes to your FSTAB before this started happening?

No i didn't and i don't have lvm2 installed

seth · 2025-03-30 06:41:44

So i have this issue on my T460 before an update it would boot properly and now when it boots, fsck checks my partitions and says "Dependency failed for File System Check".

99.98% you forgot to mount the boot partition or booted a spurious partition into /boot before the update, the kernel went into the wrong location, you're booting an old kernel (uname -a) and lack the on-disk modules for vfat etc.

Boot the install iso, mount all partitions into place, arch-chroot and re-install the kernel (into the proper location)
You can check the older system journals for where you're booting from (if /vmlinuz-linux shows up as absolute path, it's some boot partition, for "/boot/vmlinuz-linux" you're actually booting from the root partition)

nenoro · 2025-03-30 11:03:11

seth wrote:

So i have this issue on my T460 before an update it would boot properly and now when it boots, fsck checks my partitions and says "Dependency failed for File System Check".
99.98% you forgot to mount the boot partition or booted a spurious partition into /boot before the update, the kernel went into the wrong location, you're booting an old kernel (uname -a) and lack the on-disk modules for vfat etc.
Boot the install iso, mount all partitions into place, arch-chroot and re-install the kernel (into the proper location)
You can check the older system journals for where you're booting from (if /vmlinuz-linux shows up as absolute path, it's some boot partition, for "/boot/vmlinuz-linux" you're actually booting from the root partition)

No actually systemd after an update has decided to consider my partition for /home doesn't exist so i had to reinstall arch, the issue was still there, so i have removed the line for /home, it booted then i have reformat to ext4 then back to xfs both work.

Still i don't know why suddenly systemd and fsck have decided to say my sda3 isn't viable...

Arch Linux

#1 2025-03-29 22:03:22

[solved] stuck in "dependency failed for File System Check"

#2 2025-03-29 23:50:08

Re: [solved] stuck in "dependency failed for File System Check"

#3 2025-03-29 23:54:27

Re: [solved] stuck in "dependency failed for File System Check"

#4 2025-03-30 06:41:44

Re: [solved] stuck in "dependency failed for File System Check"

#5 2025-03-30 11:03:11

Re: [solved] stuck in "dependency failed for File System Check"

Board footer