AHA-39160 Drivers (windows)

[Chewy509]

Hi Guys,

I've recently had some errors occur (and continue to occur) in the system event log (WinXP x64 SP1) in regards to the installed AHA-39160 SCSI controller (Dell OEM model, with latest v3.10 Dell firmware).

EventID 11 - adpu160m - The driver detected a controller error on \Device\SCSI\adpu160m1.

The service mentioned is 'adpu160m1' which 'adpu10m' being the driver and 1 being the logical device number. However I'm not too sure which channel is being effected, as I've notice no ill effects in the system running. Channel A has a VXA-1 Tape drive, and Channel has 3x 10K.6 Drives. The controller boots off Channel B (since it has 10K.6's attached).

Does Windows allocate it's internal channel number (0 or 1) to the physical channels (A and B) or are they based on the boot setup? (eg 0 would be channel B and 1 would be Channel A).

I've searched through www.eventid.net DB, without any help.

I've also run through all the diagnostic software for both the 10K.6's and the VXA-1 drive (all pass)...

And all drivers and firmware are the latest (for the 39160 and the VXA-1 Tape drive), and have been at least 12months prior to the errors starting.

Any clues?

 

[Mercutio]

That's a worrisome thing to just let lie.

I guess one thing to do would be to disconnect the drives and use them one at a time on different channels, to see if the error persists on the same channel or moves with one or more of the drives.

Or if the controller throws the error with no drives attached.

I hate it when I run across something truly weird like that.

 

[Chewy509]

Well, just after posting, there was an additional error indicating that there was a problem with the VXA-1 drive...

But when I run the Exabyte diagnostic tools, all tests pass... So I replaced the SCSI cable (all the cables I have, have permanent terminators) and for the time being the errors have stopped.

I guess it was just a terminator or cable deciding to slowly die...