Storageworks DLT VS80 external diagnotics issues

[prezbedard]

I have been running backups without issues for the longest time. All of sudden backups began to fail. I have upgrade drivers, upgraded from symantec backup exec 10d to 12.5.

I ran the library and tape tools. I am getting some errors I can't make sense of since the drive seems to be fine according to the diagnostic lights.

Here are the results from the drive assessment tests.

Test 'DLT1 / VS80 / VS160 Drive Assessment test' started on device 'HP DLT VS80' at address '4/0.3.0'
Failed
Operations Log
Analysis Results
DLT1 / VS80 / VS160 Drive Assessment Test, version V01.06.2005
DLT1 / VS80 / VS160 Drive Assessment module version V24.05.2005
Firmware rev 'V065' is up-to-date for 'DLT VS80' as of Wed Dec 07 14:00:00 2005.
events seen as a warning (from prior to this test) (loop 4 (check event logs)
(POH: 39969) Packet # 202 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=39969/64/000228FD/3/30/00/00...
(POH: 39969) Packet # 203 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=39969/64/000228FD/3/30/00/00...
(POH: 39969) Packet # 204 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=39969/64/000228FD/3/30/00/00...
(POH: 39969) Packet # 205 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=39969/64/000228FD/3/30/00/00...
(POH: 39969) Packet # 206 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=39969/64/000228FD/3/30/00/00...
(POH: 39969) Packet # 207 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=39969/64/000228FD/3/30/00/00...
(POH: 39969) Packet # 208 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=39969/64/000228FD/3/30/00/00...
(POH: 39969) Packet # 209 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=39969/64/000228FD/3/30/00/00...
(POH: 39969) Packet # 210 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=39969/64/000228FD/3/30/00/00...
(POH: 39969) Packet # 211 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=39969/64/000228FD/3/30/00/00...
(POH: 39969) Packet # 212 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=39969/64/000228FD/3/30/00/00...
(POH: 39969) Packet # 213 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=39969/64/000228FD/3/30/00/00...
(POH: 39969) Packet # 214 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=39969/64/000228FD/3/30/00/00...
(POH: 39969) Packet # 215 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=39969/64/000228FD/3/30/00/00...
(POH: 39969) Packet # 216 - SCSI Event: POH/PC/MID/SK/ASC/ASCQ/AddErr=39969/64/000228FD/3/30/00/00...
Rewind command failed at loop 6 (quick write/read)
Byte2 0x3 SenseCode 0xc SenseQual 0x0
- The drive failed the quick write/read test.
- Try the test again with a different tape.
Load/unload command (soft unload) failed at loop 7 (quick write/read)
Byte2 0x3 SenseCode 0xc SenseQual 0x0
Total test time: 142 seconds

Are these errors indicating a bad drive? Are they fatal errors or can something be done?

Thanks!

[Eemans Dany]

Hi,

I think you have a faulty drive. As indicated in the log, there are a lot of SCSI events (errors).
Most of the time it is the tape drive controller (build in to the drive) that is faulty. Can also be the SCSI card or SCSI cable that has interferance during datatransmission (not likely).

Dany

[gregersenj]

Did you remember to stop all services for the backup application, before running L&TT?

Try with a brand new tape.
Clean the tape drive, with a cleaning tape.
Try again.
Do a second cleaning.
Try again.

If it still fail with a new tape after 2 cleaning attempts.
Then it seem to be a bad drive.

Br
/jag

[prezbedard]

I tried again this time with the backupexec services stopped. It was the same result. I know its unlikely but I do have another scsi card to try.

It is strange the drive LEDs indicate no issues. The last drive that died had clear issues it wouldn't eject the tape and the leds indicated serious errors.

[gregersenj]

I have seen, a lot of strange errors in the past years, wich is caursed by bad drives or tapes.

If you got a drive that i flasing:
wait 20 - 30 minutes. If the flasing stops, do an emergency eject - Hold eject button for 6 seconds.
If it doesn's stop flasing, try to power cycle the drive, and see.

Drive could be bad, but to check for bend pins in the connector, and correct termination.

BR
/jag