Created attachment 1981470 [details] emergency mode after first boot with BIOS mode VM Description of problem: After installing CentOS 9 Stream on a server with BIOS mode (non-EFI) the first boot after the successful installation does end up in the emergency mode caused the failed start of the initrd-switch-root.service See also https://forums.centos.org/viewtopic.php?f=54&t=80316 The problem seems to have to do with grub as the /proc/cmdline does not contain the root parameter with the UUID of the disk when using BIOS mode, but still contains the kickstart from our automated installer parameters like inst.ks or ksdevice, like it was never updated. This started happening around the latest release of the ISO and installer kernel on the 2023-07-27 Version-Release number of selected component (if applicable): $ rpm -qa|grep grub grub2-common-2.06-67.el9.noarch grub2-tools-minimal-2.06-67.el9.x86_64 grub2-tools-2.06-67.el9.x86_64 grubby-8.40-63.el9.x86_64 grub2-efi-x64-2.06-67.el9.x86_64 How reproducible: Steps to Reproduce: 1. Create VM or use hard-ware server with BIOS mode 2. Install CentOS using the latest ISO 3. Reboot system after installation Actual results: Drops to emergency mode shell with failed initrd-switch-root.service caused by missing /sysroot Expected results: Normal boot with ending in user login prompt Additional info: https://forums.centos.org/viewtopic.php?f=54&t=80316
I ran into the same issue and it looks like the /boot/loader/entries/XXX.conf didn't install properly, same as bug 2227722
Hi, There is a new build of grub with the patch reverted. If you could please try grub2-2.06-68.el9 to make sure that it works for you..?
(In reply to Marta Lewandowska from comment #2) > Hi, > There is a new build of grub with the patch reverted. If you could please > try grub2-2.06-68.el9 to make sure that it works for you..? New iso is working on both VM and real hardware
Thank you for confirming! I am closing this one as a duplicate of 2227722, which I also just closed, since it's working now. *** This bug has been marked as a duplicate of bug 2227722 ***