Score:0

RHEL 9 server with cloned disk unable to find logical volume after boot

ke flag

We have an RHEL 9 server. We cloned it's disk drive to a new disk. (dd if=/dev/olddrive of=/dev/newdrive bs=4096)

It has a couple LVM partitions (as shown on /etc/fstab on the cloned disk): enter image description here

However when booting from the new disk, we got an error: enter image description here

Here is what lvs reported for example: enter image description here

I resolved the error by first checking what ID is present in cat /etc/lvm/devices/system.devices(which I figured is what lvm uses to find volumes after some google): enter image description here

Then I did: vgimportdevices --all, which put another line for sda2 and I commented the line that was already existing there: enter image description here

After reboot, the system was able to boot without an issue.

Does anyone have any idea why it required manual intervention to boot properly? There is no issue right now, I am just scratching my head trying to figure a logical explanation for what happened.

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.