bperror -media -U results - what next?
Hi,
I have issues with drives repeatedly going down.
Quantum PX506
6 drives SDLT320
NBU 6.0 MP4 Windows 2003 single Master / Media
Initially drives #2 & #4 were going down. Drive 4...
Forum Discussion
I'm sure you have seen the below relating to cyclic redundancy checks, and that you are going through them. These are nightmarish issues and very hard to troubleshoot. All I would add for the moment is that I have seen similar situations before and it was never the actual media (ie the whole batch faulty) to blame. Cabling and fibre switches I have also seen to cause media errors as indicated below. I would guess that you are using fibre and not SCSI but would certainly be looking at cabling, cards, switches, anything between the media server and the actual tape drives. I am assuming that this setup has all worked before and then something happened and the errors started appearing and the drives going down, tapes frozen etc.
Can we have a bit more info on the setup (master / media servers - OS, connection types to tapes etc). It might be worth shutting down netbackup and trying to manually write to a tape drive with something else (tar, dd, windows backup ...) just a a sanity check. My gut feeling would be some hardware component - cable or card - somewhere inside the library causing problems but not being identifiable from logs or alerts.
Good luck.
(http://seer.entsupport.symantec.com/docs/272802.htm)
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
3. Corrupt tape drivers have been known to cause CRC errors
Can we have a bit more info on the setup (master / media servers - OS, connection types to tapes etc). It might be worth shutting down netbackup and trying to manually write to a tape drive with something else (tar, dd, windows backup ...) just a a sanity check. My gut feeling would be some hardware component - cable or card - somewhere inside the library causing problems but not being identifiable from logs or alerts.
Good luck.
(http://seer.entsupport.symantec.com/docs/272802.htm)
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://support.veritas.com/tabs/download_ddProduct_NBUESVR.htm
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.
