Battery Failed
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 battery has failed. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Caution: Electrostatic charges 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
Contact your Technical Support Representative if you do not have a replacement battery available.
The purpose of the battery is to preserve cached data in the event of a power failure. Therefore, you should replace the battery as soon as possible.
Write caching for all virtual disks has been automatically suspended (if previously enabled). Write caching will be reinstated (if applicable for each virtual disk) once you replace the battery and the replacement battery is charged to a sufficient level to support cached data in the event of a power failure.
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";
Refer to the Component requiring service field in the Details area to determine which recovery steps you need to complete.
Recovery Steps for a Battery Inside a RAID Controller Module
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 | Go to 'Procedure for Storage Arrays with Two RAID Controller Modules' |
Procedure for Storage Arrays with One RAID Controller Module
1 | Stop all I/O from all hosts to this storage array. When the Cache Active LED on the RAID controller module is no longer active (up to 5 minutes), proceed to step 2. Caution: Risk of Data Loss. You must wait for the Cache Active LED to stop blinking to ensure that all cache has been written to the physical disks in the storage array. | ||||||
2 | Click the Save As button in the Recovery Guru dialog to save the remaining steps to a file. These steps may no longer be accessible from the Recovery Guru dialog after you complete step 3. | ||||||
3 | Remove the RAID controller module that contains the affected battery. | ||||||
4 | Replace the affected battery with a new battery. Refer to your hardware documentation for the battery replacement procedure. | ||||||
5 | Insert the RAID controller module (containing the new battery) securely into place. After the RAID controller module appears on the Hardware tab in the Array Management Window, go to step 6. Note:
| ||||||
6 | Select the Hardware > Enclosure > Change > Battery Settings... menu option. | ||||||
7 |
| ||||||
8 | Record the installation date (today's date) and the new replacement date (according to the battery's warranty). | ||||||
9 | Select the battery you just replaced, and then click the Reset button to set the affected battery's age to zero. | ||||||
10 | 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 | 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. | ||||||
2 | Place the affected RAID controller module offline.
| ||||||
3 | Click the Save As button in the Recovery Guru dialog to save the remaining steps to a file. These steps may no longer be accessible from the Recovery Guru dialog after you complete step 4. | ||||||
4 | Click the Recheck button to rerun the Recovery Guru. There should be an "Offline RAID Controller Module" problem reported in the Recovery Guru Summary area. | ||||||
5 | Follow the "Offline RAID Controller Module" recovery steps until you have removed the RAID controller module. After you have removed the RAID controller module, do not continue with the "Offline RAID Controller Module" recovery steps until you are instructed to do so in this procedure. | ||||||
6 | Replace affected battery with a new replacement battery. Refer to your hardware documentation for the battery replacement procedure. Note:
| ||||||
7 | Complete the remaining "Offline RAID Controller Module" recovery steps, then go to 8. | ||||||
8 | Select the Hardware > Enclosure > Change > Battery Settings... menu option. | ||||||
9 |
| ||||||
10 | Record the installation date (today's date) and the new replacement date (according to the battery's warranty). | ||||||
11 | Select the battery you just replaced, and then click the Reset button to set the affected battery's age to zero. | ||||||
12 | 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.ABBXMLEvent6" 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>6</EventNumber>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent6.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>