Arch Linux

Neon Cat

Member

Registered: 2025-02-05

Posts: 10

[Solved] Fails to boot with "Dependency failed for /boot"

Hello,

I recently updated but something went wrong and when I rebooted it failed with:

Loading Linux linux …
Loading initial ramdisk …

[ TIME ] Timed out waiting for device /dev/disk/by-uuid/2658-BC8C.
[DEPEND] Dependency failed for File System ☐eck on /dev/disk/by-uuid/2658-BC8C.
[DEPEND] Dependency failed for /boot.
[DEPEND] Dependency failed for Local File Systems.
You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, or "exit" to continue bootup.

I tried updating the kernel, downgrading the kernel, reinstalling/reconfiguring grub and running mkinitcpio -P but nothing worked. Any response would be greatly appreciated.

Thanks.

Last edited by Neon Cat (2025-02-10 11:57:46)

Ethergeist

Member

Registered: 2025-02-07

Posts: 4

Re: [Solved] Fails to boot with "Dependency failed for /boot"

This is usually something in your /etc/fstab file that is trying to mount a disk that doesn't exist (or some other issue that prevents it from being mounted).

There are a couple of solutions to this, but the simplest way to fix it that I've found is to boot an arch installer USB and then repeat the arch install steps for Mount the file systems and then for fstab.

After you have done that then you can run

arch-chroot /mnt
mkinitcpio -P

To regenerate the boot image with the new /etc/fstab. If booting doesn't work after that, then you'd want to look for any errors listed by using the journalctl -xb command listed in the error above to diagnose things further.

Neon Cat

Member

Registered: 2025-02-05

Posts: 10

Re: [Solved] Fails to boot with "Dependency failed for /boot"

Thanks a lot, turns out my /etc/fstab had the wrong uuid. Regenerating it and running mkinitcpio -P fixed all issues.

Ethergeist

Member

Registered: 2025-02-07

Posts: 4

Re: [Solved] Fails to boot with "Dependency failed for /boot"

Awesome, glad to hear that you were able to get up and running - if you can, edit the title for this post and add [Solved] at the beginning to show that it was fixed.