cancel
Showing results for 
Search instead for 
Did you mean: 

problem with cyclic redundancy check (CRC) error

Anthony_Witbrod
Not applicable
I've seen this post about this error, but I don't see if it is supposed to happen everytime or not. We have brand new tapes with a brand new server with our 3rd hp tape drive. But...it's not working.

We get:
1 good
2 bad
1 good
1 bad
then back to
1 good
2 bad

we try new tapes in there and thought the problem was with how the job was setup so we made it manual with a new tape and it seems to work, until it gets in taht cycle above.

Why does it work on some, but no on others?

If it was dirty, it shouldn't work at all?
If it was a SCSI problem, it shouldn't work at all?

Is it then bad media if it happens intermittitly?


The cyclic redundancy check (CRC) error is generic in nature and can be caused by numerous factors. The following list contains the most common reasons for this error and 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. Tape driver:
Load the appropriate Backup Exec tape driver. The latest Backup Exec tape drivers can be downloaded from the VERITAS Technical Support Web site at http://support.veritas.com/rd/bews-drivers.htm .

4. SCSI controller wide negotiation enabled:
Use the manufacturer's SCSI setup program to disable wide negotiation on the SCSI controller card.

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

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

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 on its own controller card.
1 REPLY 1

Deepali_Badave
Level 6
Employee
Hello,


Verify if you are getting an event id's 7, 9, 11 or 15 in the system event log.


NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.