[SOLVED] Failed to mount /boot/efi after full system upgrade

yuvadm · 2013-10-25 12:19:46

After running a full system upgrade, and rebooting, I get this error:

FAT-fs (sda1): codepage cp437 not found
[FAILED] Failed to mount /boot/efi

Running systemctl status boot-efi.mount shows the same stuff.

Obviously this is my uEFI boot partition, and it booted just fine until this update. What changed?

I'm in emergency mode after the failed boot, please advise on what I can check to fix this error. Thanks!

Last edited by yuvadm (2013-10-26 12:29:41)

jean_no · 2013-10-25 16:03:17

in /etc/fstab, codepage=cp437 ==> codepage=437

yuvadm · 2013-10-25 19:12:21

My /etc/fstab already had codepage=437 in the /boot/efi partition...

jasonwryan · 2013-10-25 19:15:28

What's in your {grub,gummiboot,syslinux,whatever} config file?

yuvadm · 2013-10-25 20:22:30

Pretty much everything there is in your gist

https://gist.github.com/jasonwryan/4618490

This setup was working just fine until this system update, nothing changed besides that.

jasonwryan · 2013-10-25 20:34:11

Heh. Well, it is working for me (using a custom kernel), but I'll boot into the Arch one to check. I assume we are talking about 3.11.6?

# edit: just realized, I moved my EFI to /boot now that gummiboot expects it there...

yuvadm · 2013-10-25 20:37:43

Yep, 3.11.6 is the latest, and what I have.

EDIT: _although_, my emergency mode kernel is 3.10.3-1, not entirely sure why (maybe last time i generated initramfs?)

Last edited by yuvadm (2013-10-25 20:41:39)

jasonwryan · 2013-10-25 20:45:21

Vanilla kernel works fine here. What is your locale?

yuvadm · 2013-10-25 20:55:55

en_us.UTF-8

jasonwryan · 2013-10-25 21:02:35

So why do you need the codepage mount option? If you remove it, does booting work as expected?

yuvadm · 2013-10-25 21:06:50

I don't need it, it was probably generated by genfstab.

Unfortunately, removing it from fstab doesn't help at all, same error.

Just to make sure I tried:

# zgrep 437 /proc/config.gz
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_NLS_CODEPAGE_437=m

which I assume means the default codepage 437 should be working?

jasonwryan · 2013-10-25 21:31:58

Well, I don't have much else. Check through pacman's log and see what was included in that last update.

yuvadm · 2013-10-25 21:38:17

Thanks for your help!

(back to trying anything I can think of....)

WorMzy · 2013-10-25 21:45:53

yuvadm wrote:

Yep, 3.11.6 is the latest, and what I have.
EDIT: _although_, my emergency mode kernel is 3.10.3-1, not entirely sure why (maybe last time i generated initramfs?)

1'm assuming you determined this with uname? Can you post the output of 'pacman -Q linux' please?

Last edited by WorMzy (2013-10-25 21:46:11)

yuvadm · 2013-10-25 21:49:09

WorMzy wrote:

1'm assuming you determined this with uname? Can you post the output of 'pacman -Q linux' please?

# pacman -Q linux
linux 3.11.6-1

You're right, I tried uname earlier.

WorMzy · 2013-10-25 22:03:03

I think the problem is that the kernel you're booting (on the EFI boot partition, presumably) is the old kernel, so when it tries to load the modules necessary for mounting the FAT partiton, it can't find them (because they've been replaced by the new kernel's modules). In the emergency mode, can you downgrade your kernel to 3.10.3-1, then try mounting the efi partiton, then re-update your kernel?

yuvadm · 2013-10-25 22:18:13

I'm not quite sure what you mean by that. Which kernel am I loading on /boot/efi? It's just gummiboot.

How would I downgrade my kernel to 3.10.3-1?

Last edited by yuvadm (2013-10-25 22:18:27)

WorMzy · 2013-10-25 22:29:36

