Bug 1687191 - Upgrading to Fedora 30 breaks booting on non-EFI systems due to GRUB_ENABLE_BLSCFG
Summary: Upgrading to Fedora 30 breaks booting on non-EFI systems due to GRUB_ENABLE_B...
Keywords:
Status: CLOSED DUPLICATE of bug 1678445
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-10 19:25 UTC by Oyvind Saether
Modified: 2019-03-11 10:45 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-03-11 10:45:38 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Oyvind Saether 2019-03-10 19:25:44 UTC 
Updated some boxes to Fedora 30. Both using Legacy Boot and not EFI decided to reboot into a totally blank grub menu with nothing. These are boxes with traditional legacy grub and the configuration file in /boot/grub2/grub.cfg

The solution was to boot a USB image and cp grub.cfg.rpmsave to grub.cfg and obviously set GRUB_ENABLE_BLSCFG=false

I haven't looked into as to why blscfg doesn't work with that legacy configuration, just noticed that it happened to two different boxes. This was specially annoying on the headless box I use as a home NAS since it's usually only connected to ethernet and power so having to fix that was very annoying.
Comment 1 Javier Martinez Canillas 2019-03-11 10:45:38 UTC 

*** This bug has been marked as a duplicate of bug 1678445 ***
Note You need to log in before you can comment on or make changes to this bug.