event id 9 - did not respond within timeout - causing backup failures 1

[bnordman]

I am getting the below error quite frequently:

Event Type: Error
Event Source: adpu160m
Event Category: None
Event ID: 9
User: N/A
Computer: BUSTER
Description:
The device, \Device\Scsi\adpu160m1, did not respond within the timeout period.

When this occurs it is followed by many of these errors:

Event Type: Error
Event Source: sonysdx-VRTS
Event Category: None
Event ID: 15
User: N/A
Computer: BUSTER
Description:
The device, \Device\Tape1, is not ready for access yet.

Followed by all of my backup jobs failing. This is quite frustrating during the middle of my weekend full jobs.

I found this article:

http://www.eventid.net/display.asp?eventid=9&eventno=7191&source=a320raid&phase=1

Could anyone advise how to proceed, as it sounds like it could be a problem with the scsi portion on the actual tape library. Besides that I could try another scsi card on the server and/or cables all of which we’d probably have to order.

Thanks for any help!

 

[steveot]

Update the SCSI card driver for the Adaptec Card.
Update to the latest Veritas TAPE driver
Clean the Drive with a cleaning tape.

It look as if there is a hardware problem. So yet trying new cable, SCSI card, and terminator are steps to perform.
Also try new tapes.

 

[bnordman]

Thanks for the info Steve.

I will rule out tapes since this has been an ongoing issue for a couple months and we have swapped out new tapes several times.

Tape drivers - Updated to veritas tape drivers. (Think I was already using veritas drivers, but reinstalled anyway)

Scsi card driver - Updated the card bios.

Cleaned all tape drives.

I will see what happens tonight with my backups.

 

[bnordman]

Well, I'll give you a interim update since this is still an issue.

I was still getting the errors after putting in all new tapes and verifying I was on latest scsi bios, on the veritas tape drivers and cleaning all the tape drives.

I just swapped out the scsi card + wiped out the library from backup exec and reinstalled it and set up my partitions again. My weekend full backups are scheduled to start in a couple of hours. We will see how that goes.

If I still get failures I will have to track down another SCSI cable and maybe a terminator.

Otherwise I guess it could be the SCSI controller inside my Qualstar TLS unit?

 

[bnordman]

OK. So the new card had seemed to be running better although I was getting the below error from time to time:

Event Type: Error
Event Source: sonysdx-VRTS
Event Category: None
Event ID: 7
Description:
The device, \Device\Tape1, has a bad block.

I cleaned Tape1 a couple times in a row. The error wasn't that big of a deal though, I got it maybe twice a day.

And then last night started getting the Event ID 9 errors again. Which of course cause running jobs to just fail.

I had switched out the scsi card on my server (same model, just new card)

This is just becoming a pain. I am trying to find another scsi cable to try. I emailed the reseller of our library as we have support through them, but they have been little help.

 

[steveot]

If the cable doesn fix it then its the drive or tapes.

 

[bnordman]

Could it be the scsi controller on the library?

 

[steveot]

Well there is an interface inside the library so yes it could be any of that. I suspect the drive since you are seeing the bad blocks.

 

[bnordman]

So I replaced the SCSI cable and the terminator and no more event id 9, 11, or 15 errors! The only one I am getting now is:

Event Type: Error
Event Source: s32ait
Event Category: None
Event ID: 7

Description:
The device, \Device\Tape4, has a bad block.

This one I’ve gotten 4 times in the last 2 days. It causes the job to fail as well. It’s only been Tape4, no other tape drives.

The above is the only error I see in the System log. I see the below in the Application logs before a job fails:

Event Type: Error
Event Source: Backup Exec
Event Category: Devices
Event ID: 33152

Description:

Adamm Mover Error: Write Failure!

Error = ERROR_CRC
Drive = "SONY 2"
{5801B239-423A-4EF6-9208-17C20D2CA028}
Media = "WK0540"
{7FFFB9DA-179B-45AF-BD8C-BD30B60D8516}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(1), ScsiPass(1)

I am not sure if “SONY 2” = “Tape4” since I swapped drives around. But I can tell you that the SONY 2 error in the app log and the Tape4 error in the System log occurred within a couple minutes of each other right before the job failed with the error, “The job failed with the following error: Error reading/writing data from/to the media.”

So things are looking better: not as many jobs failing due to the scsi errors, now just a few jobs failing a day due to the s32ait errors.

Any ideas on these other errors? These are all brand-new Sony AIT3 tapes. Could be a problem with the tape drive?

 

[steveot]

The drive is bad