Logical Disk Manager reports that the disk can not be read
This event indicates that the Logical Disk Manager was unable to read data from or write data to a dynamic disk.
This event could be caused by bad disk sectors, or could indicate a total failure of the disk.
The data integrity of the volumes residing on the disk might be affected by the failures. Any applications using these volumes might experience errors.
This event is posted to the system log by Dmio.sys. The system log might contain additional information from other storage drivers that indicates the cause of the failure.
Sample Event:
Event Type: Information
Event Source: dmio
Event Category: None
Event ID: 29
Date: MM/DD/YYYY
Time: HH:MM:SS AM/PM
User: N/A
Computer: Computer_Name
Description:
dmio: Harddisk9 read error at block 445136247: status 0xC000009A
Event Type: Warning
Event Source: dmio
Event Category: None
Event ID: 35
Date: MM/DD/YYYY
Time: HH:MM:SS AM/PM
User: N/A
Computer: Computer_Name
Description:
dmio: Disk Harddisk9 block 445136247 (mountpoint F:): Uncorrectable read error
Event Type: Information
Event Source: dmio
Event Category: None
Event ID: 30
Date: MM/DD/YYYY
Time: HH:MM:SS AM/PM
User: N/A
Computer: Computer_Name
Description:
dmio: Harddisk2 write error at block 411779656: status 0xC000009A
Related Events
Dmio: Event ID 29
Dmio: Event ID 30
Dmio: Event ID 31
Dmio: Event ID 32
Other relevant status codes are:
0xC000000E STATUS_NO_SUCH_DEVICE = A device which does not exist was specified.
0xC0000185 STATUS_IO_DEVICE_ERROR = The I/O device reported an I/O error.
Possible causes include:
A hardware failure that prevents communication with the disk (for example, a disk, controller, or cable failure).
Uncorrectable bad sectors on the disk.
An unexpected removal of the disk.
Do one or more of the following:
1. Open the Disk Management snap-in.
2. Rescan the disks and then reactivate any disks with errors. Resynchronize or regenerate the volume as necessary if the disk was a member of a mirrored or RAID-5 volume.
3. Run chkdsk on any reactivated volumes.
Check the status of your hardware for any failures (for example, a disk, controller, cabling failure). In most cases, the system log contains additional events from the lower-level storage drivers that indicate the cause of the failure.
After you have isolated and resolved the hardware problem:
1. Open the Disk Management snap-in.
2. Rescan the disks and then reactivate any disks with errors. Resynchronize or regenerate the volume as necessary if the disk was a member of a mirrored or RAID-5 volume.
3. Run chkdsk on any reactivated volumes.
Target | Microsoft.Windows.Server.2003.OperatingSystem | ||
Category | EventCollection | ||
Enabled | True | ||
Event_ID | 31 | ||
Event Source | DISK | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
| ||
Event Log | System |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
EventDS | DataSource | Microsoft.Windows.EventProvider | Default |
GenerateAlert | WriteAction | System.Health.GenerateAlert | Default |
<Rule ID="Microsoft.Windows.Server.2003.OperatingSystem.LDMCantReadDisk.Alert" Enabled="onEssentialMonitoring" Target="Microsoft.Windows.Server.2003.OperatingSystem" ConfirmDelivery="true">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="EventDS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>System</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>DISK</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>31</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.Server.2003.OperatingSystem.LDMCantReadDisk.Alert.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>