Bug 1687191

Summary:	Upgrading to Fedora 30 breaks booting on non-EFI systems due to GRUB_ENABLE_BLSCFG
Product:	[Fedora] Fedora	Reporter:	Oyvind Saether <oyvinds>
Component:	grub2	Assignee:	Peter Jones <pjones>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	28	CC:	fmartine, lkundrak, pjones
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-11 10:45:38 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:

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 ***