Home
  •  

Dell MD Array Degraded Virtual Disk

Dell.MDStorageArray.ABBXMLEvent13 (Rule)

Knowledge Base article:

Summary

Degraded Virtual Disk

The causes and resolutions refer to the Dell Modular Disk Storage Manager recovery guru. Launch Dell Modular Disk Storage Manager to diagnose and fix the recovery failure as follows:

Causes

One or more physical disks have failed in a disk pool or disk group and the associated virtual disks have become degraded. The data on the virtual disks is still accessible; however, data may be lost if another physical disk in the same disk pool or disk group fails. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Caution: Possible loss of data accessibility. Do not remove a component when either (1) the Service Action (removal) Allowed (SAA) field in the Details area of this recovery procedure is NO, or (2) the SAA LED on the affected component is OFF (note that some products do not have SAA LEDs). Removing a component while its SAA LED is OFF may result in temporary loss of access to your data. Refer to the following Important Notes for more detail.

Caution: Electrostatic discharge can damage sensitive components. Always use proper antistatic protection when handling components. Touching components without using a proper ground may damage the equipment.

Important Notes

Resolutions

1

Check the Recovery Guru Details area to identify the failed physical disk(s).

2

Remove all failed physical disks associated with this disk pool or disk group (the fault indicator lights on the failed physical disks should be on).

Note: To determine the failed physical disks, select one of the degraded virtual disks (identified in the Details area) on the Storage and Copy Services tab in the AMW. Each failed physical disk will have an association dot underneath it.

3

Wait 30 seconds, then insert the new physical disks. The fault indicator light on the new physical disks may become lit for a short time (one minute or less).

Data reconstruction should begin on the new physical disk(s). Their fault indicator lights will go off and the activity indicator lights of the physical disks in the disk pool or disk group will start flashing. When the reconstruction starts, the disk pool or disk group's virtual disk icons on the Storage and Copy Services tab in the AMW change to Operation in Progress, then to Optimal, as the virtual disks are reconstructed.

Notes:

  • If you are replacing a physical disk in a storage array that contains hot spares, physical disk reconstruction will start on the hot spare before you insert the new physical disk. The data on the replacement physical disk may not be reconstructed until after it has completed the process on the hot spare.

  • If reconstruction does not start within a few minutes, select the new physical disk; then, select the Hardware > Physical Disk > Advanced > Manually Reconstruct... menu option to start reconstruction on the physical disk.

  • To monitor reconstruction progress on the affected virtual disks, on the Storage and Copy Services tab in the AMW, select the reconstructing virtual disk and view the progress in the Properties pane. Note that once the operation in progress has completed, the progress bar is no longer displayed in the Properties pane.

  • Replace only one physical disk at a time for each disk pool or disk group. Each physical disk should complete reconstruction before the next physical disk begins reconstruction.

  • Wait until the reconstruction is completed for all virtual disks before continuing.

4

Click the Recheck button to rerun the Recovery Guru. When ALL failed physical disks are replaced, then this failure should no longer appear in the Summary area. If the failure appears again after all failed physical disks have been replaced, contact your Technical Support Representative.

Element properties:

TargetMicrosoft.SystemCenter.ManagementServer
CategoryAlert
EnabledTrue
Alert GenerateTrue
Alert SeverityWarning
Alert PriorityNormal
RemotableTrue
Alert Message
Dell MD Array Degraded Virtual Disk
{0}

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.Windows.ScriptGenerated.EventProvider Default
Alert WriteAction System.Health.GenerateAlert Default
WriteToDW WriteAction Microsoft.SystemCenter.DataWarehouse.PublishEventData Default

Source Code:

<Rule ID="Dell.MDStorageArray.ABBXMLEvent13" Enabled="onEssentialMonitoring" Target="SystemCenter!Microsoft.SystemCenter.ManagementServer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>Alert</Category>

  <DataSources>

    <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.ScriptGenerated.EventProvider">

      <ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <ScriptName>RBODEventGenerator</ScriptName>

      <EventNumber>13</EventNumber>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">

      <Priority>1</Priority>

      <Severity>1</Severity>

      <AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent13.StringResource"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Data/EventDescription$</AlertParameter1>

      </AlertParameters>

      <Suppression>

        <SuppressionValue>$Data/EventDisplayNumber$</SuppressionValue>

        <SuppressionValue>$Data/Channel$</SuppressionValue>

        <SuppressionValue>$Data/PublisherName$</SuppressionValue>

        <SuppressionValue>$Data/LoggingComputer$</SuppressionValue>

        <SuppressionValue>$Data/EventCategory$</SuppressionValue>

        <SuppressionValue>$Data/EventLevel$</SuppressionValue>

        <SuppressionValue>$Data/UserName$</SuppressionValue>

        <SuppressionValue>$Data/EventNumber$</SuppressionValue>

        <SuppressionValue>$Data/EventDescription$</SuppressionValue>

      </Suppression>

      <Custom1/>

      <Custom2/>

      <Custom3/>

      <Custom4/>

      <Custom5/>

      <Custom6/>

      <Custom7/>

      <Custom8/>

      <Custom9/>

      <Custom10/>

    </WriteAction>

    <WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishEventData"/>

  </WriteActions>

</Rule>