Status 84: "Media write error"

Article:TECH35336  |  Created: 2008-01-03  |  Updated: 2010-11-16  |  Article URL http://www.symantec.com/docs/TECH35336
Article Type
Technical Solution


Environment

Issue



Status 84: "Media write error"


Error



write_data: cannot write image to media id XXXXXX, drive index #, Data error (cyclic redundancy check).


Solution



Overview:  The cyclic redundancy check (CRC) error is a generic message that can be caused by numerous hardware related factors.

Troubleshooting:
Please follow all steps within the VERITAS NetBackup (tm) Troubleshooting Guide or the NetBackup Troubleshooter within the Activity Monitor for this status code before continuing.

Please confirm hardware and software compatibility before continuing. A list of compatible hardware and software may be obtained within the VERITAS NetBackup Release Notes or on the VERITAS Support Web site.

If the above does not resolve the issue, please continue.

 
1. Status code 84 caused during a backup
 

Please look for the following log messages:

Master Log Files:

Media Server Log Files:

bptm:
write_data: cannot write image to media id XXXXXX, drive index #, Data error (cyclic redundancy check).

System Event Viewer:
 
The device, \Device\Tape#, has a bad block.
 

Client Log Files:


Resolution:

Common reasons for a CRC error with potential ways to resolve the problem:

1. Contaminated read/write heads of the tape device: Check with the hardware manufacturer for proper cleaning techniques
 

 
2. Bad media:
 
  • Replace the media
  • Try a new tape that is certified by the hardware manufacturer

3. Corrupt tape drivers have been known to cause CRC errors

 
Ensure the latest tape drivers available for your tape drives are loaded. VERITAS has tape drivers available in the VERITAS tape installer. This can be downloaded from:    http://www.symantec.com/docs/TECH51096 
 

 
4. SCSI controller is incorrectly configured to use wide negotiation:
 
  • Use the manufacturer's SCSI setup program to disable wide negotiation on the SCSI controller card
  • If the device is a wide (68 pin) SCSI device, then wide negotiation should be used. If the device is a narrow (50 pin) SCSI device, disable wide negotiation.

 
6. SCSI controller transfer rate is too fast:
 
Use the manufacturer's SCSI setup program to lower the SCSI transfer rate.
 
(NOTE: Check with the controller and backup device manufacturer for the proper configuration for SCSI transfer rate.)
 

 
7. 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.
 

 
8. 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.
 

 
9. 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.
 

 
10. General SCSI problems:
 
Isolate the tape drive(s) to its own controller card.
 


Many CRC errors are posted to the Windows Event Viewer as event 9 or 11's. Please reference the following Microsoft article to troubleshoot these event messages. For more information, refer to Microsoft Article ID: Q154690 (  http://support.microsoft.com ).
 

 



Legacy ID



272802


Article URL http://www.symantec.com/docs/TECH35336


Terms of use for this information are found in Legal Notices