This morning I got the dreaded grub prompt on boot. Took me 3 hours to understand what
https://fedoraproject.org/wiki/Common_F30_bugs#GRUB_boot_menu_is_not_populated_after_an_upgrade was talking about. I did a bunch of searching and trying things out before I hit upon the configfile grub command. Note that grub> configfile /grub2/grub.cfg.rpmsave as shown in the common bugs is not appropriate on my machine, there was no /grub2 (see below). grub> insmod ext2 grub> insmod luks grub> insmod xfs grub> ls (hd0) (hd0,msdos1) (hd0,msdos3) (hd0,msdos5) # note: under (hd0,msdos1) is /boot # note: under (hd0,msdos3) is encrypted / # note: under (hd0,msdos5) is encrypted /home # note: cryptomount -a does not work!!! grub> cryptomount hd0,msdos3 grub> insmod lvm grub> ls (crypto0) (hd0) (hd0,msdos1) (hd0,msdos3) (hd0,msdos5) # note: did not need to decrypt / for this to work... grub> configfile (hd0,1)/grub/grub.cfg.rpmsave # got old boot menu :-) # boot into F29 # after boot... > su .... # /sbin/grub2-install /dev/sda # /sbin/reboot # reboot into F30 # good as new... On Thu, May 2, 2019 at 10:33 AM richard emberson <emberson.r...@gmail.com> wrote: > I got the dreaded grub prompt on boot this morning > Took me 3 hours to understand what > > > https://fedoraproject.org/wiki/Common_F30_bugs#GRUB_boot_menu_is_not_populated_after_an_upgrade > was talking about. I did a bunch of searching and trying things out > before I hit upon > the configfile grub command. > Note that > grub> configfile /grub2/grub.cfg.rpmsave > as shown in the common bugs is not appropriate on my machine, there was > no /grub2 (see below). > > grub> insmod ext2 > grub> insmod luks > grub> insmod xfs > grub> ls > (hd0) (hd0,msdos1) (hd0,msdos3) (hd0,msdos5) > (thunderbird:3111): libnotify-WARNING **: 10:29:55.823: Failed to > connect to proxy > # note: under (hd0,msdos1) is /boot > # note: under (hd0,msdos3) is encrypted / > # note: under (hd0,msdos5) is encrypted /home > # note: cryptomount -a does not work!!! > grub> cryptomount hd0,msdos3 > grub> insmod lvm > grub> ls > (crypto0) (hd0) (hd0,msdos1) (hd0,msdos3) (hd0,msdos5) > # note: did not need to decrypt / for this to work... > grub> configfile (hd0,1)/grub/grub.cfg.rpmsave > > # got old boot menu :-) > # boot into F29 > > # after boot... > > su > .... > # /sbin/grub2-install /dev/sda > # /sbin/reboot > > # reboot into F30 > # good as new... > > > > On 5/2/19 7:59 AM, David Dusanic wrote: > > Am 01.05.19 um 00:03 schrieb Chris Murphy: > >> 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_populated_after_an_upgrade > >> > >> > >> It's worth going through all the Common Bugs. > >> > > > > I am not entirely sure about this issue and now I have read all the > > posts about it and this Grub 'lesson' is just not getting into me. > > > > So far the upgrade went fine as usual in my case. And now why I am > > replying here. My legacy boot has Grub and instead of booting into the > > newest Fedora 30 kernel it boots by default into an older one from > > Fedora 29. I never saw this before. So I have to catch up before the > > Grub prompt automatically selects the second kernel in the boot menu. > > > > Anybody experiencing this? > > > > -- > Quis custodiet ipsos custodes >
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
