Summary
After bare metal recovery or OS cloning of an LVM-based RHEL 9.x system, it may enter emergency mode and fail to boot. This issue occurs when restoring backup images to a new environment but not when overwriting in the original boot environment.
Confirmed system configurations where the issue occurs.
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 1T 0 disk
├─sda1 8:1 0 1G 0 part /boot/efi
├─sda2 8:2 0 1G 0 part /boot
├─sda3 8:3 0 26G 0 part
│ ├─rhel-var_dumpsavearea 252:0 0 6G 0 lvm /var/dumpsavearea
│ └─rhel-var 252:1 0 20G 0 lvm /var
├─sda4 8:4 0 8G 0 part [SWAP]
└─sda5 8:5 0 988G 0 part /
Causes
LVM changes cause PV scanning to fail on RHEL 9.x and clones when the device's WWID changes.
https://access.redhat.com/solutions/7025698
Workaround
If the LVM system enters emergency mode after restoration, follow this workaround:
1) Log in by entering "root" as the password.
2) To boot the system, run vi /etc/fstab
, comment out the relevant volumes (e.g., /var
and /var/dumparea
), and save the file.
3) Reboot the system and log on.
4) Undo the comments from step 2.
5) Follow Red Hat's guidance:
5-1) Run pvs
to find incorrect entries.
Remove problematic lines from /etc/lvm/devices/system.devices
.
Open the line from "IDTYPE=" to "PART=3" using vi, gedit, or similar editors.
5-2) Run vgimportdevices -a
and pvs -v
to verify the issue is resolved.
6) After reboot, the target volume is correctly accessible.
Target Product
- ActiveImage Protector 2022 Linux
(40936839765913)
Comments
0 comments
Please sign in to leave a comment.