RHEL System with LVM Fails to Boot After Bare Metal Restore (BMR)

h1. RHEL System with LVM Fails to Boot After Bare Metal Restore (BMR)

h2. Summary

After performing a Bare Metal Restore (BMR) on a Red Hat Enterprise Linux (RHEL) based system that uses Logical Volume Manager (LVM), the system may fail to boot normally and instead drop to a *dracut* prompt or require booting into *rescue mode*. This issue can often be resolved by regenerating the initramfs and rebuilding the GRUB configuration.

h2. Symptoms

* System fails to boot after a Bare Metal Restore.
* Boot process stops at a {{dracut}} prompt.
* The operating system does not load normally.
* Manual intervention is required to access the system.

 !Dracut.png!


h2. Environment

* Red Hat Enterprise Linux (RHEL)
* RHEL-based distributions
* Systems using Logical Volume Manager (LVM)
* Systems restored through a Bare Metal Restore (BMR) process

h2. Resolution

h3. Step 1: Boot into Rescue Mode

# Reboot the restored system.
# From the boot menu, select the *Rescue Mode* option.
# Log in to the system when prompted.

 !RescueMode.png|width=500!


h3. Step 2: Regenerate the Initramfs

At the {{dracut}} prompt (or from the rescue environment shell), run the following command:

{code:bash}
dracut --regenerate-all -f
{code}

This command rebuilds the initramfs images for all installed kernels and ensures the necessary drivers and LVM components are included.

h3. Step 3: Rebuild the GRUB Configuration

After the initramfs regeneration completes successfully, rebuild the GRUB configuration:

{code:bash}
grub2-mkconfig > /boot/grub2/grub.cfg
{code}

h3. Step 4: Reboot the System

{code:bash}
reboot
{code}

h2. Verification

After rebooting, verify that:

* The system boots normally without entering rescue mode.
* The root filesystem mounts successfully.
* LVM volumes are available.
* No boot-related errors appear during startup.


h2. Additional Notes

If the issue persists after performing the above steps, review the following logs:

* {{/var/log/messages}}
* {{journalctl \-xb}}

Also review any GRUB or dracut-related error messages displayed during boot. These logs can provide additional insight into any remaining boot configuration or storage-related issues.