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.
dmio: Harddisk0 write error at block <block number>: status <status code>
|English: Request a translation of the event description in plain English.|
See ME159865 to find out how to distinguish a physical disk device from an event message.
See the link to "Veritas Support Document ID: 252111" if you are using VERITAS Volume Manager for Windows 2000.
From a newsgroup post: "Look at your "boot.ini" file and make sure you are not using both the "/3GB" and "/PAE" switches together. Using either of these switches will take a toll on some resources and using both is not recommended. Doing so can cause blue screens or dmio issues like what you are having".
I was seeing three of these errors, status 0xc0000015, every time I started Windows 2000 server. It was on a hard disk, which I had recently moved onto a Promise FastTrak onboard ATA-133 RAID channel. I found that somebody who had experienced a similar problem had solved it by reformatting the disk, so I copied all of the data to another partition and then initially tried a quick format. No luck, then a full format, still no luck, then finally I downloaded the hard disk manufacturer's utility program and checked the disk (just to confirm there were no actual physical errors on it – there were not), then performed a low-level format. This seems to have solved the problem. I am not getting the three write error messages any more in Windows 2000. However, if I boot directly into Norton Ghost then I still get some Bad Block errors.
The event ID's 37, 50, and 30 have been showing up with a dmio source for about a week now on our IBM Netfinity 5100 with an EXP300 external SCSI raid cage. A tech support call to IBM lead us to run the ServeRAID Mgr. software and send the log files to IBM. This revealed that we had two drives with errors. So we then were asked to run a second log file/dump file with a utility that IBM sent us and it showed we have 2 bad stripes on our Raid 5. We are getting two new drives sent to us because we have bad blocks that are the main cause of these errors (according to IBM). The bad stripes we are just going to have to live with since putting new drives in will not fix the stripes only the blocks. I just hope we do not have to get at the data that went on those stripes. Hope this helps anyone else with these errors.
Status 0xc0000015 - I have got this error after a hard disk crashed.
Block 1006044368 : status 0xc0000015. My harddisk (A 10, 24 Go MPF3102AT fujitsu) was not well recognized by the Bios (detecting 136 Go). I've update my Bios and all is OK.
Status 0xc0000185 Check cable.
Status 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
Status 0xC000009C, or STATUS_DEVICE_DATA_ERROR, generally indicates bad blocks (sectors) on the hard disk.
Status 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose data or power cables, a problem with SCSI termination, or improper controller or hard disk configuration.
Status 0xC000016A, or STATUS_DISK_OPERATION_FAILED, also indicates bad blocks (sectors) on the hard disk.
Status 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination, defective storage controller hardware, defective disk cabling, or two devices attempting to use the same system resources.
|Private comment: Subscribers only. See example of private comment|
|Links: ME159865, ME329075, Veritas Support Document ID: 252111|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated