Chris Murphy writes:
On Tue, Apr 30, 2019 at 9:53 AM Sjoerd Mullender
<sjoerd(a)acm.org> wrote:
>
> Now that the release announcement has been done, I can say that
> upgrading for me (on a VM) also failed. After the final reboot, I just
> got a grub prompt.
It could be this:
https://fedoraproject.org/wiki/Common_F30_bugs#GRUB_boot_menu_is_not_popu...
If I deciphered this correctly: the default configuration of grub2 is that
it now reads its configuration from someplace else, and not
/boot/grub2/grub.cfg. The F30 grub2 package no longer installs
/boot/grub2/grub.cfg, so it gets renamed to grub.cfg.rpmsave on the upgrade,
but if grub2-install was never executed, the actual bootloader was never
updated, so the older grub2 that's actually still booting the system is
still looking for /boot/grub2/grub.cfg, hence the regression.
But something is still updating /boot/grub2/grub.cfg, since my grub.cfg
timestamps are from the last F29 kernel update.
I just ran grub2-install on my up-to-date F29 system, and rebooted.
Everything on F29 still seems to be in order, the grub menu is the same. If
another kernel update gets installed before I attempt an upgrade to F30,
will I still see /boot/grub2/grub.cfg getting updated with the newer kernel,
or it'll just update whatever the actual grub2 reads, at boot time?