You are not logged in.
I just updated my system and upon reboot I've found myself in emergency mode. journalctl -xb tells me among other things that /boot could not be mounted. Following this thread https://bbs.archlinux.org/viewtopic.php?id=171880, I tried downgrading my kernel to 3.18.2 using pacman -U, and while it did downgrade, I am still not able to boot normally. Thinking the kernel upgrade process just caught a glitch, I tried reupdating my kernel, which caused the mkinitcpio script to run.
It said /boot appeared to be a separate partition but was not mounted. Rebooting, I still found myself in the same boat.
This is a dm-crypt+LUKS EFI system using gummiboot. The line currently in my fstab is LABEL=EFI /boot vfat rw,relatime,fmask=0022,dmask=0022,code page=437,iocharset=iso8859-1,short name=mixed,errors=remount-ro 0 2
uname -r tells me the emergency mode is using Linux kernel 3.18.2 instead of the 3.18.6 kernel I updated to. pacman -Q says Linux 3.18.6-1.
Journalctl -xb | grep -I failed | less shows that systemd failed to load display manager and failed to start Load Kernel Modules. Two units failed according to systemctl --state=failed.
When I startup and when I try and connect to the internet with netctl, I get the codepage cp437 error and am prompted again for my root password. Further investigation reveals that is in my /etc/fstab. I don't remember putting that in there. How can I see if any software modified it during the update?
I'd really appreciate suggestions for restoring my system. Thanks in advance.
Last edited by kandrews (2015-02-27 01:35:08)
Offline
chroot'ing in using the latest installation media and re-installing the kernel fixed this issue.
Offline
Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.
Offline