You are not logged in.
I was going through the Installation Guide while setting up a new Arch VM. Everything was working fine until I tried to mount my newly created EFI System Partition.
When I issued the command "mount -v /dev/sda1 /boot/efi", I got the error message "mount: /mnt/boot/efi: unknown filesystem type 'vfat'.".
When I issued the command "modprobe vfat", I got the error message "modprobe: FATAL: Module vfat not found in directory /lib/modules/7.0.10-arch1-1".
The output of "cat /proc/filesystems" does not include "vfat".
I downloaded the ISO file this morning using the magnet link.
Last edited by fishnet37222 (Yesterday 18:14:36)
Offline
When I issued the command "mount -v /dev/sda1 /boot/efi", I got the error message "mount: /mnt/boot/efi: unknown filesystem type 'vfat'."
Did you run the command before arch-chroot or after?
You have to mount ESP partition to /mnt/boot/efi/ before chrooting.
Offline
That's what I'm trying to do. In the live environment before any chrooting, there is currently no support for the vfat filesystem.
Offline
What does `ls /lib/modules/` show?
Offline
root@archiso ~ # ls /lib/modules
7.0.10-arch1-1
root@archiso ~ # ls /lib/modules/7.0.10-arch1-1
extramodules modules.alias.bin modules.builtin.bin modules.dep.bin modules.softdep modules.weakdep
kernel modules.builtin modules.builtin.modinfo modules.devname modules.symbols pkgbase
modules.alias modules.builtin.alias.bin modules.dep modules.order modules.symbols.bin vmlinuzOffline
That's what I'm trying to do. In the live environment before any chrooting, there is currently no support for the vfat filesystem.
But you run "mount -v /dev/sda1 /boot/efi" and somehow got "mount: /mnt/boot/efi: unknown filesystem type 'vfat'."
I just booted 2026.06.01 ISO image in VM: no any problem with vfat mounting, the module is present.
Offline
It seems the image available through the Magnet link on the Downloads page is incorrect. I downloaded a new copy of the ISO from the fastly mirror, and vfat support seems fine now.
Offline
It seems the image available through the Magnet link on the Downloads page is incorrect.
Out of curiosity, did you verify signature of the image before boot? Is it valid?
Offline
I didn't. I've never felt the need to in the past because they've always worked as expected.
Offline
A corruption that kept SHA1 intact, didn’t catastrophically corrupt a compressed stream, sniped out the vfat module alone, and caused no filesystem errors? That would be surprising.
Assuming that is not PEBCAK, which may happen to anybody and you shouldn’t be ashamed of one if that’s the case, consider running memtest a few times.
Paperclips in avatars? | Sometimes I seem a bit harsh — don’t get offended too easily!
Offline
When I issued the command "mount -v /dev/sda1 /boot/efi", I got the error message "mount: /mnt/boot/efi: unknown filesystem type 'vfat'.".
99.8% chroot related
What is the output of "modprobe -v vfat" right after booting the iso and before doing anything else?
Offline
I had deleted the ISO downloaded from the magnet link since I had a working one from the fastly mirror. I just downloaded a new copy of the ISO from the magnet link, and the modprobe command you asked about results in no output. "lsmod | grep vfat" shows that the module is loaded. So it appears I had a bad download after all.
Offline
That explanation is among the least likely.
PEBCAK is the most likely, but there is no way to verify it anymore. However, if that’s system instability leading to memory corruption, you can still detect it. And my advice is to do so. Of course it’s up to you.
Paperclips in avatars? | Sometimes I seem a bit harsh — don’t get offended too easily!
Offline