VMWARE CONVERTER – BLOCK LEVEL VOLUME CLONEMGR::CLONEVOLUME: DETECTED A WRITE ERROR DURING THE CLONING OF VOLUME
Description :-
2020-02-07T19:54:26.603+05:30 info vmware-converter-server[07024] [Originator@6876 sub=Default] ConverterConnection: KeepAlive timer canceled, StopKeepAlive succeeded
2020-02-07T20:14:19.559+05:30 error vmware-converter-server[11364] [Originator@6876 sub=Ufa.HTTPService] Failed to read request; stream: , >, error: class Vmacore::TimeoutException(Operation timed out)
2020-02-07T20:14:29.571+05:30 error vmware-converter-server[15840] [Originator@6876 sub=Ufa.HTTPService] Failed to read request; stream: , >, error: class Vmacore::TimeoutException(Operation timed out)
2020-02-10T11:47:28.864+05:30 error vmware-converter-server[04664] [Originator@6876 sub=Default] [task,350] [LRO] Unexpected Exception: converter.fault.CloneFault
2020-02-10T11:47:28.896+05:30 info vmware-converter-server[04664] [Originator@6876 sub=Default] [task,379] [task-1] — ERROR — Convert: converter.fault.CloneFault
–> (converter.fault.CloneFault) {
–> faultCause = (vmodl.MethodFault) null,
–> description = “BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[44-4D-49-4F-3A-49-44-3A-4D-11-A2-7C-A1-86-F8-47-90-4D-26-40-C5-C7-5E-FD]. Error: 209 (type: 1, code: 13)”,
–> msg = “”
–> }
Solution :-
1)This issue is usually happening because of space issues at destination VMware ESXi Datastore.
2)If this is the issue, you can convert disk with the thin provision and then try.
3)Recreated boot.ini on the source machine.
4)Run chkdsk to make sure there are no issues with the source drive.
5)Disable SSL in worker file of converter.
See also :-