Issues with BIOS Boot after Updating RHEL 8.10

0
6
Asked By TechWizard99 On

I recently updated around 100 systems running RHEL 8.10 using Ansible with dnf. The majority are UEFI-based and upgraded fine, but I encountered problems with two virtual machines that operate in legacy BIOS mode. After the update, both failed to boot.

Here's a bit of context:
- These are virtual machines with no changes at the VM level (like firmware, boot order, or disk configuration).
- There were no manual changes to grub or the bootloader other than those applied in the update.

After rebooting, I faced these symptoms:
- The VM couldn't boot from the disk anymore.
- It immediately tried to PXE boot instead.
- The disk remains in the BIOS boot order, but no valid boot target is found.
- It appears the bootloader or MBR may have been wiped or become unusable.

These were standard RHEL installs, without any unusual partitioning or dual-boot scenarios.

I know legacy BIOS is becoming less common, but these systems were stable before the update. I'm aiming to see if others have faced similar issues or if there's any Red Hat knowledge base references. Also, I'm trying to determine if this is a known problem or just a rare edge case. I managed to recover critical data by mounting the VMDK to another VM, and services are back up and running on a new UEFI VM. I'm planning to try a recovery disk next week to figure out the root cause.

3 Answers

Answered By SysAdminChic On

You might want to consider converting those VMs from BIOS to UEFI. It can help stabilize the booting process, especially since UEFI is the standard now. Check out resources from Red Hat for guidance on making that switch.

Answered By DataRecoveryDude On

It’s definitely still possible for VMs to boot with BIOS/MBR, especially for legacy OS setups. For example, Windows 7 32-bit doesn’t support UEFI at all. Just keep in mind that while it works for some, they may not prioritize issues related to this setup moving forward.

Answered By LegacyFan74 On

Honestly, BIOS hasn’t been relevant for quite a while now. It’s not surprising they haven’t focused testing on it much anymore. That said, it’s understandable to rely on legacy systems if they’ve been running well for you.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.