bergquistcompany
asked on
Vmware 5.1 P2 V error FAILED: An error occurred during the conversion: 'BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId
While running a P2V of a desktop PC receive error
FAILED: An error occurred during the conversion: 'BlockLevelVolumeCloneMgr: :CloneVolu me: Detected a write error during the cloning of volume \WindowsBitmapDriverVolume Id=[8D-0B- 8D-0B-00-7 E-00-00-00 -00-00-00] . Error: 37409 (type: 1, code:
2338)'
Any suggestions would be appreciated?
FAILED: An error occurred during the conversion: 'BlockLevelVolumeCloneMgr:
2338)'
Any suggestions would be appreciated?
What type of OS? What type of hardware and windows license type?
at what percentage did this occur?
Have you checked the physical disk for errors?
See my EE Articles
HOW TO: Synchronize changes when completing a P2V or V2V with VMware vCenter Converter Standalone 5.1
HOW TO: P2V, V2V for FREE - VMware vCenter Converter Standalone 5.1
HOW TO: P2V, V2V for FREE - VMware vCenter Converter Standalone 5.0
HOW TO: Improve the transfer rate of a Physical to Virtual (P2V), Virtual to Virtual Conversion (V2V) using VMware vCenter Converter Standalone 5.0
Have you checked the physical disk for errors?
See my EE Articles
HOW TO: Synchronize changes when completing a P2V or V2V with VMware vCenter Converter Standalone 5.1
HOW TO: P2V, V2V for FREE - VMware vCenter Converter Standalone 5.1
HOW TO: P2V, V2V for FREE - VMware vCenter Converter Standalone 5.0
HOW TO: Improve the transfer rate of a Physical to Virtual (P2V), Virtual to Virtual Conversion (V2V) using VMware vCenter Converter Standalone 5.0
There is a workaround for this.
The trick is to only transfer one drive at a time. This means that if the source has a C and a D drive you'll be P2V'ing this machine twice creating to seperate VMs - one only containing the C drive including the system partition and another VM (which I just called 'servername_Ddrive') containing only the D drive. When both P2V's are done the second one is removed from inventory. For the first VM, go to Edit Settings and attach the disk from the second VM, 'servername_Ddrive'. After that, you can boot the VM now containing both drives. Be aware that the newly attached disk will deafult to drive letter D. This means that if it had another drive letter before, you'll have to change it manually.
An important point to mention in this process is that when transferring the second VM only containing the D drive, the transfer will fail with an error around 98% stating something like "An error ocurred during reconfiguration...". This is ok - as long as the drive has been succesfully cloned, this is what matters.
An alternative workaround that will most likely work as well is to do a cold clone. By cold clone I mean using the cold clone iso that can be found among the vCenter installation files (not for vSphere 5, only v4 and earlier) to boot the server and then converting the server while it is powered off.
The trick is to only transfer one drive at a time. This means that if the source has a C and a D drive you'll be P2V'ing this machine twice creating to seperate VMs - one only containing the C drive including the system partition and another VM (which I just called 'servername_Ddrive') containing only the D drive. When both P2V's are done the second one is removed from inventory. For the first VM, go to Edit Settings and attach the disk from the second VM, 'servername_Ddrive'. After that, you can boot the VM now containing both drives. Be aware that the newly attached disk will deafult to drive letter D. This means that if it had another drive letter before, you'll have to change it manually.
An important point to mention in this process is that when transferring the second VM only containing the D drive, the transfer will fail with an error around 98% stating something like "An error ocurred during reconfiguration...". This is ok - as long as the drive has been succesfully cloned, this is what matters.
An alternative workaround that will most likely work as well is to do a cold clone. By cold clone I mean using the cold clone iso that can be found among the vCenter installation files (not for vSphere 5, only v4 and earlier) to boot the server and then converting the server while it is powered off.
ASKER
It is Windows XP lenovo laptop T500 OEM license.
It appears to have finished as it does boot up to CTRL+ALT+DEL but I'm not sure if it's reliable given the warning. It has C and devices with removable storage as A and DVD (E:)
Unknown devices:
Primary IDE Channel
Secondary IDE Channel
Base System Device
Unknown Device
Video Controller
Do I need to blow away and re run P2V?
It appears to have finished as it does boot up to CTRL+ALT+DEL but I'm not sure if it's reliable given the warning. It has C and devices with removable storage as A and DVD (E:)
Unknown devices:
Primary IDE Channel
Secondary IDE Channel
Base System Device
Unknown Device
Video Controller
Do I need to blow away and re run P2V?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If this is an OEM license, it may not activate correctly as a VM.
ASKER
Right on thanks!