I suppose you updated you system but did not reboot before trying to mount that filesystem?
Then the behaviour is easily explained: during the update of the kernel (the package is named linux) all files belonging to the running kernel are removed and replaced with new files under a new path (corresponding to the new kernel version)!
This means that every action that tries to load a kernel module (explicit using modprobe or implicit by trying to mount a filesystem, whose module was not yet loaded) is unable to find said module and thus fail. There is no other way as to reboot in order to activate the new kernel and its modules.
There is no mount.vfat executable because the kernel does not need such helper binary to mount vfat.
Am 22.01.22 um 14:09 schrieb Jeanette C. via arch-general:
After a further reboot FAT filesystems can now be mounted, which is strange. I found a side note about that somewhere. I did reboot after installing the new kernel.
Jan 22 2022, David Rosenstrauch via arch-general has written:
On 1/22/22 5:30 AM, Jeanette C. via arch-general wrote:
Hey hey, I just updated my system yesterday and now I can't mount a VFAT filesystem.
Installed packages: linux 5.16.2.arch1-1 util-linux 2.37.2-5
There is no mount.vfat or mount.fat program/script and apparently no kernel module installed that contains "fat" in its name.
Is there a change in the way to mount such filesystems?
Best wishes and thanks for any hints,
Maybe try installing dosfstools?