asked on P2V process failed, how to resolve?
This is using a VMware vConverter 5.5 attempt to conduct a P2V conversion for a MS windows 2008 32-bit physical server. This physical server contains 2 - 300 GB HDDs. Configured using RAID-1, and get total 273 GB hard disk space. C: drive takes 80 GB, and remaining 193 Gb is D: drive. There are about 6+ gb free space on C: drive. Server is using 4 gb RAm.
P2V conversion on C: drive is successful without error. However, P2V on D: drive failed with the errors as shown in attached file. Why the conversion failed? How should I do to get it right?
Thanks in advance.
ee---p2v-errors.jpg
P2V conversion on C: drive is successful without error. However, P2V on D: drive failed with the errors as shown in attached file. Why the conversion failed? How should I do to get it right?
Thanks in advance.
ee---p2v-errors.jpg
VMware
Last Comment
MichaelBalack
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Hi Andrew,
One last question - Can I separate this into 2 jobs, first job do the C: drive, and then second job do the d: drive?
As now the conversion job for c: drive is underway.
One last question - Can I separate this into 2 jobs, first job do the C: drive, and then second job do the d: drive?
As now the conversion job for c: drive is underway.
You could try a C: on it's own, but the issue, could be due to reconfiguration of the VM, and not the disks!
ASKER
Thanks andrew...
ASKER
Hi Andrew,
Please see my steps:
1. Conduct P2V on C:\ (Boot) drive alone. Resize the partition and tick "reconfigure VM"
2. Conduct P2V on D:\ drive, and stick to the existing size. Not "reconfigure VM"
3. Use StarWind to do a v2v conversion from VMDK to VHD for MS HyperV 2012 r2
4. On HyperV Manager, choose to create a new VM
5. Put in vCPU, RAM, stick C:\ drive vhd to the first IDE, and D:\ vhd to the iSCSI 0
6. After booting into the Windows, select to run the "Integration Services"
7. Upon the reboot, found the admin profile was changed and have to manually run "explorer.exe"
8. Worst still, the original C:\ became E:\ drive, and D:\ became C:\ bootable
9. Delete the whole VM and redo
10. This time round, only attach C:\ vhd as first IDE, and booting up without problem
11. After booting into the Windows, wait for the hardware detection and driver auto-installed
12. Select to run "Integrated services". After that, reboot without problem
13. Down the VM, and attach a new VHD of 10 GB to iSCSI0, and boot the VM
14. open disk manager, and format the disk w/o drive letter. Down the VM again
15. Attach D: vhd as iSCSI1, and boot up the VM
16. This time round, everything works perfect. C:\ still C:\ drive, and D:\ drive is d:\ drive
Thanks,
Please see my steps:
1. Conduct P2V on C:\ (Boot) drive alone. Resize the partition and tick "reconfigure VM"
2. Conduct P2V on D:\ drive, and stick to the existing size. Not "reconfigure VM"
3. Use StarWind to do a v2v conversion from VMDK to VHD for MS HyperV 2012 r2
4. On HyperV Manager, choose to create a new VM
5. Put in vCPU, RAM, stick C:\ drive vhd to the first IDE, and D:\ vhd to the iSCSI 0
6. After booting into the Windows, select to run the "Integration Services"
7. Upon the reboot, found the admin profile was changed and have to manually run "explorer.exe"
8. Worst still, the original C:\ became E:\ drive, and D:\ became C:\ bootable
9. Delete the whole VM and redo
10. This time round, only attach C:\ vhd as first IDE, and booting up without problem
11. After booting into the Windows, wait for the hardware detection and driver auto-installed
12. Select to run "Integrated services". After that, reboot without problem
13. Down the VM, and attach a new VHD of 10 GB to iSCSI0, and boot the VM
14. open disk manager, and format the disk w/o drive letter. Down the VM again
15. Attach D: vhd as iSCSI1, and boot up the VM
16. This time round, everything works perfect. C:\ still C:\ drive, and D:\ drive is d:\ drive
Thanks,
ASKER
Hi Andrew,
After the step 7, I did booting up the VM using a w2k8 32-bit CD, and select Recovery mode.
although I corrected the bcdedit as follows:
bcdedit /set {bootmgr} device partition=c:\
bcdedit /set {default} device partition=c:\
bcdedit /set {default} osdevice partition=c:\
It didn't help. I don't know why.
After the step 7, I did booting up the VM using a w2k8 32-bit CD, and select Recovery mode.
although I corrected the bcdedit as follows:
bcdedit /set {bootmgr} device partition=c:\
bcdedit /set {default} device partition=c:\
bcdedit /set {default} osdevice partition=c:\
It didn't help. I don't know why.
ASKER
Hi Andrew,
Thanks you very much to point to the root cause. A very straight forward common human error as D: drive is not bootable, so not "reconfigure" needed. If ticked, you would expect to see the p2v process stopped at >96%.
Very much appreciate you help.
Thanks you very much to point to the root cause. A very straight forward common human error as D: drive is not bootable, so not "reconfigure" needed. If ticked, you would expect to see the p2v process stopped at >96%.
Very much appreciate you help.
Yes, it stopped at 98%
Yes, I chose to resize the partitions, but not install vmware tools
Okay, i will try the conversion again...