Cloning of a VM fails with "Error caused by file /vmfs/volumes/vsan:xxxx-xxxxx-xxxxx/###-#####-###/VM-name.vmdk"

Products

• VMware vCenter Server

Issue/Introduction

• Cloning of a Virtual machine from/to a vSAN datastore may fail with below error.
  
  Error caused by file /vmfs/volumes/vsan:xxxx-xxxxx-xxxxx/###-#####-###/VM-name.vmdk
  
  
  
  
  
• The /var/run/log/hostd.log reports Input/output error for the clone operation.
  
  2025-10-03T08:35:22.227Z Er(163) Hostd[210#####] [Originator@6876 sub=DiskLib opID=mg#####-######-auto-gs4s-h5:######-f2-01-#### sid=###### user=vpxuser:#######\#######] DISKLIB-LIB_CLONE   : DiskLibCloneWholeDisk: Failed to clone whole disk: Input/output error
2025-10-03T08:35:22.227Z Er(163) Hostd[210####:#####\#######] DISKLIB-LIB_CLONE   : DiskLibCloneGrowInt: Failed to clone whole disk: Input/output error

Environment

vSphere vSAN 7.x
vSphere vSAN 8.x

Cause

Cloning is failed due to the Checksum errors on components which are part of the affected VM object.

2025-10-03T10:33:07.911Z Wa(180) vmkwarning: cpu67:2099697)WARNING: LSOM: LSOMScrubReadComplete:2983: Throttled: Checksum error on comp 92479b68-6239-2323-d585-############, offset 37131366400 (computed CRC 0x0 != saved CRC 0x81bf8868 (F)) 4096
2025-10-03T10:33:38.033Z Wa(180) vmkwarning: cpu70:2099697)WARNING: LSOM: LSOMReadVerifyChecksum:5241: Throttled: Checksum error on comp 92479b68-6239-2323-d585-############, offset 37131366400 (computed CRC 0x0 != saved CRC 0x81bf8868 (F)) 4096
2025-10-03T10:34:08.070Z Wa(180) vmkwarning: cpu61:2099697)WARNING: LSOM: LSOMScrubReadComplete:2983: Throttled: Checksum error on comp 92479b68-6239-2323-d585-############, offset 37131366400 (computed CRC 0x0 != saved CRC 0x81bf8868 (F)) 4096


Virtual machine / Object which is having the affected components can be identified by using the below command output.
# esxcli vsan debug object list --all 


Checksum errors could be an indication of further underlying issues on the vSAN disks.
VMware vSAN disk encounters medium errors but not failed out by vSAN

Resolution

Work-around:

• Consolidate the snapshot for the Virtual Machine.
• Clone the existing Storage policy used by the affected Virtual machine and create a new policy with Checksum disabled.
• Apply the new policy for the affected VM 'LIPI_BRIN_MX_MAILBOX03'.
• Clone the VM and verify the status.
• Please use the newly cloned VM for production. Remove the existing VM once you have validated and confirmed the cloned VM is running as expected.