Improve company productivity with a Business Account.Sign Up

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 743
  • Last Modified:

EventID 11 Source Disk

Hi Experts!

I keep getting this error in my event log on the server (Compaq Proliant ML350) how do I fix it?
Sometimes after I reboot the server I get an "Inaccessible Boot Device" "blue screen", and I have to go to the recovery console, chkdsk /p, chkdsk /r, fixboot c:, fixmbr to get her humming again, so here's the error. It get's logged frequently.

Event Type:      Error
Event Source:      Disk
Event Category:      None
Event ID:      11
Date:            9/6/2004
Time:            6:12:04 AM
User:            N/A
Computer:      SERVER
The driver detected a controller error on \Device\Harddisk0\DR0.
0000: 04 02 22 00 01 00 72 00   .."...r.
0008: 00 00 00 00 0b 00 04 c0   .......À
0010: 01 01 00 00 00 00 00 00   ........
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 32 14 3f 04 00 00 00   .2.?....
0028: 00 00 00 00 00 00 00 00   ........
0030: 00 00 00 00 2a 00 00 00   ....*...
0038: 02 84 00 00 80 03 04 00   .„..€...
0040: 2a 00 02 1f 8a 19 00 00   *...Š...
0048: 10 00                     ..      


1 Solution

Looks like you might need to contact HP/Compaq for a possible replacement of either the Hard drive or the Hard Drive controller.
Checking on this error you will find that there are many possible solutions.  Here are a few:

See Q885352 if the problem appears when you cancel an I/O operation to a raw USB 2.0-attached hard disk drive in Windows 2000 Server SP4.

From a newsgroup post: "I had event 11 errors and it was a bug in my IBM ServeRaid firmware. Under heavy disk I/O these errors would occur. I updated the firmware and raid drivers and the problem was resolved. Prior to finding out about this bug, I temporarily resolved the problem by defragging my hard drive to reduce disk I/O".

From a newsgroup post: "I had the same error on my MSI board, 1700 AMD XP, 512mb Ram, 2 hard drives each partitioned at 20x20, and Windows 2000 Advanced Server. I was able to fix this problem. It would seem that on many of the motherboards out there windows 2000 does not support different drive types. I change it so each drive was on its own IDE physical connection, and put my CDROM on the second channel as slave. I then removed the "Remote Storage Service". This took care of the errors in Event Viewer. If you have only one drive, ensure you do not have it configured to cable select and update to the latest IDE drivers from your motherboard manufacturer".

Anonymous (Last update 8/31/2004):
In my case, after I disabled S.M.A.R.T. for my IDE drive the problem has not appeared anymore.

Anonymous (Last update 4/16/2004):
Replacing the IDE cable helped me to fix this error.

Corey Monteiro (Last update 3/26/2004):
Boot-up was also very slow when these errors began to occur. I found the cause to be a USB Compact Flash card reader. Boot-up returned to normal speed and errors went away after disconnecting the card reader.

Paol (Last update 3/18/2004):
In my case, there problem was the power source.

Lihai Feng (Last update 10/3/2003):
This problem confused me for weeks. At last I resolved it successfully. I run ms cluster on two pc. They both have a qlogic 1040b scsi adapter, directly connected to digital ba356 scsi storage box. One 1040b's scsi id is 6, and the other is 7. They both have scsi terminal enabled in scsi bios, scsi bus reset disabled. Former I set both adapters id at 7, and encounter event 11 and 9 in my event log.

Giles Collard (Last update 10/3/2003):
I have had the above Event ID on my system logs which would show up as soon as the system had booted and at random times there after. This normally took the form of five or six of the above errors in quick succession. I thought this was due to one of the HD controllers playing up. Tried swapping drives, cables, ports and reinstalling the system on a clean disk. As soon as I installed the system the errors came back. Since then I have traced the problem to the HD caddies I had my drives in, which until last week worked fine. Since I removed the drives from the caddies and connected the IDE cable directly to the drives the error has not reoccurred since.

Adrian Grigorof
As per Microsoft: "ATA66 DMA transfer mode is not supported for the onboard IDE controller." See the link below.
One user solved this by disabling DMA in the BIOS and disabling the Write Cache in Windows 2000.

This error is more likely to have been caused if Intel ATA Mass Storage device driver is installed or if it is an incorrect version. This is especially true if Roxio EZCD Creator is installed. Possible solutions include: Uninstall the Intel driver and reinstall after Roxio EZCD Creator, simple do not use the Intel driver.

I've been encountering this problem for ages. At seemingly random times, my computer would lock itself solid. I had updated the bios on my motherboard to no avail. It finally turns out that the culprit is the USB CompactFlash reader attached to my machine. Any CF cards are mounted as IDE devices, even though they are really connected via USB. Simply removing any CF cards when they are not in use fixed this problem.

I would probably recommend running some HP/Compaq diagnostics on your hard drive(s).  You might have to just troubleshoot this problem with a number of the solutions until you find one that works.  I hope this helps
neomage23Author Commented:

Thanks for the info. I follow your advice and contacted Compaq/HP technical support. We concluded that the behavior could only mean that there was a bad SCSI drive.

The system is under warranty, and Compaq/HP is sending a new drive.

Thanks a bunch for your message.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now