Redundancy Group Not Consistent
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.
During a reconfiguration operation with Pre-Read Redundancy enabled, a data inconsistency was found. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
The reconfiguration operation will continue and it will update the parity information to be consistent with the data; however, loss of data access could occur.
When this problem occurs, the RAID controller module firmware tries to determine which virtual disks in a disk pool or disk group are affected by the loss of cached data. If this determination can be made, the affected virtual disks are marked as Offline. Otherwise, the associated disk pool or disk group is marked as Offline. The affected virtual disks are considered to be corrupted because there is a data inconsistency that cannot be resolved. A critical event is logged to the Major Event Log.
Caution: Loss of data access. Data on the affected virtual disks will not be accessible unless you can restore the data from a replicated virtual disk or another backup medium, or if the applications using those virtual disks have their own mechanisms for recovering from corrupted data.
1 |
| ||||||||||||||||||||||||
2 | Review the Recovery Guru Details area to identify the affected virtual disk. Note: The affected virtual disk is currently the primary virtual disk in the replicated relationship. | ||||||||||||||||||||||||
3 | On the Storage and Copy Services tab in the Array Management Window (AMW), identify the secondary virtual disk and associated remote storage array that completes the replicated pair with the primary virtual disk. | ||||||||||||||||||||||||
4 | Since the primary virtual disk is offline, the replicated pair must be broken from the secondary virtual disk. To do this, open the AMW for the secondary virtual disk. | ||||||||||||||||||||||||
5 | Perform the following steps to break the replication relationship:
| ||||||||||||||||||||||||
6 | The primary virtual disk can now be placed online. To do this, open the AMW for the primary virtual disk (this storage array) and perform the following steps:
| ||||||||||||||||||||||||
7 | Perform the following steps to break the replication relationship from the primary virtual disk:
| ||||||||||||||||||||||||
8 | In order to completely synchronize the two virtual disks and restore the data, the current primary virtual disk (on this storage array) must be reestablished in the remote replication as the secondary virtual disk, and the current secondary virtual disk must be reestablished as the primary virtual disk. To do this, open the AMW for the storage array that is the local storage array for the secondary virtual disk identified in step 3. NOTE: Ensure that both RAID controller modules in the storage array are online before continuing with the remaining steps of the recovery procedure. | ||||||||||||||||||||||||
9 | Perform the following steps to reestablish the replication relationship between the two virtual disks:
| ||||||||||||||||||||||||
10 | After synchronization has completed, highlight the new primary virtual disk on the Storage and Copy Services tab in the AMW. | ||||||||||||||||||||||||
11 | Select the Copy Services > Replication > Remote Replication (Legacy) > Change > Role to Secondary option. | ||||||||||||||||||||||||
12 | After the process has completed, 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.ABBXMLEvent402" 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>402</EventNumber>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent402.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>