My Adaptec 19160 has been working flawlessly for two months, and all of a sudden, I started hearing my SCSI drive attached to my controller stop suddenly during an access, then spin up. I have two SCSI HDs attached to the card, a Fujitsu 10k uw160 and a Seagate 318406lw. The seagate is the one that is giving me problems.
I thought it might be the drive, so I downloaded seagate's bootable drive fitness tester, but the drive came up clean.
I also copied the data off, wiped the drive, repartitioned, and reformated, but the errors persist.
The eventids that are showing up are
The driver detected a controller error on \Device\Scsi\adpu160m1
with an eventid of 11.
Looking at the event log itself, the error thrown by the controller is
[xxxxx022] Adapter or target device protocol error
The adapter or target device has broken the communication protocol. A badly behaving device could cause this message to appear. Normally this is not a serious problem. If you get this message frequently over a short period of time, it could indicate that the device or system is malfunctioning. Unplug or power down unused devices to see if the problem persists.
I the tried to update the driver, but the embedded windows one is all that is available. If I go to adaptec, they have a beta driver that is 3 years old and doesn't address this problem.
Any assistance would be greatly appreciated.
I thought it might be the drive, so I downloaded seagate's bootable drive fitness tester, but the drive came up clean.
I also copied the data off, wiped the drive, repartitioned, and reformated, but the errors persist.
The eventids that are showing up are
The driver detected a controller error on \Device\Scsi\adpu160m1
with an eventid of 11.
Looking at the event log itself, the error thrown by the controller is
[xxxxx022] Adapter or target device protocol error
The adapter or target device has broken the communication protocol. A badly behaving device could cause this message to appear. Normally this is not a serious problem. If you get this message frequently over a short period of time, it could indicate that the device or system is malfunctioning. Unplug or power down unused devices to see if the problem persists.
I the tried to update the driver, but the embedded windows one is all that is available. If I go to adaptec, they have a beta driver that is 3 years old and doesn't address this problem.
Any assistance would be greatly appreciated.
Facebook
Twitter