Logical Disk Manager reports a failed disk group import
This event indicates that the Logical Disk Manager was unable to automatically start any dynamic disks and volumes at system startup.
Dynamic volumes will be unavailable for use until the problem is resolved.
This event is posted to the system log by Dmboot.sys. The system log might contain additional information from other storage drivers that indicates the cause of the failure.
Sample Event:
Event Type: Error
Event Source: dmboot
Event Category: None
Event ID: 6
Date: MM/DD/YYYY
Time: HH:MM:SS AM/PM
User: N/A
Computer: Computer_Name
Description:
dmboot: Failed to auto-import disk group Computer_NameDg0. All volumes in the disk group are not available.
Possible causes include:
A hardware failure that prevents communication with any dynamic disk (for example, a disk, controller, or cable failure).
Corruption of all dynamic disks.
Reactivate the disk. To do this:
Open the Disk Management snap-in and check the status of the dynamic disks.
Identify the disks with Missing or Offline status.
Attempt to reactivate the disks using Reactivate Disk.
If that does not resolve the problem, do the following:
1. Open the Disk Management snap-in.
2. Rescan the disks and reactivate the failed disks and volumes. 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. The application and system logs might contain additional events from other storage drivers that indicate the cause of the failure.
Check the status of the disks, controllers, cables, and other hardware.
After the root problem has been isolated and resolved:
1. Open the Disk Management snap-in.
2. Rescan the disks and reactivate the failed disks and volumes. 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 | 6 | ||
Event Source | dmboot | ||
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.LDMAutoImportFailed.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>dmboot</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>6</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.LDMAutoImportFailed.Alert.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>