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

omarchy update fails with "Boot path '/boot' is not a FAT32 filesystem" on a valid ESP

omarchylinux-omarchyuefiliminesystemd
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

#12060 supports the symptom, the error text, the two findmnt layers and the explicit fstab entry as the remedy. check_boot_partition() in /usr/lib/limine/limine-common-functions passes mountpoint -q on the automount, then reads the first line of findmnt -n -o FSTYPE and prints exactly "Boot path '$path' is not a FAT32 filesystem." The appended fstab line matches this workstation's installer-written /boot line apart from the UUID. omarchy-migrate touches its per-user marker only after the migration exits 0, and the migration writes /var/lib/omarchy/migrations/1789325478 only after the limine-entry-tool --tree check passes, so a failed run does retry, and the verify step names the right machine marker. The earlier audit's guard against an idle automount and an empty UUID is kept. One claim in the cause is unsupported: 'for example a system set up by other means and then converted to Omarchy'. #12060's reproduction says only that the ESP was not written to fstab and gives no account of how. The cause is rewritten without the invented example. Not exercised: no fstab edited, no autofs layout reproduced.

The cause above was rewritten on 2026-10-05 to match this note; the fix was corrected by the audit itself.
RISK

A wrong UUID or a typo in /etc/fstab for /boot can drop the next boot to emergency mode (see fstab-bad-entry-emergency-mode). Run sudo findmnt --verify before rebooting.

Symptom

omarchy update stops in the kernel migration:


Running migration (1789325478)
Install the Omarchy kernel and make it the first Limine boot entry
ERROR: Boot path '/boot' is not a FAT32 filesystem.

The ESP is a normal FAT32 partition and the machine boots fine.

Cause

/boot is not listed in /etc/fstab, so systemd-gpt-auto-generator mounts the ESP through a generated automount. Limine's validation in limine-mkinitcpio-hook (check_boot_partition in /usr/lib/limine/limine-common-functions) reads the filesystem type with findmnt -n -o FSTYPE and gets autofs for the outer automount layer instead of vfat, then rejects it. findmnt /boot shows both layers:


/boot systemd-1   autofs
/boot /dev/...    vfat

The Omarchy installer normally writes an explicit /boot vfat line to fstab. #12060 does not say how the reporter's install came to lack one.

Fix

Give /boot an explicit fstab entry so systemd generates a normal boot.mount, then let the migration retry.


# 1. trigger the automount, then confirm both layers
sudo ls /boot >/dev/null
findmnt /boot

# 2. find the ESP's UUID from the vfat layer, and stop if it is empty
esp_dev=$(findmnt -n -o SOURCE,FSTYPE /boot | awk '$2=="vfat"{print $1}' | head -1)
esp_uuid=$(lsblk -no UUID "$esp_dev")
echo "$esp_dev $esp_uuid"
[ -n "$esp_uuid" ] || { echo "no vfat UUID found, do not edit fstab"; false; }

# 3. append the same line Omarchy's installer writes (only after step 2 printed a UUID)
sudo cp /etc/fstab /etc/fstab.bak
echo "UUID=$esp_uuid  /boot  vfat  rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro  0 2" \
  | sudo tee -a /etc/fstab

# 4. check fstab parses before rebooting
sudo findmnt --verify

Reboot, then confirm, and rerun the pending migration. The migration writes its completion marker only after it succeeds, so it runs again:


findmnt -n -o FSTYPE /boot      # must print vfat, a single line
omarchy-migrate                 # no sudo, it calls sudo itself

If findmnt --verify complains, restore the backup with sudo cp /etc/fstab.bak /etc/fstab before rebooting.

Verify

findmnt /boot prints one line with FSTYPE vfat. omarchy-migrate completes, sudo test -e /var/lib/omarchy/migrations/1789325478 && echo done prints done, and pacman -Q linux-omarchy succeeds.

Sources

omarchy-kernel-migration-boot-not-fat32-autofs