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

bergquistcompany
bergquistcompany used Ask the Experts™
on
While running a P2V of a desktop PC receive error
FAILED: An error occurred during the conversion: 'BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[8D-0B-8D-0B-00-7E-00-00-00-00-00-00]. Error: 37409 (type: 1, code:
2338)'

Any suggestions would be appreciated?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Paul SolovyovskySenior IT Advisor
Top Expert 2008

Commented:
What type of OS?  What type of hardware and windows license type?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:

Commented:
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.
11/26 Forrester Webinar: Savings for Enterprise

How can your organization benefit from savings just by replacing your legacy backup solutions with Acronis' #CyberProtection? Join Forrester's Joe Branca and Ryan Davis from Acronis live as they explain how you can too.

Author

Commented:
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?
Senior IT Advisor
Top Expert 2008
Commented:
If you can login than you just need to run vmware tools to put the drivers on the system.  Because it is an OEM copy the VM may not work properly due to the install not seeing OEM hardware.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
If this is an OEM license, it may not activate correctly as a VM.

Author

Commented:
Right on thanks!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial