Failed to mount /boot/efi after update - Emergency Mode

General system Newbie
1

Hi everyone, I ran into a kernel version mismatch after a system update. My system boots into 7.0.13 but /usr/lib/modules/ only has 7.0.14. Because of this, the vfat module is missing and /boot/efi fails to mount, throwing me into Emergency Mode. I have a Live USB ready, could someone please guide me on how to fix the systemd-boot entries or chroot to match the new kernel? Thank you!

image
image1000×750 222 KB

image
image750×1000 243 KB

2

https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/

Depending on your filesystem, follow the appropriate instructions for chroot.

Assuming, you have the default systemd-boot and dracut, once you are in chroot:

reinstall-kernels

to regenerate your initramfs and boot entries.

3

I think he uses GRUB, because the mountpoint is /boot/efi.

4

You are right!

A picture says more that a thousand words!

@dev11

We need more and more accurate info.

5

Now that I notice he even said /boot/efi in the title. So @dev11 we need to know if you use GRUB or systemd-boot because this is very inconsistent as GRUB uses /boot/efi and systemd-boot uses /efi.

Show us the output of the bootctl status command.

6

“Thanks everyone! The issue is solved. The automatic kernel-install generated a generic entry missing my root UUID and options, causing the /dev/gpt-auto-root hang. I fixed it by copying my old working config, updating the kernel version to 7.0.14, and re-signing with sbctl.”