Error Atapi 9
Contents |
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to disk error 51 see an entire company using just one server, these days that's no longer the case. New atapi error event 9 computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on
Error Atapi 11
these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on
Atapi Incompatible Error
any of the servers. read more... Event ID: 9 Source: atapi Source: atapi Type: Error Description:The device, \Ide\IdePort0, did not respond within the timeout period. English: This information is only available to subscribers. An example of English, please! Comments: Anonymous In my case, this problem was solved after uninstalling KASPERSKI AV/IS. x 11 Anonymous In my case, error indicated \Device\Ide\IdePort1. Upon going to registry, went to regedit and navigated to hkey_local_machine\hardware\devicemap\scsi\scsi port 1 - noticed it atapi error 11 device ide ideport0 was labeled as "cdrom peripheral" - replaced cdrom drive, no more errors. x 4 John Panton Message: IDE-port 0 not responding within the timeout period. It could be HDD 0 or IDE/ATAPI controller, but first: - Check the cables from the MB to the HDD. - Check the operation of any other devices connected to the same cable as HDD 0- even disconnect any CD/DVD drives on that cable. x 9 Alexander Solano In my case, this problem was solved after uninstalling Roxio's Easy CD Creator 5.0. There are known compatibility issues between Windows XP and versions of Easy CD Creator earlier than version 5.1. See ME310628 for details. x 51 Peter Hayden In one case, a computer was running Windows 2000 Professional SP4 that was configured to boot from a SCSI drive. An IDE drive was temporarily added in order to perform some work on it. When the computer was started this event was repeated four times and then followed by EventID 11 from source atapi. Windows showed the disk as normal but Partition Magic 8.0 showed it as "BAD". Remove or replace the faulty hard drive. x 54 Anonymous Getting this error could mean that your hard disk controller is not working well. Check to see if you have difficulty accessing the hard disk (slow), or if the hard disk is having trouble powering up. Even though the contr
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server http://serverfault.com/questions/44210/event-log-atapi-the-device-did-not-respond-within-the-timeout-period-freeze Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Event Log: atapi - the device did not respond within the timeout period - Freeze up vote 0 down vote favorite I have a Windows Server 2003 that stops working randomly (displays image on atapi error monitor but is completely frozen), all I could found on the event log as causes were an error from atapi and a warning from msas2k3. The event log entries are: Event Type: Error Event Source: atapi Event Category: None Event ID: 9 Date: 22-07-2009 Time: 16:13:33 User: N/A Computer: SERVER Description: The device, \Device\Ide\IdePort0, did not respond within the timeout period. For more information, see Help and Support Center at http : // go.microsoft.com / fwlink / events.asp. Data: 0000: 0f 00 10 00 01 00 64 error atapi 9 00 ......d. 0008: 00 00 00 00 09 00 04 c0 .......À 0010: 01 01 00 50 00 00 00 00 ...P.... 0018: f8 06 20 00 00 00 00 00 ø. ..... 0020: 00 00 00 00 00 00 00 00 ........ 0028: 00 00 00 00 01 00 00 00 ........ 0030: 00 00 00 00 07 00 00 00 ........ Event Type: Warning Event Source: msas2k3 Event Category: None Event ID: 129 Date: 22-07-2009 Time: 16:14:23 User: N/A Computer: SERVER Description: Reset to device, \Device\RaidPort0, was issued. For more information, see Help and Support Center at http : // go.microsoft.com / fwlink / events.asp. Data: 0000: 0f 00 10 00 01 00 68 00 ......h. 0008: 00 00 00 00 81 00 04 80 ...... 0010: 04 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 00 00 00 00 00 00 00 00 ........ 0030: 01 00 00 00 81 00 04 80 ...... Any hints? windows-server-2003 raid windows-event-log share|improve this question asked Jul 22 '09 at 18:57 rjlopes 8329 add a comment| 3 Answers 3 active oldest votes up vote 1 down vote I'm aware that this is an old question, but I've replaced many a burnt-out consumer motherboard for this when the user tries overclocking and manages to run the southbridge outside of spec. SATA controller pooches itself and starts to throw these errors. I'd have a suspicious look at your RAID controller; all t