On Tue, May 7, 2019 at 11:53 AM Samuel Sieb <samuel@xxxxxxxx> wrote: > > On 5/7/19 10:42 AM, Chris Murphy wrote: > > If it's missing or zero length, is curious, but after we know that, it > > must be be fixed so you can run the grub2-mkconfig command now. > > It must be empty because otherwise the "cat" command would have given an > error. A very surprising situation though. I've seen zero length grub.cfg before, but it was on XFS, and it was because of an unclean umount, and GRUB doesn't support journal replay, so it could only read stale file system metadata. After coaxing normal boot, kernel XFS code did journal replay and the grub.cfg was no longer zero length. That isn't what's going on here, FAT doesn't have a journal. It might not be a bad idea to unmount /boot/efi and do an fsck on the ESP using -av flags. On mount, the vfat driver sets the dirty bit on the file system; and /etc/fstab as created by anaconda calls for running fsck if the dirty bit is present. So...I doubt the fsck will find anything that it can fix, but ... wheee! -- Chris Murphy _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
