Re: Upgrade to Fedora 34 broke the boot menu.
On Tue, May 11, 2021 at 8:54 AM Björn Persson wrote: > > Adam Williamson wrote: > > Do you have any idea what went wrong? I don't recall hearing of anyone > > else having this trouble, yet. And we've definitely had pre-BLS > > installs upgraded, as people hit the GNOME login bug on them... > > The current hypothesis is that the system was using and updating > /boot/grub2/grub.cfg, leaving /boot/efi/EFI/fedora/grub.cfg to go stale, > and the upgrade replaced the file in use with the stale one. > > This would mean that different programs have different ideas about > which grub.cfg is in use. > > See also https://bugzilla.redhat.com/show_bug.cgi?id=1958540 A grubx64.efi created by grub2-install, on any version of Fedora, will use /boot/grub2/grub.cfg -- Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Upgrade to Fedora 34 broke the boot menu.
Adam Williamson wrote: > Do you have any idea what went wrong? I don't recall hearing of anyone > else having this trouble, yet. And we've definitely had pre-BLS > installs upgraded, as people hit the GNOME login bug on them... The current hypothesis is that the system was using and updating /boot/grub2/grub.cfg, leaving /boot/efi/EFI/fedora/grub.cfg to go stale, and the upgrade replaced the file in use with the stale one. This would mean that different programs have different ideas about which grub.cfg is in use. See also https://bugzilla.redhat.com/show_bug.cgi?id=1958540 Björn Persson pgpX3XiSBtS43.pgp Description: OpenPGP digital signatur ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Upgrade to Fedora 34 broke the boot menu.
On Sun, 2021-05-09 at 21:40 +0200, Björn Persson wrote: > My boot menu is now repaired. > > I replaced /boot/grub2/grub.cfg with the following: > > insmod part_gpt > insmod ext2 > search --no-floppy --fs-label --set=root speedy.boot2 > insmod blscfg > blscfg > > That was good enough to find the kernel and get Fedora going. (Keeping > all the partitions labeled pays off in situations like this.) Then I > ran "grub2-mkconfig -o /boot/grub2/grub.cfg" to get the boot working > normally. Do you have any idea what went wrong? I don't recall hearing of anyone else having this trouble, yet. And we've definitely had pre-BLS installs upgraded, as people hit the GNOME login bug on them... -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Upgrade to Fedora 34 broke the boot menu.
My boot menu is now repaired. I replaced /boot/grub2/grub.cfg with the following: insmod part_gpt insmod ext2 search --no-floppy --fs-label --set=root speedy.boot2 insmod blscfg blscfg That was good enough to find the kernel and get Fedora going. (Keeping all the partitions labeled pays off in situations like this.) Then I ran "grub2-mkconfig -o /boot/grub2/grub.cfg" to get the boot working normally. Björn Persson pgpOIohB2HgVJ.pgp Description: OpenPGP digital signatur ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Upgrade to Fedora 34 broke the boot menu.
On Sat, May 8, 2021 at 3:51 PM Björn Persson wrote: > > Chris Murphy wrote: > > Does /etc/default/grub contain > > GRUB_ENABLE_BLSCFG=false > > ? > > No, it says "GRUB_ENABLE_BLSCFG=true". > > > There have been two big GRUB changes and if you followed them without > > any intervention or customizations, you get upgraded correctly. If you > > make customizations or opt out, then those are pretty much not tested > > by anyone. So you've probably discovered a bug. > > I've customized the kernel parameters to unhide the boot messages to be > able to see what's happening when something goes wrong. I also need to > fix various problems at times. I always struggle to figure out the > proper way to update the boot menu or the initramfs when necessary. If > the instructions I found at some point in the past weren't quite right, > then I suppose I may have had some non-canonical configuration. > > > Recreate /boot/grub2/grub.cfg > > That file contains the outdated menu entries I described. Is there a > way to recreate it from the Dracut shell, or with the filesystem > temporarily mounted on another Fedora 32 system? No, it takes over 600 spawned helpers by grub2-mkconfig to compute the supreme magnificence of all potentialities and grandiose of the universe to birth a custom shell script that is the grub.cfg for your particular computer. And this means the system has to be assembled already for the magnificence to be figured out. Before you replace /boot/grub2/grub.cfg can you stat it? And at that to the bug report? -- Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Upgrade to Fedora 34 broke the boot menu.
Alexander Ploumistos wrote: > Have you looked in /boot/loader/entries/ ? I don't know how they get > created, but a couple of times I've had some extra entries after an > upgrade - nothing older than Fedora N-2 though. It contains files that seem to match the menu entries I should get, none of the outdated entries I actually see. Björn Persson pgpz23pXbFgYJ.pgp Description: OpenPGP digital signatur ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Upgrade to Fedora 34 broke the boot menu.
Chris Murphy wrote: > Does /etc/default/grub contain > GRUB_ENABLE_BLSCFG=false > ? No, it says "GRUB_ENABLE_BLSCFG=true". > There have been two big GRUB changes and if you followed them without > any intervention or customizations, you get upgraded correctly. If you > make customizations or opt out, then those are pretty much not tested > by anyone. So you've probably discovered a bug. I've customized the kernel parameters to unhide the boot messages to be able to see what's happening when something goes wrong. I also need to fix various problems at times. I always struggle to figure out the proper way to update the boot menu or the initramfs when necessary. If the instructions I found at some point in the past weren't quite right, then I suppose I may have had some non-canonical configuration. > Recreate /boot/grub2/grub.cfg That file contains the outdated menu entries I described. Is there a way to recreate it from the Dracut shell, or with the filesystem temporarily mounted on another Fedora 32 system? Björn Persson pgpwCgzgHgw6P.pgp Description: OpenPGP digital signatur ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Upgrade to Fedora 34 broke the boot menu.
On Sat, May 8, 2021 at 11:36 AM Chris Murphy wrote: > > If you have BLS disabled, enable it. Recreate /boot/grub2/grub.cfg > (this is now the correct location on UEFI and BIOS). If you've > accidentally stepped on the forwarding /boot/efi/EFI/fedora/grub.cfg If you have accidentally done 'grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg' on Fedora 34+ you can fix it just by doing: sudo dnf reinstall grub2-common That will move the grub.cfg to /boot/grub2 and the package scripts will re-create the forwarding stub file on the EFI system partition. -- Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Upgrade to Fedora 34 broke the boot menu.
Oh and you can delete any stale *conf files you find in /boot/loader/entries/. That will remove them from the GRUB menu. If you want the rescue kernel+initramfs updated you can just remove them as well. They'll be replaced the next time the kernel is updated, or you can reinstall a kernel. -- Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Upgrade to Fedora 34 broke the boot menu.
On Sat, May 8, 2021 at 6:52 AM Björn Persson wrote: > > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > Grub complains about not finding some theme files, and then displays a > menu with two kernels from Fedora 29 and a rescue entry from Fedora 28. Does /etc/default/grub contain GRUB_ENABLE_BLSCFG=false ? > If I choose one of the Fedora 29 entries, then Grub unsurprisingly > fails to find the kernel. The rescue entry actually boots to some kind > of shell, after printing lots of timeout messages, but getting from > there to a working system will be a major research project for me. The rescue entry points to a "no host-only" initramfs that has more kernel and dracut modules baked in than the usual "host only" initramfs. This kernel+initramfs pair are created during a clean install. There is no automatic mechanism to ever update them. By design they go stale. Once the /usr modules are removed, this rescue entry almost certainly cannot complete a startup and you get dropped to a dracut shell. You can delete the pair, and at next kernel installation time, they'll be recreated and based on the kernel being installed. A worthwhile feature would be to enhance the rescue entry: * pin this kernel's rpm, so that the /usr modules stick around for a release lifecycle; or * make the initramfs even bigger so that it contains everything plausibly needed to do graphical boot * include the overlayfs, and LiveOS dracut modules (possibly themselves needing some enhancement) so that we can boot a read-only sysroot with a read-write overlay using /run (it'd be a volatile overlay just like a LiveOS boot) But this hypothetical rescue feature should get it's own thread for discussion. > The menu also has entries for "advanced flags" (or something like that; > not sure what it would be in English) and "tboot". Both lead to other > menus with boot entries from Fedora 25. > > The boot partition contains three sets of vmlinuz, initramfs, config > and System.map files – one fc34 set and two fc32 sets as expected – but > Grub has apparently reverted to a years-old boot menu program. There have been two big GRUB changes and if you followed them without any intervention or customizations, you get upgraded correctly. If you make customizations or opt out, then those are pretty much not tested by anyone. So you've probably discovered a bug. If you have BLS disabled, enable it. Recreate /boot/grub2/grub.cfg (this is now the correct location on UEFI and BIOS). If you've accidentally stepped on the forwarding /boot/efi/EFI/fedora/grub.cfg then right now you have to manually recreate it. There isn't a script to fix this once it's been obliterated. Fortunately it's simple: search --no-floppy --fs-uuid --set=dev $UUID set prefix=($dev)/grub2 export $prefix configfile $prefix/grub.cfg Use lsblk -f to find the UUID for /boot and substitute that UUID for $UUID above. This assumes a dedicated ext4 volume for /boot, which is the Fedora default. If you have a different configuration you might need to specify a different UUID for the file system containing /boot/grub2/grub.cfg which might also need a modified line 2 to point to a boot directory, i.e. ($dev)/boot/grub2 -- Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Upgrade to Fedora 34 broke the boot menu.
On Sat, May 8, 2021 at 6:37 PM Björn Persson wrote: > > Tomasz Torcz wrote: > > Dnia Sat, May 08, 2021 at 02:51:31PM +0200, Björn Persson napisał(a): > > > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > > > Grub complains about not finding some theme files, and then displays a > > > > Missing theme files sounds like > > https://bugzilla.redhat.com/show_bug.cgi?id=1944571 > > (Error message during boot about missing fireworks.png) > > If only that one file is missing for you, then I think my outdated boot > menu is another bug. Have you looked in /boot/loader/entries/ ? I don't know how they get created, but a couple of times I've had some extra entries after an upgrade - nothing older than Fedora N-2 though. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Upgrade to Fedora 34 broke the boot menu.
Tomasz Torcz wrote: > Dnia Sat, May 08, 2021 at 02:51:31PM +0200, Björn Persson napisał(a): > > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > > Grub complains about not finding some theme files, and then displays a > > Missing theme files sounds like > https://bugzilla.redhat.com/show_bug.cgi?id=1944571 > (Error message during boot about missing fireworks.png) If only that one file is missing for you, then I think my outdated boot menu is another bug. Björn Persson pgpl2MnGUuNP2.pgp Description: OpenPGP digital signatur ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Upgrade to Fedora 34 broke the boot menu.
Neal Gompa wrote: > On Sat, May 8, 2021 at 8:53 AM Björn Persson wrote: > > > > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > > Grub complains about not finding some theme files, and then displays a > > menu with two kernels from Fedora 29 and a rescue entry from Fedora 28. > > If I choose one of the Fedora 29 entries, then Grub unsurprisingly > > fails to find the kernel. The rescue entry actually boots to some kind > > of shell, after printing lots of timeout messages, but getting from > > there to a working system will be a major research project for me. > > > > The menu also has entries for "advanced flags" (or something like that; > > not sure what it would be in English) and "tboot". Both lead to other > > menus with boot entries from Fedora 25. > > > > The boot partition contains three sets of vmlinuz, initramfs, config > > and System.map files – one fc34 set and two fc32 sets as expected – but > > Grub has apparently reverted to a years-old boot menu program. > > > > Which component in Bugzilla might be responsible for this mess? > > > > That's probably grub2. OK, I filed a bug report against grub2. Björn Persson pgpk9__mFcJGh.pgp Description: OpenPGP digital signatur ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Upgrade to Fedora 34 broke the boot menu.
Dnia Sat, May 08, 2021 at 02:51:31PM +0200, Björn Persson napisał(a): > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > Grub complains about not finding some theme files, and then displays a Missing theme files sounds like https://bugzilla.redhat.com/show_bug.cgi?id=1944571 (Error message during boot about missing fireworks.png) -- Tomasz Torcz “(…) today's high-end is tomorrow's embedded processor.” to...@pipebreaker.pl — Mitchell Blank on LKML ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Upgrade to Fedora 34 broke the boot menu.
On Sat, May 8, 2021 at 8:53 AM Björn Persson wrote: > > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > Grub complains about not finding some theme files, and then displays a > menu with two kernels from Fedora 29 and a rescue entry from Fedora 28. > If I choose one of the Fedora 29 entries, then Grub unsurprisingly > fails to find the kernel. The rescue entry actually boots to some kind > of shell, after printing lots of timeout messages, but getting from > there to a working system will be a major research project for me. > > The menu also has entries for "advanced flags" (or something like that; > not sure what it would be in English) and "tboot". Both lead to other > menus with boot entries from Fedora 25. > > The boot partition contains three sets of vmlinuz, initramfs, config > and System.map files – one fc34 set and two fc32 sets as expected – but > Grub has apparently reverted to a years-old boot menu program. > > Which component in Bugzilla might be responsible for this mess? > That's probably grub2. -- 真実はいつも一つ！/ Always, there's only one truth! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Upgrade to Fedora 34 broke the boot menu.
I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now Grub complains about not finding some theme files, and then displays a menu with two kernels from Fedora 29 and a rescue entry from Fedora 28. If I choose one of the Fedora 29 entries, then Grub unsurprisingly fails to find the kernel. The rescue entry actually boots to some kind of shell, after printing lots of timeout messages, but getting from there to a working system will be a major research project for me. The menu also has entries for "advanced flags" (or something like that; not sure what it would be in English) and "tboot". Both lead to other menus with boot entries from Fedora 25. The boot partition contains three sets of vmlinuz, initramfs, config and System.map files – one fc34 set and two fc32 sets as expected – but Grub has apparently reverted to a years-old boot menu program. Which component in Bugzilla might be responsible for this mess? Björn Persson pgpbycvIEd1Uy.pgp Description: OpenPGP digital signatur ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
