Bug 1939036 - grub.cfg on ESP contains "None" instead of the fs-uuid
Summary: grub.cfg on ESP contains "None" instead of the fs-uuid
Keywords:
Status: CLOSED DUPLICATE of bug 1930567
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-15 13:48 UTC by Thorsten Leemhuis
Modified: 2021-03-15 13:51 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-15 13:51:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Thorsten Leemhuis 2021-03-15 13:48:52 UTC
Description of problem:
Just did a fresh install with Fedora-Workstation-Live-x86_64-34_Beta-1.2.iso and the installed system didn't boot as grub immediately dropped me to its shell. Turns out the grub.cfg on my ESP had this in the first line:

> search --no-floppy --fs-uuid --set=dev None

I replaced the "None" with the UUID from my /boot/ partition and then the system started to boot.

Not sure how it came to this. 

This is a system that already had a Fedora on it, which was left in place (IOW: I installed F34 in parallel). I did a manual configuration with the blivet-gui module from anaconda with this layout:

- a encrypted Btrfs volume with two subvolumes for / and /home; 
- a Btrfs volume for /boot
- my existing ESP mounted at /boot/efi
- a swap parititon

Comment 1 Thorsten Leemhuis 2021-03-15 13:51:11 UTC

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


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