vMotion failed. System Error. Source side error is : Source side relocate failed
for the virtual machine. Error caused by file
/vmfs/volumes/vsan:###############-#############/#########-####-
####-####-############/<VM Name>.vmdk Target side error is : Could not
complete network copy for file [ma-ds-########-########-####-#############]
<VM Name>/<VM Name>.vmdk
/common/logs/admin/app.log<Time Stamp> [VmotionService_SvcThread-71799, Ent: HybridityAdmin, , TxId: ########-####-####-####-#############] ERROR c.v.v.h.m.common.MigrationUtil- [migId=########-####-####-####-#############] Job (########-####-####-####-#############) failed with exception System Error. Source side error is : Source side relocate failed for the virtual machine. Error caused by file /vmfs/volumes/vsan:#############-##############/########-####-####-####-#############/<VM name>.vmdk
Target side error is : Could not complete network copy for file [ma-ds-########-####-####-####-#############] <VM name>/<VM name>.vmdk
java.lang.RuntimeException: Source side error is : Source side relocate failed for the virtual machine. Error caused by file /vmfs/volumes/vsan:#############-##############/########-####-####-####-#############/<VM name>.vmdk
Target side error is : Could not complete network copy for file [ma-ds-########-####-####-####-#############] <VM name>/<VM name>.vmdk
at com.vmware.hybridity.service.vmotion.jobs.VmotionWorkflow.doJoinMonitorProgress(VmotionWorkflow.java:2438)
/var/log/hostd.log
<Time Stamp> Er(163) Hostd[2102405]: [Originator@6876 sub=NfcManager opID=########-####-####-####-############# sid=5206e6ec user=vpxuser:<domain>\Administrator] File transfer [/vmfs/volumes/vsan:#########-########/########-####-####-####-#############/<VM name>.vmdk -> /vmfs/volumes/########-####-####-####-#############/<VM name>/<VM name>.vmdk] failed: XXX DiskLib error should follow -- Failed to read the file
: Input/output error
/var/log/vmkernel.log
<Time Stamp> Wa(180) vmkwarning: cpu54:2099225)WARNING: LSOM: LSOMReadVerifyChecksum:5241: Throttled: Checksum error on comp ########-####-####-####-#############, offset 61711851520 (computed CRC 0x0 != saved CRC 0x81bf8868 (F)) 4096
VMware HCX
Data integrity issues, specifically checksum mismatches, were detected during the file transfer.
If you believe you have encountered this issue, please open a support case with Broadcom Support (vSAN team) and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.