Error: "Data error (cyclic redundancy check)" while taking a backup of the VM.

Products

• VMware vSphere ESXi

Issue/Introduction

• Virtual machine backup task failed with errors 'Error (3) Data error (cyclic redundancy check).'
Task failed. Error: Cannot find layout information for disk: 200


• The /var/log/vmkernel.log in ESX host may show similar messages as below
  
  MM.DD.YYYY hh:mm:ss cpu6:2097722)ScsiDeviceIO: 4176: Cmd(0x45b907ccb408) 0x28, CmdSN 0x80000012 from world 2111676 to dev <naa.id> failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x3 0x11 0x0 Medium Error, LBA
  
  
• In instances where Veeam is utilized as the backup solution, the following logs may appear on the vendor side:
  
  Processing <vm_name> Error: Data error (cyclic redundancy check). Asynchronous request operation has failed. [requestsize = 159744] [offset = 90979045376] Failed to upload disk '>' Agent failed
  
  
• The backup vendor logs are as below:
  
  [MM.DD.YYYY hh:mm:ss] Error (3)    Data error (cyclic redundancy check).
  [MM.DD.YYYY hh:mm:ss] Error (3)    Asynchronous request operation has failed. [requestsize = 4194304] [offset = 68160585728]
  [MM.DD.YYYY hh:mm:ss] Error (3)    Failed to upload disk '>'
  [MM.DD.YYYY hh:mm:ss] Error (3)    Agent failed to process method {DataTransfer.SyncDisk}.
  [MM.DD.YYYY hh:mm:ss] Error (3)     (System.AggregateException)
  [MM.DD.YYYY hh:mm:ss] Error (3)    Data error (cyclic redundancy check). (Veeam.Backup.Common.CCppComponentException)
  [MM.DD.YYYY hh:mm:ss] Error (3)       in c++: Error code: 0x00000017
  [MM.DD.YYYY hh:mm:ss] Error (3)       in c++: Next asynchronous read request cannot be processed.
  
  
  
• Error screenshot for reference:

         

 

Environment

• ESXi 7.x
• ESXi 8.x
• ESX 9.x

Cause

The affected VM is residing on a datastore and the backend physical disks associated the datastore are experiencing  hardware (disks) Medium Error for the hard drives 

 

Resolution

As these medium errors indicate a hardware-level issue with the physical drive, please contact your hardware vendor for further investigation.

To resolve this perform one of the below.

• Clone the virtual machine from vSphere Client - For more information refer - Clone an Existing Virtual Machine
• Shut down the Guest OS. Clone the virtual machine using command line - Cloning or Converting a Virtual Disk or RDM
• Perform a V2V conversion using the VMware vCenter Converter Standalone .Log in to the Broadcom Support Portal and download the latest version of VMware Converter Standalone.For more information refer - Using VMware vCenter Converter Standalone
  
  
  
  

Additional Information

Refer to Interpreting SCSI sense codes in VMware ESXi