Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1707199 - Grub missing Fedora entries after upgrade from F29 -> F30
Summary: Grub missing Fedora entries after upgrade from F29 -> F30
Keywords:
Status: CLOSED DUPLICATE of bug 1652806
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 30
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-07 02:52 UTC by Mirko Predosin
Modified: 2019-10-15 07:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-15 07:39:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mirko Predosin 2019-05-07 02:52:32 UTC
Description of problem:

I have dual boot system with Fedora on /dev/sda and Windows 7 on /dev/sdb.  After the upgrade from F29-F30, all of the Fedora entries were missing.

It turns out that grub2-mkconfig was failing due to a change in /etc/default/grub.

Changing the GRUB_ENABLE_BLSCFG entry resolved the issue.

GRUB_ENABLE_BLSCFG=true
to
GRUB_ENABLE_BLSCFG=false

Comment 1 Mirko Predosin 2019-05-07 03:06:09 UTC
This seems relevant and shows what motivated the change in /etc/default/grub that broke my system.

https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault

Comment 2 Mirko Predosin 2019-05-07 03:09:30 UTC
This is the article that I came across explaining the fix.
https://www.linode.com/community/questions/18148/node-unbootable-after-in-place-upgrade-to-fedora-30-converted-grub-config-to-bls

Comment 3 Javier Martinez Canillas 2019-10-15 07:39:42 UTC

*** This bug has been marked as a duplicate of bug 1652806 ***


Note You need to log in before you can comment on or make changes to this bug.