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. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: Various sources|
The device, <device path>, did not respond within the timeout period.
|English: This information is only available to subscribers. An example of English, please!|
"Also, this error can be generated by a defective hard drive. 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 disk drive named and on its controller. You might have to contact the vendor of the device for technical support.
It has also been reported that IDE tape drives (i.e. Seagate IDE Travan) may generated this type of errors."
- \Scsi\IntelATA2 - intelata - no info
- \Ide\IdeDeviceP0T0L0 - IdeChnDr - no info
- \Scsi\ini910u1 - ini910u - no info
- \IdeDeviceP0T0l0 - no info
- \Scsi\sym_u31 - no info
If you use EMC Symmetrix disk arrays see ME248191 link below.
It is generated when the device cannot initialize within the normal time period, or when it stops responding during normal operation. The event source is the device driver name. This occurs on one of the following three circumstances:
- a drive or device controller cannot initialize due to hardware failure or IRQ conflict. If you have installed new hardware, remove it and read the installation manual again.
- a device reports to the PnP service but does not respond to the OS. try rebooting.
- a removable media on the mass controller that generated the error (like backup tape, DLT, or CDROM) is badly written and the drive resets so frequently that it doesn''t report to the OS. Avoid piracy :-)
On my dual-controller Advansys U160 SCSI card, I got rid of this W2K pro error by doing two things:
1) set PCI#2 access #1 Retry in Advanced Chipset BIOS to DISABLED
2) disable any unused SCSI channels within device manager
\Ssci\aic78u21 - First, make sure the scsi chain is correct, even if it has always been so. Check termination. Check everything that could possibly be wrong with the drive itself. If nothing obvious appears, try switching the device to a different controller card. This issue almost always points to a hardware problem, and most of the time it is the card that is to blame (too many devices, improper termination, etc).
\Scsi\HPT3xxNT1 - Occured on my ABIT KG7 RAID. Upgrading RAID driver to v2.0.919.0 appears to solve problem. Driver available at www.highpoint-tech.com.
As per ME289189: "This behavior can occur when the events are logged in the precise code location where the receiving side of a TCP connection stops receiving data, leaving the connection open. This causes the sender side to fill up the TCP window and eventually stop responding in the send call. To resolve this problem, obtain the latest service pack for Windows 2000."
\Scsi\ql22001 - This is related to the Q-Logic 2200 GBIC interface. No additional info.
\ScsiPort0 - See the information about this event ME182335 - "The SCSI adapter (HBA) did not respond to the system after an I/O has been issued."
\Ide\ideport1 - This occured during the Onstream backup drive scheduled backup. The tape was not in drive due to delay winding tape on bootup.
\Scsi\ultra1 - This is happening on my promise ultra66 ide controller card. It seemed like it didn't hurt anything, but it would not allow me to restore from a backup tape device connected to the card. I reconnected the tape drive to the motherboard's on-board IDE controller and restored without any problems. Now, though, I worry that it may occasionally corrupt my backup tapes.
\Scsi\mraid2k1 - The source of this error turned out to be our RAID controller driver. The RAID controller however wasn't malfunctioning. A disk in our RAID 5 array was degrading to the point that we were unable to get a backup for a couple of days. Fortunately no data was lost but the error reporting directly from the controller only sporadically showed media errors. The only consistent and true error reporting was our Windows2000 event viewer. Our hardware manufacturer tried repeatedly to discount the Windows2000 errors but they turned out to be correct.
\Scsi\dpti2o1 (Adaptec I2O RAID Host Adapters) - So far the only remedy I know is a reboot.
Venkatesh Babu G
\ScsiPort1 - See ME259237: For clusters, this could be caused in some configurations by powering on or off devices on the shared bus, if the bus is differential. Time-out events could indicate cabling, termination, or SCSI hardware configuration problems.
|Private comment: Subscribers only. See example of private comment|
|Links: ME154690, ME126380, www.highpoint-tech.com, ME289189, ME248191, ME259237|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated