Arch Linux

extrapalantine

Member

Registered: 2016-07-15

Posts: 64

Unable to boot: "Dependency failed for File System Check on /dev/sda6"

A few days ago, I somehow managed to completely bork my Arch kernel during a routine pacman update.

The system froze in the middle of updating, then abruptly rebooted after about 30 mins.

When I tried to boot into Arch again, it dropped me straight back to the BIOS menu. Uh oh.

I managed to use a live USB to chroot into the filesystem and downgrade the kernel to an earlier version.

Now, instead of dropping me back at the BIOS menu, Arch starts booting, then hangs with the following errors:

A start job is running for dev-sda6.device

[DEPEND] Dependency failed for Intrd Root Device
[DEPEND] Dependency failed for File System Check on /dev/sda6
[DEPEND] Dependency failed for /sysroot
[DEPEND] Dependency failed for Intrd Root File System
[DEPEND] Dependency failed for Reload Configuration from the Real Root

And then it drops me to an emergency mode prompt, which doesn't respond to any keyboard input.

Last edited by extrapalantine (2018-03-11 11:54:56)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: Unable to boot: "Dependency failed for File System Check on /dev/sda6"

https://wiki.archlinux.org/index.php/Pa … an_upgrade

Moving to NC...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

extrapalantine

Member

Registered: 2016-07-15

Posts: 64

Re: Unable to boot: "Dependency failed for File System Check on /dev/sda6"

I'm glad to hear this is a simple fix. But I'm still having some issues completing the instructions on the "Pacman crashes during an upgrade" page.

When I try to run

mkinitcpio -p Linux

from the live USB prompt, I get:

ERROR: Specified kernel image does not exist: '/boot/vmlinuz-linux'

So I've tried mounting the partitions manually, chrooting in, and using pacman to download and rebuild the kernel... but that gives me:

Pacman fails with "Could not resolve host"

I've followed the directions for fixing a broken network connection (my network worked perfectly when Arch was up and running) but even though the service is up and running, I can't connect to google.com or to 8.8.8.8.

I'm wondering if this may be related to the fact that

A start job is running for dhcpcpd

and never starts when I'm booting from the live USB.

Simulacrum

Member

Registered: 2017-02-23

Posts: 28

Re: Unable to boot: "Dependency failed for File System Check on /dev/sda6"

So I've tried mounting the partitions manually, chrooting in, and using pacman to download and rebuild the kernel... but that gives me:

I wonder wherer you ch-rooted into, in case you haven't mounted any partitions..?

A "Could not resolve host" is usually a connection problem. Have you tried to run a ping?

You can check the status of the dhcpcd daemon with

systemctl status dhcpcd.service

extrapalantine

Member

Registered: 2016-07-15

Posts: 64

Re: Unable to boot: "Dependency failed for File System Check on /dev/sda6"

Thanks, Simulacrum. I followed your advice and ran

systemctl status dhcpcd.service

...and found that dhcpcd was enabled but not started. So I ran

systemctl atart dhcpcd.service

And then

systemctl status dhcpcd.service

And saw that dhcpcd was active/running.

However, I still got the "Could not resolve host" error when pinging www.google.com and 8.8.8.8, so I knew something must still be wrong with my network interface itself.

On a hunch, I followed the instructions in this handy guide to tether my Android phone to my laptop, and ran

dhcpcd enp0s20u3

Now that dhcpcd was enabled *and* started, I was able to ping www.google.com, which meant I could finally run

pacman --root=/mnt --cachedir=/mnt/var/cache/pacman/pkg -Syyu

as described in this guide, and upgrade/rebuild my broken kernel.

After that, I was able to reboot into Arch, and (almost) everything was just as before! Yay!

The root cause of the crash, it seems, was a problem upgrading wine and/or wine-staging -- so now I'm working on repairing those broken packages.

But the core issue is now fixed, so this can be marked as "Solved." Thanks so much for your help!

Last edited by extrapalantine (2018-03-14 13:05:57)