On Tue, Apr 30, 2019 at 7:21 PM Todd Zullinger tmz@pobox.com wrote:
Chris Murphy wrote:
On Tue, Apr 30, 2019 at 4:17 PM Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Tue, 2019-04-30 at 16:03 -0600, Chris Murphy wrote:
Just a heads up that this can be an issue, but I'm not sure how common it is. It applies to BIOS (not UEFI) firmware, and for systems that originally had Fedora 20 or older installed and also never had 'grub2-install' issued since then. Therefore it can be prevented just by running 'grub2-install' before commencing the Fedora 30 upgrade.
https://fedoraproject.org/wiki/Common_F30_bugs#GRUB_boot_menu_is_not_populat...
It's worth going through all the Common Bugs.
The text actually says:
So if you have an installation that has been updated since Fedora 20 or before, it is recommended to execute the grub2-install command before doing a system upgrade.
I assume that should say "... if you have an installation that has NOT been updated since Fedora 20 or before ..."
Good catch. I fixed that, and made a few other clean ups, let me know if you spot any other problems.
I thing it was correct before, but perhaps it could still be improved. (Obviously, the wording isn't as clear as it can be or we wouldn't be having this conversation. ;)
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.
It happens if the most recent 'grub2-install' happened with a Fedora 20 or older GRUB package. e.g. if you installed Fedora 20 clean, then did an OS upgrade every 6-12 months all the way through to Fedora 30, then you'd probably run into this bug. But if at any point from Fedora 21 and newer you ever did a 'grub2-install' you won't hit it.