6

I am experiencing the same problem described here: Fail to boot: Codepage not found.

My error is: FAT-fs (sdx1): codepage cp437 not found

My fstab mount command for the device is:

LABEL=ESP /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2

The above is automatically generated by a script and it hasn't changed recently. The problem started recently.

I have already run mkinitcpio -p linux and it completes as expected without any errors. Other systems that are configured identically (afaics) do not have this issue.

I have checked the wiki as suggested at the comment by Gilles on the other question, but I don't find the specific problem.

Rui F Ribeiro
  • 55,929
  • 26
  • 146
  • 227
MountainX
  • 17,168
  • 59
  • 155
  • 264
  • Anything changed recently, e.g. system upgrade? – RudiC Nov 02 '18 at 16:58
  • Yes, there was a recent system update which included a new kernel. But this update wasn't a problem on any of my other identically configured computers. – MountainX Nov 03 '18 at 02:33

2 Answers2

5

I think you need a kernel that was compiled with CONFIG_NLS_CODEPAGE_437=y/m.

Dzamo Norton
  • 293
  • 3
  • 10
0

I'm running Arch Linux. This problem can generally be resolved by including vfat in the modules list in /etc/mkinitcpio.conf. Here's an example:

MODULES=(nvidia vfat)

However, another way this same error message can occur is if you boot Arch with a kernel version that does not exactly match the version of the libraries on your system. That's how I encountered it. I resolved it simply by booting with the correct kernel version.

MountainX
  • 17,168
  • 59
  • 155
  • 264