We are trying to virtualize a CentOS 6.10 box that is apparently running a software raid (I think). It is tricky verifying as the machine is remote, and the users don't have a clue.
The method we've tried is by doing a full-image restore via our Acronis Cloud software, which normally works great.
I'm thinking however, due to the raid, we're not succeeding. On our attempts, Hyper V says there's no bootable disk. We've done a grub rebuild, but still couldn't get it to fully work.
What we see disk wise to recover from in Acronis is "md0" and "main-root". However from fdisk -l on the physical machine, here's what we see:
[root@msc ~]# fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x5c707033
Device Boot Start End Blocks Id System
/dev/sda1 * 1 32 256000 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/sda2 32 121602 976504832 fd Linux raid autodetect
Disk /dev/md1: 999.8 GB, 999806730240 bytes
2 heads, 4 sectors/track, 244093440 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/main-root: 991.6 GB, 991550242816 bytes
255 heads, 63 sectors/track, 120549 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/main-swap: 8254 MB, 8254390272 bytes
255 heads, 63 sectors/track, 1003 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/md0: 262 MB, 262078464 bytes
2 heads, 4 sectors/track, 63984 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Any thoughts? A better way to do this P2V considering there's a software raid?
User contributions licensed under CC BY-SA 3.0