Partially Complete Disk Group or Disk Pool
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:
Open Start >> Programs >> Dell >> MD Storage Manager >> Modular Disk Storage Manager Client.
If the MD Storage Array is already being managed by MDSM, you can proceed with the Causes and Resolution sections.
From Edit -> Add Storage Array, provide the IP address of the MD Storage Array and Add it to the discovered devices configuration in order to manage it.
Select the MD Storage Array and follow the steps specified in this recovery guru.
One or more physical disks are missing from a disk group or disk pool. There are still enough physical disks remaining that the virtual disks can continue servicing I/O. However, the virtual disks may not be able to continue I/O if more physical disks are removed or fail. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
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
You should fix this problem as soon as possible because further physical disk failures and/or physical disk removals could result in an "Incomplete Disk Group or Disk Pool" problem and loss of data.
For both disk groups and disk pools, this problem can occur for the following reasons:
There was a loss of power to one or more expansion enclosures.
You removed physical disks - either inadvertently or in order to replace the physical disks.
As a result of one or more physical disks being bypassed. If there is a "Bypassed Physical Disk" problem being reported in the Recovery Guru Summary area, complete the recovery steps to correct the "Bypassed Physical Disk" problem first. Only continue with the recovery steps for this problem if it is still displayed after you click Recheck.
You can replace missing physical disks for a disk group or disk pool while the affected virtual disks are receiving I/O.
Affected Disk Groups
For disk groups, this problem can also occur for the following reasons:
You removed physical disks because you intend to export them to another storage array. However, you did not use the export operation available in the MD storage management software to prepare these physical disks before removal.
You inserted physical disks because you intend to import them from another storage array. However, you selected the force import operation in the MD storage management software and not all of the physical disks for the disk group are inserted.
The disk group will be in a Degraded state on the Storage and Copy Services tab.
If a virtual disk is in a disk group and is receiving I/O, then the virtual disk may be displayed as a degraded virtual disk if there is not sufficient hot spare coverage.
Affected Disk Pools
For disk pools, this problem can also occur if you removed physical disks because you intend to export them to another storage array, or inserted physical disks because you intend to import them from another storage array. However, the disk pool feature does not support exporting or importing physical disks.
The only recovery action for a disk pool is to replace any missing physical disks.
The disk pool will be in a Partial state on the Storage and Copy Services tab.
1 |
| ||||||||||||||
2 |
|
Completing a Physical Disk Replacement
1 |
| ||||||||||||||||||||||
2 | Assign a physical disk to take over for the missing physical disk by completing the following steps:
| ||||||||||||||||||||||
3 | Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your Technical Support Representative. |
Completing a Disk Group Export
1 | Reinsert all of the missing physical disks associated with this disk group into the original slots. The Details area provides the physical location of the missing physical disks as well as the affected disk group. |
2 | Wait for the disk group and its associated virtual disks to display an Optimal status. |
3 | On the Storage and Copy Services tab in the Array Management Window, select the disk group you want to export. |
4 | Select the Storage > Disk Group > Advanced > Export menu option. |
5 | Follow the instructions in the Export Disk Group wizard to successfully export the disk group. |
6 | Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your Technical Support Representative. |
Completing a Disk Group Import
1 | Insert all of the missing physical disks associated with this disk group with the original physical disks from the source storage array. The Details area provides the physical location of the missing physical disks as well as the affected disk group. Note: If the original physical disks are not available, you can also use the Replace Physical Disk option in the MD storage management software to reconstruct other unassigned physical disks in the storage array to take over for the missing physical disks. |
2 | Wait for the disk group and its associated virtual disks to display an Optimal status. |
3 | Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your Technical Support Representative. |
Target | Microsoft.SystemCenter.ManagementServer | ||
Category | Alert | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
|
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 |
<Rule ID="Dell.MDStorageArray.ABBXMLEvent421" 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>421</EventNumber>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent421.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>