Results 1 to 1 of 1
Currently I'm on an LVM setup with just 1 hard drive. The partitions are /boot and everything else is allocated to the LVMv2 type partition. I have recently cloned this ...
- 05-28-2010 #1Just Joined!
- Join Date
- May 2010
- Posts
- 1
LVMv2 New Hard Drive
Currently I'm on an LVM setup with just 1 hard drive. The partitions are /boot and everything else is allocated to the LVMv2 type partition. I have recently cloned this hard drive to a larger one (from 40gB to 80gB) but now when I boot I'm getting a kernel panic saying "No Volume Groups Found".
What I believe is happening is my LVM metadata inside /etc/lvm/backup (and possibly elsewhere) is referencing my old drive by something called the UUID. Basically what I need to do is tell it to look at the new hard drive specifically so that it can find my volume groups.
If I chroot into the lvm partition, mount proc and dev, and do a vgdisplay and lvdisplay - everything is correct. Apparently the problem is somewhere in the boot process. Any help is appreciated - thanks in advance.


Reply With Quote