Storage vmotion failing with Checksum mismatch between vSan datastore.

Products

• VMware vSAN

Issue/Introduction

The storage vmotion is failing with checksum mismatch error. Skyline health indicates vsan is healthy. 

Below is the error seen in vCenter:

Error message : Failed waiting for data. Error 195887167. Connection closed by remote host, possibly due to timeout. 2025-07-03T19:48:49.447128Z Failed to copy source (/vmfs/volumes/vsan:xxxxxvmdk) to destination (/vmfs/volumes/vsan:xxx/xxxx/xxxx.vmdk): Checksum mismatch. Failed to copy one or more disks. A fatal internal error occurred. See the virtual machine's log for more details. 2025-07-03T19:48:51.337343Z vMotion migration [xxxx] failed to read stream keepalive: Connection closed by remote host, possibly due to timeout

Environment

VMware vSAN (All Versions)

Cause

The failure occurs because the vSAN object has an unrecoverable medium or checksum error. vSAN blocks I/O on the affected component to prevent corruption, which causes backup, clone, or consolidation, migration  tasks to fail.

Resolution

The issue was resolved by creating a new policy with checksum option disabled and apply that policy to the virtual machine. 

 

Additional Information

For more information kindly refer :  VMware vSAN disk encounters medium errors but not failed out by vSAN