RAID Controller Module Removed
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.
A RAID controller module was removed from the RAID controller module enclosure. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
This storage array is configured to use dual RAID controller modules, therefore you should re-insert the RAID controller module as soon as you can in order to ensure proper redundancy. Any problem that may arise with the other RAID controller module could result in loss of access to your data.
The virtual disks that were originally owned by the affected RAID controller module have been moved to the alternate RAID controller module. Therefore, the Summary area may also display a Virtual Disk Not on Preferred Path problem. Complete the "RAID Controller Module Removed" Recovery Steps first, and the "Virtual Disk Not on Preferred Path" problem will be resolved automatically. The virtual disks will be automatically redistributed back to the RAID controller module that owns them when the RAID controller module is re-inserted and placed Online. This redistribution will not occur if the RAID controller module is placed Offline and then Online.
If this problem occurred because you were instructed to remove the RAID controller module in the Recovery Steps of a different problem, then disregard this problem and continue with the Recovery Steps for the other problem.
1 | Re-insert the RAID controller module back into its original slot. |
2 | If the RAID controller module was in a non-optimal state prior to it's removal, then you will need to place it online and redistribute the virtual disks manually. Refer to the online help for further assistance. Otherwise, if the RAID controller module was optimal prior to it's removal, then it should transition to an online state and the virtual disks will be redistributed automatically. Go to step 3. |
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 |
Home
<Rule ID="Dell.MDStorageArray.ABBXMLEvent266" 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>266</EventNumber>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent266.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>