OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
boot-kernel high occasional DISPUTE

"unknown filesystem type 'vfat'" when mounting /boot or /boot/efi at boot

archomarchyendeavouroscachyosmanjarouefisystemd
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The two causes and both remedies are right, and kernel-modules-hook is a real package (extra 0.1.7) that solves the upgrade-while-running case. Two problems. MODULES=(vfat nls_cp437 nls_iso8859-1) is written as a bare assignment. On Omarchy and on NVIDIA systems MODULES already holds the early-KMS list, and pasting this silently deletes it, trading a /boot/efi mount failure for a black screen. Also the module name is spelled nls_iso8859-1 in the mkinitcpio block and nls_iso8859_1 in the dracut block. Because modprobe treats - and _ interchangeably this happens to work, but the inconsistency invites hand-editing errors.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.

Symptom

Immediately after an update the boot sequence reports:


[FAILED] Failed to mount /boot/efi.
mount: /boot/efi: unknown filesystem type 'vfat'.

and the system drops to emergency mode. The partition is fine: fsck.vfat from a live USB reports no errors, and reinstalling GRUB does not help.

Cause

The vfat kernel module (plus its nls_iso8859-1 / nls_cp437 codepage dependencies) is not available when the mount is attempted. Two ways this happens: the initramfs/early boot lacks the module, or the kernel package was upgraded while running and /usr/lib/modules/$(uname -r) was replaced, so modprobe vfat fails until reboot.

Fix

**First, is this only the running system?** If modprobe vfat fails with 'Module vfat not found in directory /lib/modules/6.x', the kernel was upgraded underneath you, so just reboot, then prevent recurrence:


sudo pacman -S kernel-modules-hook

**If it persists across a reboot**, force the modules into the image. Check what MODULES already holds before you assign, or you will delete it:


grep -h '^MODULES' /etc/mkinitcpio.conf /etc/mkinitcpio.conf.d/*.conf

Then **append** to the existing list rather than replacing it (add these three to whatever is already inside the parentheses):


# /etc/mkinitcpio.conf  -- e.g. MODULES=(nvidia nvidia_modeset vfat nls_cp437 nls_iso8859-1)
MODULES=(<keep whatever was there> vfat nls_cp437 nls_iso8859-1)

Ensure modconf is in HOOKS so /etc/modprobe.d and forced modules are honoured:


HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck)

Rebuild (one command, not both, because limine-mkinitcpio wraps mkinitcpio):


sudo mkinitcpio -P        # Arch / CachyOS
sudo limine-mkinitcpio    # Omarchy (rebuilds initramfs AND the UKIs on the ESP)

For a **dracut** system (EndeavourOS default), use a drop-in, and keep the module names consistent with the mkinitcpio spelling:


sudo tee /etc/dracut.conf.d/force-vfat.conf >/dev/null <<'EOF'
force_drivers+=" vfat nls_cp437 nls_iso8859-1 "
EOF
sudo dracut-rebuild

(dracut-rebuild is EndeavourOS's wrapper. On plain dracut use sudo dracut --regenerate-all --force.)

Verify

lsinitcpio /boot/initramfs-linux.img | grep vfat (mkinitcpio) or lsinitrd | grep vfat (dracut) finds the module, sudo mount -a succeeds, and systemctl --failed is empty after reboot.

Sources

vfat-module-missing-boot-efi-mount-fails