I have a customer with a legacy application that is still running on CentOS 5.11. I have recommended we clone the VM and bring it in-house on Proxmox and put it behind a firewall to better protect it since CentOS 5 updates ended years ago.
I have managed to boot the Linode in rescue mode and clone ('dd') the various partitions /dev/sda thru /dev/sde. These are using ext3 for the filesystem.
On Proxmox I have copied these images via dd to raw LVM devices on Proxmox but they will not boot. It appears the Linode is using Virtio SCSI (Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5) for the disk driver but this does not work in Proxmox. I have also tried SATA and IDE for the heck of it but it will not boot using any of those disk types.
If I run a rescue CD from a CentOS 5 it does not see the devices at all. If I use a CentOS 7 Rescue CD, I can see the devices and mount them. I can confirm I have all of files from the original server. However if I do an "fdisk -l" it says "Disk /dev/sda doesn't contain a valid partition table."
Also when looking at the disk in parted it shows the Partition Table as "loop".
Does anyone have any pointers on what I might be missing and how to get this system to boot?
Best regards,
Eric
I have managed to boot the Linode in rescue mode and clone ('dd') the various partitions /dev/sda thru /dev/sde. These are using ext3 for the filesystem.
On Proxmox I have copied these images via dd to raw LVM devices on Proxmox but they will not boot. It appears the Linode is using Virtio SCSI (Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5) for the disk driver but this does not work in Proxmox. I have also tried SATA and IDE for the heck of it but it will not boot using any of those disk types.
If I run a rescue CD from a CentOS 5 it does not see the devices at all. If I use a CentOS 7 Rescue CD, I can see the devices and mount them. I can confirm I have all of files from the original server. However if I do an "fdisk -l" it says "Disk /dev/sda doesn't contain a valid partition table."
Also when looking at the disk in parted it shows the Partition Table as "loop".
Does anyone have any pointers on what I might be missing and how to get this system to boot?
Best regards,
Eric
Last edited: