V-79-57344-34028 - "Data error (cyclic redundancy check)" is reported in the Backup Exec job log during a failed backup/verify operation

V-79-57344-34028 - "Data error (cyclic redundancy check)" is reported in the Backup Exec job log during a failed backup/verify operation

  • Article ID:100017905
  • Last Published:
  • Product(s):Backup Exec

Problem

"Data error (cyclic redundancy check)" is reported in the Backup Exec job log during a failed backup/verify operation on tape.

Error Message

Storage device "Drive" reported an error on a request to read data from media. 0x17

0xe00084c7 - A backup storage read/write error has occurred. If the storage is tape based, this is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issues. If the storage is disk based, check that the storage subsystem is functioning properly. Review any system logs or vendor specific logs associated with the storage to help determine the source of the problem. You may also want to check any vendor specific documentation for troubleshooting recommendations.

A backup storage read/write error has occurred. If the storage is tape based, this is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issues. If the storage is disk based, check that the storage subsystem is functioning properly. Review any system logs or vendor specific logs associated with the storage to help determine the source of the problem. You may also want to check any vendor specific documentation for troubleshooting recommendations.

Final Error Code:  00000017 HEX 

Final Error Description:  "Data error (cyclic redundancy check)"

"Storage device "%Device%" reported an error on a request to write data to media. Error reported: Data error (cyclic redundancy check)." 

Error description:  "Data error (cyclic redundancy check)."

OR Job LogFinal Error Code:  a00084f9 HEX

Related Error Codes:

00000017 HEX
a000084f9 HEX
0xa000e006
0xe00084ec 
UMI code: V-79-57344-34028
UMI code: V-276-16
UMI code: V-79-57344-33991
UMI code: V-79-0-23
 

Cause

The following list contains the most common reasons for this error:

1.  Contaminated read/write heads of the tape device:
2.  Bad media as there may be hard read/write errors :
3.  Tape driver:
4.  SCSI controller wide negotiation:
5.  SCSI controller transfer rate is too fast:
6.  SCSI controller synchronous negotiation enabled:
7.  Incorrect termination or bad cables:
8.  Confirm that the tape drive is functioning properly:
9.  General SCSI problems
10. Tape Drive / Tape Library Firmware issue.

If the backup is going to disk, the most common cause is an imminent drive failure.
Often, NTFS errors will start appearing in the event logs regarding bad blocks, Disk, and CRC errors.
 

Solution

The cyclic redundancy check (CRC) error is generic in nature and can be caused by numerous factors.  Typically this means that a tape read/write error has occurred. This is usually caused by dirty read/write heads in the tape drive. Clean the tape drive and try the job again. If the problem persists, consider trying a different tape. Finally, the problem could be with cabling, termination or other hardware issue."

The following list contains the most common reasons for this error and potential ways to resolve the problem:

CAUSE POTENTIAL SOLUTION 
1.  Contaminated read/write heads of the tape device: Check with the hardware manufacturer for proper cleaning techniques.
2.  Bad media as there may be hard read/write errors : Replace the media. Try a new tape that is certified by the hardware manufacturer.
 
For more information about "soft" and "hard" write errors ,Please click on the link  100020857
3.  Tape driver: Load the appropriate tape driver. 
4.  SCSI controller wide negotiation: If the device is a wide (68 pin) SCSI device, then wide negotiation may and should be used. If the device is a narrow (50 pin) SCSI device, disable wide negotiation. Use the manufacturer's SCSI setup program to disable wide negotiation on the SCSI controller card.
5.  SCSI controller transfer rate is too fast: Use the manufacturer's SCSI setup program to lower the SCSI transfer rate. Check with the controller and backup device manufacturer for the proper configuration for SCSI transfer rate.
6.  SCSI controller synchronous negotiation enabled: Use the manufacturer's SCSI setup program to disable synchronous negotiation on the SCSI controller card. Check with the controller and backup device manufacturer for the proper configuration for SCSI synchronous negotiation.
7.  Incorrect termination or bad cables: Verify that the SCSI cable is good and is configured to provide proper SCSI termination. Do not mix passive and active termination.
8.  Confirm that the tape drive is functioning properly: Check with the tape drive manufacturer for diagnostic software to test the condition of the tape drive hardware.
9.  General SCSI problems: Isolate the tape drive on its own controller card.
10. Tape Drive / Tape Library Firmware issue Upgrade the firmware of Tape Drive / Tape Library and power cycle the device.For more information, refer to Microsoft Article ID: Q154690 (https://support.microsoft.com/)

 

If the error occurs when backing up to a Backup To Disk Location:

Run chkdsk on the source and destination drive to confirm the disk integrity.

If it occurs on deduplication storage: Confirm that the dedup folder is not running out of space on the volume where it resides.  If this is the case, attempt to follow the instructions found in: Reclaiming space in a Backup Exec Deduplication Folder - 100001882

 

 

 

Related Articles

An explanation of "soft" and "hard" write errors visible on the Statistics tab within Backup Exec.

A000FE34 or E000FE34 or 00000000 - Difference encountered in file data reported during verify job operation.

How do the "verify" and "write checksums to media" processes work and why are they necessary?

References

Etrack : 0xe00084c7
UMI : V-79-57344-33991
JIRA : 00000017 HEX
UMI : V-79-57344-34028
UMI : V-276-16
Etrack : 0x17
Etrack : 0xa000e006
Etrack : 0xa00084ec
Etrack : 0xe00084ec
UMI : V-79-0-23

Was this content helpful?