FS#45684 - [linux] [boot] [systemd] filesystems hook doesn't load vfat
Attached to Project:
Arch Linux
Opened by Aleksa Sarai (cyphar) - Friday, 17 July 2015, 11:22 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 18 July 2015, 04:19 GMT
Opened by Aleksa Sarai (cyphar) - Friday, 17 July 2015, 11:22 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 18 July 2015, 04:19 GMT
|
Details
Description:
When booting on my UEFI system, systemd fails to mount /boot (which is set in /etc/fstab, and is on a `vfat` formatted partition). Upon further inspection in the recovery shell, it becomes clear that the `vfat` module hasn't been loaded. To my understanding, HOOKS="... filesystems ..." in /etc/mkinitcpio.conf is meant to load the appropriate modules without having to specify the MODULES. Adding MODULES="vfat" and rebuilding the initramfs is a workaround to the problem, but does not solve the overarching problem of HOOKS="... filesystems ..." not doing its job. Additional info: * linux=4.1.2-2 Steps to reproduce: Have a `vfat` partition set in your /etc/fstab with Linux kernel version 4.1.2-2-ARCH. Upon booting you should get an error from systemd saying that it couldn't mount that partition. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Saturday, 18 July 2015, 04:19 GMT
Reason for closing: None
Additional comments about closing: Reporter can no longer reproduce.
Saturday, 18 July 2015, 04:19 GMT
Reason for closing: None
Additional comments about closing: Reporter can no longer reproduce.
# uname -r
4.1.2-2-ARCH
# grep vfat /etc/fstab
UUID=0265-5E7F /root/foo vfat defaults 0 0
My VM boots just fine to a login prompt, and the filesystem is mounted.
Do you have problems with other modules not being autoloaded?
For the record, just booted the mentioned kernel, my ESP mounted just fine from fstab.