On Wed, May 1, 2019 at 12:48 PM Charles R. Dennett <cdennett@xxxxxxxxx> wrote: > On 5/1/19 5:25 AM, Tom H wrote: >> On Wed, May 1, 2019 at 3:21 AM Todd Zullinger <tmz@xxxxxxxxx> wrote: >>> >>> What I took from the prior wording is that if you installed Fedora >>> 20 or earlier and then only updated the OS since (and had not >>> manually run grub2-update), that you would hit this bug. >> >> "grub2-install" not "grub2-update". > > Is there any way to tell just by looking for the presence or absence > of any particular file or directory that you would run into this > bug? 1) The existence of "/boot/grub2/i386-pc/blscfg.mod" should be a good indication because it's an F29 addition (AFAIR). But I couldn't tell you whether the F29 version'll work correctly with the F30 version. Unless you're multi-booting and grub's managed by another distribution, you may as well run "grub2-install /dev/...". The bug report says that it's supposed to be fragile, but it last failed for me seven years ago (more or less) with "/boot" on mdraid1. Maybe I've just been lucky... Whether you're multi-booting or not, there's an invocation of "grub2-install" that doesn't update the MBR, "grub2-install --grub-setup=/bin/true /dev/...". In the early days of grub2 (v1.9[78]?), you could have boot problems if the versions of the modules embedded in the MBR/MBR-gap stages differed from the "/boot/grub/i386-pc" versions, but, AFAIK, this hasn't been an issue for a while. 2) You can compare the versions that are output by grep version /boot/grub/i386-pc/modinfo.sh and grub2-probe --version _______________________________________________ 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
