Event ID 9, Drive not detected on Scanning SCSI BIOS

[CA948062]

I have my Compaq External DLT 40/80 Drive and notice some event viewer error:

Event Type: Error
Event Source: adpu160m
Event Category: None
Event ID: 9
Date: 5/4/2005
Time: 2:59:11 PM
User: N/A
Computer: SERVER
Description:
The device, \Device\Scsi\adpu160m2, did not respond within the timeout period.
Data:
0000: fe fe 10 00 01 00 6a 00 þþ....j.
0008: 00 00 00 00 09 00 04 c0 .......À
0010: 00 01 00 00 00 00 00 00 ........
0018: ee fe ee fe 00 00 00 00 îþîþ....
0020: 00 00 00 00 00 00 00 00 ........
0028: ee fe ee fe ee fe ee fe îþîþîþîþ
0030: ee fe ee fe 07 00 00 00 îþîþ....

I have ask our supplier to replace the DLT device but still error occurs. What can I do to fix this error? I do not know if this question fits to this category. By the way, for further details, I have Proliant ML 370 G3 with 3GHz processor running o

[Curtis Ballard]

Event id 9 for the Adaptec cards is not specific. The data you posted seems to be shifted by 1 byte. I inserted an extra byte at the start and got valid data that matches your failure.

Event 9 can be caused by a device error or other problems that have nothing to do with the device. It is a common cause of incorrect replacement because it can be:
- A device failure causing it to not respond to commands
- A command sent with too short of a timeout
- A timeout communicating between the OS and the HBA
- An overlapped command such as a log sense while a write is in progress
- A SCSI bus error causing commands to fail

Counting from byte 0:
Bytes 7/8 are eventcategory
Bytes 13/14/15/16 are IO errorcode 0xc0040009 here (did not respond in timeout)
Bytes 17/18/19/20 are Unique Errorcode 00000100 here. The last 2 bytes, 0100, are the interesting bytes.

For this case 0100 it means that the device did not respond to the HBA in time. 0101 would mean that the HBA did not respond to an OS request.

For this case the problem is something after the OS/HBA connection. It can still be a bad HBA if the output drivers have failed, or a bad SCSI bus. The most common issue I have seen though is a command timeout. The command timeout may mean there is a problem but it could also be expected.

Are you seeing failures at the same time as these events? If you are not geting failures when these events occur then it may not indicate a problem.

[CA948062]

Hi,

I am seeing this error (EID 9) from time to time but I ignore it. My scenario is I have a daily backup scheduled (using veritas backup exec 9.1) and one day, backup didn't ran so I've restart my server and notice that the DLT drive is not being detected and it didn't continue to start up to Windows until I detach the scsi cable to the server. I experience this before(backup didnt ran) about six months ago. The supplier replace the drive but still Event ID 9 occurs but backup is running until I experience it again. Hoping for your idea on how to solve this problem.

[CA1338514]

Seems I have the same Error on ML350G3 with new Ultrium 215i. Have you found the solution?

Michal

[CA1361973]

You probably need to replace the system board. If the SCSI port is soldered to the sysboard you could have a busted solder connection. I see it all the time in the ML370G3