GRUB boot problem after LVM Redhat Disk clone (Can the LABEL be changed on lvm2 ?)

I have cloned one RedHat disk to another using "dd" but now cannot boot unless one disk or the other is physically removed. The disk uses LVM with the /boot using lvm2 format. I think the problem is that GRUB sees identical boot blocks. Is it possible to change an lvm2 format boot LABEL so that GRUB sees 2 different labels? This is easy for ext2 or ext3 using e2label but I have found no way to change an LVM, lvm2 format, label for /boot.
Thanks in advance,
M
mmay5Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
nociConnect With a Mentor Software EngineerCommented:
I doubt it is the names.
All info in a LVM container is managed through GUID's (Globaly Unique ID')
The assumption is that at least every LVM object has a unique GUID.

So if you dd copy a disk the volumes have the same GUID and there fore may be considered identical... No doubt this is a recipe for disaster waiting to happen.

The best thing is to create a new Physical volume, + Volume group and create new LV's there (of the same size).
Then you can copy from the originall LV to the new LV.
When mounting based on label then you also need unique labels on the new disks, if mounting by GUID use the new GUID's
0
 
mmay5Author Commented:
Sounds correct. So my real issue is that I never used LVM commands like pvcreate, lvcreate and just dd cloned the disk.
Without using pvcreate, I ended up with the same GUID. Oh well, LVM is nice for some things but it makes cloning boot disks
a bit more of a headache. Thanks for your help. I accepted that answer.
0
 
nociSoftware EngineerCommented:
Maybe this does help:
http://tldp.org/HOWTO/LVM-HOWTO/
0
All Courses

From novice to tech pro — start learning today.