-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-9.4
-
None
-
grub2-2.06-80.el9
-
None
-
Moderate
-
ZStream
-
sst_desktop_firmware_bootloaders
-
ssg_display
-
3
-
False
-
-
None
-
Red Hat Enterprise Linux
-
None
-
Approved Blocker
-
-
x86_64
-
None
What were you trying to do that didn't work?
When installing a system with /boot as a Software Raid, the system will not boot properly in case grub2-common created the wrapper but enter grub> prompt.
Hopefully with Anaconda, the issue doesn't happen because Anaconda generates the wrapper by itself (which is, IMHO, a bug, it should let grub2-common handle this).
This is however an issue when Leapp'ing a system from RHEL8 to RHEL9.
The issue happens because the parameter --root-dev-only is passed to search command:
search --no-floppy --root-dev-only --fs-uuid --set=dev ${BOOT_UUID}
In case of Software Raid, this parameter breaks the functionality.
Please provide the package NVR for which bug is seen:
grub2-common-2.06-77.el9.noarch
How reproducible:
Always
Steps to reproduce
- Install a RHEL8 system in UEFI with /boot on a SoftRaid
- Leapp it
Expected results
Boots on RHEL9 after upgrade
Actual results
Falls into grub> prompt
- is duplicated by
-
RHEL-36249 leapp breaks in reboot phase on UEFI systems with /boot/efi on a Software Raid
- Closed
- is related to
-
RHEL-4388 EFI grub.cfg wrapper doesn't always execute properly, leading to getting "grub>" prompt
- New
-
RHEL-36187 RHEL-9: Anaconda creates its own version of EFI/redhat/grub.cfg wrapper
- Planning
-
RHEL-58830 RHEL-10: Anaconda creates its own version of EFI/redhat/grub.cfg wrapper
- Planning
- relates to
-
RHEL-4388 EFI grub.cfg wrapper doesn't always execute properly, leading to getting "grub>" prompt
- New
- links to
-
RHBA-2024:132763 grub2 update