Error "Failed to copy source VMDK to destination VMDK : I/O error" - During VM disk consolidation
search cancel

Error "Failed to copy source VMDK to destination VMDK : I/O error" - During VM disk consolidation

book

Article ID: 413482

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • Disk consolidation for a virtual machine fails, displaying this error in the Tasks and Events log:

Failed to copy source (/vmfs/volumes/<datastore-uuid>/VM-DIRECTORY/VM_Name-000001.vmdk) to destination (/vmfs/volumes<datastore-uuid>/VM-DIRECTORY/VM_Name.vmdk): I/O error. An error occurred while consolidating disks: The operation failed. Consolidation failed for disk node 'scsi0:0': The operation failed. Failed to get copy progress while consolidating disks from '/vmfs/volumes/<datastore-uuid>/VM-DIRECTORY/VM_Name-000001.vmdk' to '/vmfs/volumes<datastore-uuid>/VM-DIRECTORY/VM_Name.vmdk'.

You may also see below messages

  • In ESXi - var/run/logvmkernel log:
    yyyy-mm-ddThh:mm:ss.xxxZ cpuxx:14375299)WARNING: SVM: 2869: scsi0:x Failed SVMFDSIoctlMoveData: Busy

    OR

    YYYY-MM-DDTHH:MM:SSZ cpu35:3842709)WARNING: SVM: 2990: scsi0:0 copyBitmapInfo already cleaned up. Failing request to set copyBitmap
    YYYY-MM-DDTHH:MM:SSZ cpu9:3843117)WARNING: SVM: 2869: scsi0:0 Failed SVMFDSIoctlMoveData: I/O error


  • In ESXi - var/run/loghostd log:
    Failed to copy source (/vmfs/volumes<datastore-uuid>/VM-DIRECTORY/VM_Name-0000x.vmdk) to destination (/vmfs/volumes<datastore-uuid>/VM-DIRECTORY/VM_Name.vmdk): Busy.

  • In ESXi - vmfs/volumes/datastore-name/VM-name/vmware log:
    yyyy-mm-ddThh:mm:ss.xxxZ Wa(03) vmx - Mirror: scsi0:x: Failed to copy disk: Busy
    yyyy-mm-ddThh:mm:ss.xxxZ Wa(03) vmx - MirrorDiskCopyGetCopyProgress: Failed to get disk copy progress for source disk: '/vmfs/volumes<datastore-uuid>/VM-DIRECTORY/VM_Name-0000x.vmdk' and destination disk: '/vmfs/volumes<datastore-uuid>/VM-DIRECTORY/VM_Name.vmdk'

Environment

ESXi - All versions

Cause

The disk consolidation failure is caused due to underlying storage issue.

Resolution

Engage the storage vendor for further investigation on the I/O errors.

For further assistance contact Broadcom Technical Support. Refer Creating and managing Broadcom support cases