[SOLVED] Stuck in Emergency mode: Failed to mount /boot

GaiusAurus · 2015-08-27 05:30:09

I was in the middle of copying something in dolphin (plasma) and the desktop froze. Stupidly, I held down the power button to force a restart. Now, I am in emergency mode because arch fails to mount /boot.

"systemctl status boot.mount" says that it exited status code 32, and also give the error "mount: unknown filesystem type vfat".

"pacman -Qi linux" gives version 4.1.6-1, while "uname -a" gives 4.1.5-1.

When I try to exit emergency mode with ^D or systemctl default, I get "error getting authority: error initializing authority: could not connect: no such file or directory (g-io-error-quark, 1)"

I was able to somewhat get back out of emergency mode by commenting out the /boot partition in /etc/fstab.

How can I fully get back?

Last edited by GaiusAurus (2015-08-29 03:44:36)

kozaki · 2015-08-27 10:26:03

Please share with us your /etc/fstab, pacman.log and journalctl arround when the issue occured.
You can chroot to get them.

mrunion · 2015-08-27 12:03:49

Sounds like you updated the Kernel without having your /boot partition mounted (or having the wrong /boot partition mounted). Basically, you need to boot a live disk/USB stick and chroot in and fix the Kernel version mismatch. A quick forum search on the topic will yield plenty of information.

GaiusAurus · 2015-08-29 03:44:14

I downgraded the kernel and that fixed it. Marking as solved. Thanks!

headkase · 2015-08-29 03:47:29

GaiusAurus wrote:

I downgraded the kernel and that fixed it. Marking as solved. Thanks!

That did not solve it. That is a band-aid that covers whatever was really wrong. Either your /boot was not mounted when you upgraded the kernel, the kernel you're booting from isn't in /boot (UEFI system?), or something else. You should really follow the earlier suggestion and post the contents of your /etc/fstab file to get started on the real solution.

It is a band-aid because the next time you go to upgrade the underlying problem hasn't actually been solved. And partial upgrades in Arch - not upgrading the kernel - are not supported simply because you are going to run in breakages if you insist on that.

kozaki · 2015-08-29 11:11:41

BTW I've got an Intel netbook that's also stuck when booting with latest kernels 4.1.6, but with no possible input. Posted the logs and config files in this post System won't finish bootin and hang after pacman -Syu. *Might* be linked somehow

Arch Linux

#1 2015-08-27 05:30:09

[SOLVED] Stuck in Emergency mode: Failed to mount /boot

#2 2015-08-27 10:26:03

Re: [SOLVED] Stuck in Emergency mode: Failed to mount /boot

#3 2015-08-27 12:03:49

Re: [SOLVED] Stuck in Emergency mode: Failed to mount /boot

#4 2015-08-29 03:44:14

Re: [SOLVED] Stuck in Emergency mode: Failed to mount /boot

#5 2015-08-29 03:47:29

Re: [SOLVED] Stuck in Emergency mode: Failed to mount /boot

#6 2015-08-29 11:11:41

Re: [SOLVED] Stuck in Emergency mode: Failed to mount /boot

Board footer