Description of problem: The anaconda produced /etc/fstab contains an entry for the EFI System partition mounted at /boot/efi, and is incorrectly set to 0. Version-Release number of selected component (if applicable): anaconda-21.27-1 How reproducible: Always Steps to Reproduce: 1. Install to UEFI firmware based computer. Actual results: /etc/fstab entry for the EFI System Partition is UUID=D281-9CE9 /boot/efi vfat umask=0077,shortname=winnt 0 0 Expected results: Last column, fspassno, should be 1. Additional info: Tested with fspassno 1, and an ESP with dirty bit set. Systemd-fsck is executed and automatically repairs the volume, boot commences.
Actually, per man 5 fstab it should be 2. (And really we shouldn't be mounting the ESP persistently anyway, but that's a separate battle, in the meantime insofar as we are mounting it rw all the time, we should check and repair it at boot time.)
Evidently we should be setting EFIFS._check to True.
http://www.freedesktop.org/software/systemd/man/systemd-fstab-generator.html "The passno field is treated like a simple boolean, and the ordering information is discarded." So on systemd systems, it doesn't matter if it's a 1 or 2, they're treated the same.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22