Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 11 Source: adpu160m

Source
Level
Description
The driver detected a controller error on \Device\Scsi\adpu160m1
Comments
 
This event might especially occur under the following conditions:
A SCSI harddisk installed using an SCA-Adapter.
The harddisc is located on rubber attenuators to uncouple the harddisc to silence the drive.
The SCSI Bus is set to LVD Mode

Reason: No connection between the harddisk and the case so there''s no ground connection.
Solution: Simply ground the harddisc enclosure by connecting it with a small wire to the case (or anything else grounded).
This error can occur when running the HP/Compaq Tape and Library tools to upgrade firmware on an HP/Compaq server. When the hardware device scan occurs, the tool generates these errors in the event log. If you see the EventID error (along with an EventID 117 and EventID 9 from adpu160m) generated only when you run the HP Tape and Library tool then you can safely ignore it.
Error messages generated by the adpu160m.sys driver can be viewed by opening the Windows NT Event Viewer error logs. To view events generated by the driver, follow these steps:

Double-click the Event Viewer icon in the Administrative Tools program group. Error messages generated by the driver show up as Event ID 11. Error messages generated by the SCSI port show up as Event ID 9.

To view event details, select System from the Log menu. Double-click the adpu160m.sys driver event that has an Event ID of 11. (There may be none or multiple driver events.)
The top portion of the Event Detail dialog box displays information such as the time that the event was generated, the computer on which the event occurred (in case of remote monitoring) and the description of the event. The Data section of the Event Details dialog box displays the error messages generated.

Click the Words radio button.
In the Data section of the dialog box, the entry in the second row and second column (to the right of the 0010: entry) lists the error message generated by the driver. The common error messages for the driver are described below.

NOTE: The entry in the third row of the last column identifies the SCSI ID of the device originating the error.

adpu160m.sys Error Messages
The following error messages are listed sequentially according to the last three digits of the error message. For example, [xxxxx010], [xxxxx011], [xxxxx012], etc.

NOTE: When reporting problems to Customer Support, be sure to include the complete error message in your problem description.

[xxxxx004] Command completed with error
[xxxxx005] Command completed with error
[xxxxx006] Command completed with error
A request issued to a target device completed with indication that there is an error. In most cases, the error is recovered and normal operations continues.

[xxxxx010] Error issuing command
An error has occurred while the driver was setting up its internal datastructures.

[xxxxx011] Error issuing command
The requested command is not supported by this driver.

[xxxxx012] Error issuing command
[xxxxxx99] Error issuing command
The driver does not recognize the target device.

[xxxxx021] Target device protocol error
An unexpected event occurred during data transfer between the adapter and target device. Normally, this indicates a faulty or non-compliant target device.

[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.

[xxxxx023] Target device parity error
The driver has detected a parity error by the target device.

[xxxxx024] Data overrun or underrun
The adapter was given more or less data than the expected amount of data.

[xxxxx031] Target device queue full
The target device internal buffer is full.

[xxxxx032] Target device busy
The target device reports a Busy status. Another program may already be using this device.

[xxxxx050] Host adapter failure
[xxxxxx9A] Host adapter failure
Your host adapter may not be properly installed or is defective. Try resetting the adapter in the PCI slot, or try installing it a different PCI slot.

[xxxxx081] Adapter initialization failure
[xxxxxx8A] Adapter initialization failure
[xxxxxx83] Adapter initialization failure
An error has occurred while the driver was setting up its internal data structures. Verify that your adapter is supported by this version of the driver.

[xxxxx089] Unable to allocate memory
This indicates that there may be a problem with the amount of memory installed in your system. Verify that your system has at least the minimum amount of memory required by your operating system.

[xxxxx096] Adapter hardware initialization failure--possible resource conflict
The driver has attempted to initialize the adapter hardware but failed. This might suggest that the adapter resources (e.g., IRQ) conflict with another board installed in your system.

[xxxxx097] Unable to allocate memory
This indicates that there may be a problem with the amount of memory installed in your system. Verify that your system has at least the minimum amount of memory required by your operating system.

[xxxxx0af] Unable to de-allocate memory that was allocated for a target device
Normally, this is not a serious problem, unless you get this message frequently over a short period of time. The memory can be reclaimed by rebooting the system.

[xxxxx0ce] Scatter/gather limit exceeded
An I/O request packet from the system contained a Scatter/Gather element list that contained more elements than are supported by the miniport. Scatter/Gather is a list of data segments that define the entire data transfer. Scatter/Gather is a means to improve total data throughput. This error might be caused by a component external to the miniport driver, such as the operating system or an ASPI application.

[xxxxxd4] Adapter hardware failure - adapter reset
The host adapter hardware failed and the miniport has to reset the hardware.

[xxxxx0d6] Internal driver error
An error has occurred while the driver was setting up its internal data structures. Try installing the most up-to-date version of the driver available from the Adaptec Web site.
See ME154690 for a troubleshooting approach. Some contributors considered some of these errors as being caused by faulty SCSI devices attached to the controllers (i.e CD-ROM drives). Also you can check the cabling on the device named in the message. If the cabling is working satisfactorily and you continue to receive this message, run hardware diagnostics on the device. You might have to contact the vendor of the device for technical support, or you might have to replace the controller. The problem can be with the controller itself but most likely with the devices attached to it (like SCSI hardrives or tape drives).

See the link to "EventID 11 from source Disk" for additional information on this event.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Read more...

 

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Read more...