Logical Disk Manager reports a volume has not started
This event indicates that the Logical Disk Manager was unable to automatically start a dynamic volume at boot time. The volume that the Logical Disk Manager could not start is identified by its drive letter (if any).
The data on this volume is 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: 3
Date: MM/DD/YYYY
Time: HH:MM:SS AM/PM
User: N/A
Computer: Computer_Name
Description:
dmboot: Failed to start volume Volume2 (E:)
Data:
0000: 00 00 00 00 03 00 4e 00 ......N.
0008: 00 00 00 00 03 00 50 c0 ......PÀ
0010: 00 00 00 00 00 00 00 00 ........
0018: 01 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
Possible causes include:
A hardware failure that prevents communication with a disk that is a member of this volume (for example, a disk, controller, or cable failure).
Corruption of a disk that is a member of this volume.
Possible resolutions include the following:
1. Open the Disk Management snap-in and check the status of the disks that are members of the volume.
2. Identify the disks with Missing or Offline status.
3. Attempt to reactivate the disks using Reactivate Disk.
1. Open the Disk Management snap-in.
2. Rescan the disks and then reactivate any 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.
Reactivate the disk.1. Open the Disk Management snap-in and check the status of the disks that are members of the volume.2. Identify the disks with Missing or Offline status.3. Attempt to reactivate the disks using Reactivate Disk.
Check the hardware status for any failures. The event log 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 you have isolated and resolved the hardware problem, rescan and reactivate any failed disks and volumes. To do this:1. Open the Disk Management snap-in.2. Rescan the disks and then reactivate any 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.2000.OperatingSystem | ||
| Category | EventCollection | ||
| Enabled | True | ||
| 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 |
Home<Rule ID="Microsoft.Windows.Server.2000.OperatingSystem.LDMVolumeNotStarted.Alert" Enabled="onEssentialMonitoring" Target="Microsoft.Windows.Server.2000.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>
<Or>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>2</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>3</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</Or>
</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.2000.OperatingSystem.LDMVolumeNotStarted.Alert.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>