Bug 1939036

Summary: grub.cfg on ESP contains "None" instead of the fs-uuid
Product: [Fedora] Fedora Reporter: Thorsten Leemhuis <fedora>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: anaconda-maint-list, jonathan, kellin, vanmeeuwen+fedora, vponcova, wwoods
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: 2021-03-15 13:51:11 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 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 ***