Gummiboot is your boot manager, not the kernel. The kernel is the vmlinuz file that gummiboot loads for you. What I think has happened is that you have two kernels 'installed', one on the EFI boot partition, and one on your Arch install's root filesystem.

Your boot manager is loading the one on the EFI partition (which is an old version), but your root filesystem only has modules installed for the newer kernel.

You may be able to downgrade from the emergency shell by running:

# pacman -U /var/cache/pacman/pkg/linux-3.10.3-1-x86_64.pkg.tar.xz

Its important that the modules on the root filesystem match up to the kernel you're booting with, or else they will be incompatible.

jasonwryan · 2013-10-25 22:30:14

WorMzy wrote:

I think the problem is that the kernel you're booting (on the EFI boot partition, presumably) is the old kernel, so when it tries to load the modules necessary for mounting the FAT partiton, it can't find them (because they've been replaced by the new kernel's modules).

Good catch.

yuvadm · 2013-10-26 08:14:27

WorMzy wrote:

You may be able to downgrade from the emergency shell by running:
# pacman -U /var/cache/pacman/pkg/linux-3.10.3-1-x86_64.pkg.tar.xz

OK, I'll try that soon, but assuming that works I'll still need to upgrade the kernel that gummiboot is loading.

How would I go about upgrading it? I prefer doing that directly via a USB boot, instead of downgrading first.

EDIT: ok so your suggestion worked, downgrading to 3.10.3 got me the normal boot process back. Going to try and upgrade the kernel again, hoping the proper kernels will be copied properly to /boot

EDIT 2: so now I upgraded back to 3.11.6 and I see an upgraded kernel in /boot/vmlinuz-linux but it's not updated in /boot/efi/EFI/arch/vmlinuz-linux.efi so should I copy it manually? Would I need to do so on every update?

EDIT 3: additional shipment of fail - I saw the gummiboot warnings about $esp location https://wiki.archlinux.org/index.php/Gummiboot and still not sure what I need to copy manually or not, so I ran the gummiboot update as well as copied again all the files (initramfs and vmlinuz) from /boot, and now the boot process fails somewhere else with the screen just going black mid-process.

Last edited by yuvadm (2013-10-26 09:17:32)

WorMzy · 2013-10-26 11:54:04

That sounds like a kernel mode setting problem, it could be that the kernel you updated to has a bug in the graphics driver you use. I'd create a new topic about that though, it's not related to your original problem.

I recommend that you read this: https://wiki.archlinux.org/index.php/EF … mfs_to_ESP

yuvadm · 2013-10-26 12:20:49

Yep, seems like the original problem is indeed solved and I'm hitting a new problem.

Either way, I'm moving my ESP to /boot so this stuff doesn't happen again, and I won't need to mess with manual updates.

Thanks so much for all the help

EDIT: the black screen problem was a very stupid one, the update changed some stuff with screen brightness and the default was pitch black...

Last edited by yuvadm (2013-10-26 15:33:55)

Arch Linux

#1 2013-10-25 12:19:46

[SOLVED] Failed to mount /boot/efi after full system upgrade

#2 2013-10-25 16:03:17

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#3 2013-10-25 19:12:21

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#4 2013-10-25 19:15:28

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#5 2013-10-25 20:22:30

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#6 2013-10-25 20:34:11

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#7 2013-10-25 20:37:43

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#8 2013-10-25 20:45:21

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#9 2013-10-25 20:55:55

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#10 2013-10-25 21:02:35

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#11 2013-10-25 21:06:50

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#12 2013-10-25 21:31:58

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#13 2013-10-25 21:38:17

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#14 2013-10-25 21:45:53

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#15 2013-10-25 21:49:09

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#16 2013-10-25 22:03:03

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#17 2013-10-25 22:18:13

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#18 2013-10-25 22:29:36

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#19 2013-10-25 22:30:14

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#20 2013-10-26 08:14:27

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#21 2013-10-26 11:54:04

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

#22 2013-10-26 12:20:49

Re: [SOLVED] Failed to mount /boot/efi after full system upgrade

Board footer