I created an image of a centos server with sda1 mounted to /boot and sda2 contains LVM logical volume mounted to /. I then created a new server on all different hardware with same size hard drive and the recovery process from clonezilla seems to go fine. When I try to boot the new server, I get a message that the volume group VolGroup00 cannot be found. I then booted into the clonezilla live cd and mounted the logical volume /dev/VolGroup00/LogVol01 to /mnt and mounted /dev/sda1 to /mnt/boot. I then chroot /mnt and ran mkinitrd -v -f initrd-xxx.img xxx (where xxx was the same kernel version as the existing initrd-xxx.img). A lot of stuff happened and it looked like drivers were being installed. However, when rebooting, I get the same kernel panic. I tried the same process with the --force-lvm-probe flag on mkinitrd but still get the kernel panic. Any thoughts on how to get the recovered server to boot?
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I created an image of a centos server with sda1 mounted to /boot and sda2 contains LVM logical volume mounted to /. I then created a new server on all different hardware with same size hard drive and the recovery process from clonezilla seems to go fine. When I try to boot the new server, I get a message that the volume group VolGroup00 cannot be found. I then booted into the clonezilla live cd and mounted the logical volume /dev/VolGroup00/LogVol01 to /mnt and mounted /dev/sda1 to /mnt/boot. I then chroot /mnt and ran mkinitrd -v -f initrd-xxx.img xxx (where xxx was the same kernel version as the existing initrd-xxx.img). A lot of stuff happened and it looked like drivers were being installed. However, when rebooting, I get the same kernel panic. I tried the same process with the --force-lvm-probe flag on mkinitrd but still get the kernel panic. Any thoughts on how to get the recovered server to boot?
Thanks!
Are you sure the Linux kernel from CentOS supports your new, different hardware?
Steven.