Hi all,
I have tried to convert a power on physical machine to a workstation vm and it always failed at 3%-5%. The converter showed the same error message "BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume Disk#0_Partition#1." every time. I have made a disk check using HD Tune which showed no bad blocks.
Source OS: windows server 2008
Converter version: 6.0.0 build-2716716
ESXi: 6.0
Do I need to try a file level clone? Would be grateful if anyone can give me some advice.
From logs I see you trying to convert a physical machine to ESX 6 (not to workstation format).
The error is:
2017-12-21T17:31:29.360+08:00 verbose vmware-converter-worker[01196] [Originator@6876 sub=Default] [,0] SSL: syscall error 10054: An existing connection was forcibly closed by the remote host
2017-12-21T17:31:29.360+08:00 warning vmware-converter-worker[01196] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1
2017-12-21T17:31:29.360+08:00 warning vmware-converter-worker[01196] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcFssrvr_IO: failed to send write data
2017-12-21T17:31:29.360+08:00 verbose vmware-converter-worker[01196] [Originator@6876 sub=Default] [,0] DISKLIB-LIB : RWv failed ioId: #771 (2338) (34) .
followed by:
2017-12-21T17:31:30.043+08:00 warning vmware-converter-worker[01196] [Originator@6876 sub=Default] [,0] SSL: Unknown SSL Error
2017-12-21T17:31:30.043+08:00 verbose vmware-converter-worker[01196] [Originator@6876 sub=Default] [,0] SSL Error: error:1409E10F:SSL routines:SSL3_WRITE_BYTES:bad length
2017-12-21T17:31:30.043+08:00 warning vmware-converter-worker[01196] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1
2017-12-21T17:31:30.043+08:00 warning vmware-converter-worker[01196] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcSendMessage: send failed: NFC_NETWORK_ERROR
2017-12-21T17:31:30.043+08:00 warning vmware-converter-worker[01196] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcFssrvr_Close: failed to send close message
As a possible solution you can try to disable SSL communication with ESX and try again.
Change the value of the tag <nfc><useSsl> to false in converter-worker.xml then restart the worker service.
HTH
The real solution is to get logs from the ESX and investigate why SSL connection fails, probably there are difference between supported SSL/TLS versions from both sides.
I suggest you try performing file level cloning and check if the issue persists. however disabling SSL while conversion has its performance benefits.
check the linked KB
This should help https://kb.vmware.com/s/article/50121359