time out errors

[Jeff Tolly]

Have a Proliant 5000 with support paq 5.5b.

The server runs fine but when connected to a StorageTek L40 tape library (not my choice)/Veritas 8.6, both have latest drivers and firmware, via internal SCSI interface we get time out errors.

Event Type: Error
Event Source: Cpq32fs2
Event Category: None
Event ID: 9
Description:
The device, \Device\Scsi\Cpq32fs21, did not respond within the timeout period.
Data:
0000: 0010fefe 006a0001 00000000 c0040009
0010: 00000100 00000000 feeefeee 00000000
0020: 00000000 00000000 feeefeee feeefeee
0030: feeefeee 00000007

Configured a 64bit/66MHz Ultra3 SCSI adapter but am getting the same timeout errors.

Event Type: Error
Event Source: adpu160m
Event Category: None
Event ID: 9
Description:
The device, \Device\Scsi\adpu160m1, did not respond within the timeout period.
Data:
0000: 00100000 006a0001 00000000 c0040009
0010: 50000101 00000000 00000000 00000000
0020: 00000000 00000000 00000000 00000000
0030: 00000000 00000007

The SCSI cable is fine and have tried others with the same results.

Have no settings on the 5000 to tweak except for the internal SCSI adapter for SCSI 1 or 2, it is set to 2.

Can someone explain these timout period errors and if there are any steps or tweaks I need to make please let me know. Would like to get some backups going.

Thank you

[Christopher Moshier]

You might look at the following Q articles that were given to me by HP after I experienced the same along with Event ID:50 which were the failure to write.

Q325040
Q329945

Hope it helps, the articles didn't seem to have my exact problem but the Rep. said these are what's fixing the problems that are being experienced.

[Jeff Tolly]

Searched for the Q articles but couldn't find them? Do you have a URL or location that I can find these?

Thank you

[Christopher Moshier]

These are Microsoft Q articles, here is the links.

http://support.microsoft.com/default.aspx?scid=kb;en-us;816004

http://support.microsoft.com/default.aspx?scid=kb;en-us;325040

http://support.microsoft.com/default.aspx?scid=kb;en-us;329945

They all don't seem to be directly related to the problems we were having as well as you but we have not experienced the problems since testing and putting the hotfixes on for W2K sp3