vmware converter error code 2338
Hi Experts,
How do I fix this error when I am trying to p2v a win2008 server. I'm using vmware vcenter standalone converter 6. here is the error message:
esxi6
vcenter6
thx.
How do I fix this error when I am trying to p2v a win2008 server. I'm using vmware vcenter standalone converter 6. here is the error message:
FAILED: An error occurred during the conversion: 'BlockLevelVolumeCloneMgr:All the partitions reside on one physical disk and all the partitions have 0% fragmentation.:CloneVolu me: Detected a write error during the cloning of volume \WindowsBitmapDriverVolume Id=[E3-59- DE-BA-00-0 0-50-06-00 -00-00-00] . Error: 37409 (type: 1, code:
2338)'
esxi6
vcenter6
thx.
ASKER
chkdsk had no errors found.
Can you explain how you are P2V'ing this machine...where is the source and target both located? e.g. are they right next to each other in the same subnet or is the source in one location or subnet and the target is in another?
ASKER
my source is the physical machine located in subnet a in location a and the target is a host in location b in subnet b through a vpn. why would this matter though? all my research has said this has to do with bad blocks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That was it! I specified the datastore in the same location and it worked without error. Thx....you rock!!!!!!
Do you have a backup of the data? If so, you could try CHKDSK to remedy. It sounds like you may have a bad block on the disk.
As a workaround, you cloud try converting each partition separately. Run the converter but uncheck all the other partitions except for one and repeat the process for each partition. The partition with the bad block will most likely fail (provided that is the root cause) but you will have the data from the other partitions successfully converted into .vmdk files (Virtual HDDs), which you can use to add into the newly created VM eventually. The success of this workaround will depend on a lot of variables such as your ultimate goal (e.g. what is your end goal...to P2V the machines as is or to P2V it temporarily and then upgrade the OS...and so on), also where the bad block is located (e.g. if it is located on the C drive or the other partitions D, E, etc.) For example, if the bad block resides on the OS and you are planning to P2V it then upgrade the OS then converting the other partitions will set you up so you can just create a new VM from scratch or template and then add the data (from the successfully converted .VMDK files) as virtual HDDs. Then you'll have the data ported over, with an upgraded OS in a new VM. Because of the original shape of the pHDD I'd recommend transferring all the data onto brand new virtual HDDs as precaution.
Lastly, if all else fails you should contact the hardware vendor of the physical server for further assistance (e.g. warranty service, etc.).
Let me know if you have any questions!