Failed I/O Host Card
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.
An I/O host card in one of the RAID controller modules is not functioning properly. 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 will need to replace the RAID controller module that has the failed host card. The failed RAID controller module is listed in the Component requiring service field in the Details area.
To ensure a complete configuration restore (both disk pool and traditional disk group), it is highly recommended that storage array configuration data is backed up prior to executing this procedure. This is especially important for simplex storage arrays, and RAID controller modules that operate without the use of batteries. To save your configuration, open either the Command Line Interface (CLI), or the Script Editor from the Enterprise Management Window (EMW), and execute the following command:
save storageArray dbmDatabase sourceLocation=onboard controller[0] contentType=all file="hostfile.zip";
If... | Then... |
Your storage array has one RAID controller module | Go to 'Procedure for Storage Arrays with One RAID Controller Module.' |
Your storage array has two RAID controller modules | If there are any hosts connected to this storage array that are NOT running a host-based, multi-path failover driver, stop I/O to the storage array from each of these hosts. Go to 'Procedure for Storage Arrays with Two RAID Controller Modules.' |
Procedure for Storage Arrays with One RAID Controller Module
1 | Check the replacement part number of the affected RAID controller module to ensure that the new RAID controller module has the same replacement part number.
| ||||||||||
2 | Stop all I/O to this storage array. | ||||||||||
3 | Turn off power to all power-fan canisters in the enclosure containing the failed RAID controller module. | ||||||||||
4 | Remove the affected RAID controller module. Refer to the Enterprise Management Window to view which management method you are using to manage this storage array.
| ||||||||||
5 | If necessary, insert the battery from the old RAID controller module into the new replacement RAID controller module. Make sure at least 1 minute has elapsed and then insert the new (compatible) RAID controller module firmly into place. | ||||||||||
6 | Turn on power to all power-fan canisters in the enclosure. Wait until all physical disks have completed the spin-up process, and then go to step 7. | ||||||||||
7 | On the Hardware tab in the AMW, select the affected RAID controller module and view the status of the RAID controller module in the Properties pane. | ||||||||||
8 | 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. |
Procedure for Storage Arrays with Two RAID Controller Modules
1 | Place the affected RAID controller module offline.
| ||||||
2 | Read all of the following steps before taking any action. The remaining recovery steps will no longer be accessible from the Recovery Guru dialog after you complete step a.
|
| 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.ABBXMLEvent150" 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>150</EventNumber>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent150.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>