Bug 1713902
| Summary: | With Fedora 30 the kernel update does not update the grub configuration anymore | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Albert Flügel <af> | ||||||
| Component: | grub2 | Assignee: | Peter Jones <pjones> | ||||||
| Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 30 | CC: | amlau, bcodding, cdewolf, fmartine, lkundrak, netllama, pjones, sergio, sgraf, twaugh | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i686 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-03-19 17:29:14 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Albert Flügel
2019-05-25 15:17:47 UTC
Please share the following files: - /boot/grub2/grub.cfg - /boot/grub2/grubenv - /etc/default/grub - /boot/loader/entries/*.conf Created attachment 1574439 [details]
Requested files packed into a tar
The problem is that you have GRUB_ENABLE_BLSCFG=true in /etc/default/grub but your /boot/grub2/grub.cfg is for an non-BLS configuration. You need to re-generated your grub.cfg with grub2-mkconfig -o /boot/grub2/grub.cfg. With GRUB_ENABLE_BLSCFG=false the kernel neither got updated. Since i recovered from an unbootable system there was no kernel update, so the real check, whether the kernel update is booted, was not yet possible. For anyone googling this: To regenerate the /boot/grub2/grub.cfg after an upgrade to a release with BLS, that is GRUB_ENABLE_BLSCFG=true in /etc/default/grub, first do: grub2-install /dev/sda (or whatever is your boot device) Then run grub2-mkconfig -o /boot/grub2/grub.cfg . Otherwise the grub on your disk is probably not BLS capable and your computer does not boot anymore with error messages. Recovery using the rescue entry is neither possible anymore, because the grub config is broken to larger degree for the different system entries. On my laptop only the memtest was left offered for booting. Then you must boot a rescue image from CD/DVD/USB-stick or whatever your machine is able to. Or type in the correct boot parameters to grub. Sorry, i wanted to say: With GRUB_ENABLE_BLSCFG=false the grub.cfg neither got updated during a kernel upgrade A successive kernel update worked without issues. Nonetheless, this bug was regarding the distribution upgrade. As i'm not willing to downgrade just to test the scenario again, i assume, this problem will see the eol of F30 without much further care, if noone else experiences it or silently fixes himself. I'm also running into this same problem after upgrading from Fedora 29 to 30. Every time there's a new kernel, the grub config is never updated. If I manually run ' grub2-mkconfig -o /boot/grub2/grub.cfg' then the config is updated. Created attachment 1607742 [details]
requested files
Attaching the files requested earlier.
I reinstalled grub on my boot device and used grub2-switch-to-blscfg to switch configuration style. This bypasses the issue described here. See also https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault#How_To_Test (In reply to Albert Flügel from comment #4) > With GRUB_ENABLE_BLSCFG=false the kernel neither got updated. > Yes, this is likely due the GRUB core.img becoming stale and needing to be updated with grub2-install. This is a known F30 bug documented in [0], there is also documented the work around for this issue. [0]: https://fedoraproject.org/wiki/Common_F30_bugs#GRUB_boot_menu_is_not_populated_after_an_upgrade. This isn't fixed, and the "documented the work around" does not apply. I long ago dealt with the broken grub. I'm still stuck with a grub config that never updates whenever I update the kernel version. The only "work around" is to run 'grub2-mkconfig -o /boot/grub2/grub.cfg' manually after every kernel update. (In reply to Lonni J Friedman from comment #12) > This isn't fixed, and the "documented the work around" does not apply. I > long ago dealt with the broken grub. I'm still stuck with a grub config > that never updates whenever I update the kernel version. The only "work > around" is to run 'grub2-mkconfig -o /boot/grub2/grub.cfg' manually after > every kernel update. If you are re-generating your grub.cfg after each kernel install then I assume that you don't have GRUB_ENABLE_BLSCFG=true set in /etc/default/grub, so in that case you need to install the grubby-deprecated package to make new menu entries to be added to the existing grub.cfg. The other option is to set GRUB_ENABLE_BLSCFG=true in /etc/default/grub and re-generate your grub.cfg. If you have a legacy BIOS install, then it may be needed to update the GRUB core.img with grub2-install /dev/X (where X is the block device where the GRUB was installed). Thanks. Installing grubby-deprecated fixed the problem when GRUB_ENABLE_BLSCFG=false is set. |