Mixed Physical Disk Types - Out of Compliance
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.
The Mixed Physical Disk Types feature is Out of Compliance. This problem can occur in the following scenarios:
Scenario 1 (Most common scenario) - The storage array contains a mix of physical disk types (such as Serial ATA (SATA) and Fibre Channel) but the Mixed Physical Disk Types feature is not enabled or is not supported by this storage array.
Scenario 2 (Less common scenario) - The storage array MAY or MAY NOT contain a mix of physical disk types, however, you connected physical disks to one or more RAID controller modules where 1) the RAID controller modules were NOT previously attached to any physical disks, and 2) the physical disks were already previously configured while attached to other RAID controller modules where the Mixed Physical Disk Types feature was supported and enabled.
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
This problem can occur if you disable a feature pack key. Disabling a feature pack key can result in multiple individual features transitioning to an Out of Compliance state since you may have globally lowered the limits supported by the storage array. If there is a "Feature Pack - Out of Compliance" problem in the Summary area, complete those recovery steps first. If this problem still appears after you complete the recovery steps for the "Feature Pack - Out of Compliance" problem, then proceed with the recovery steps below.
Scenario 1 typically happens because you performed one of the following actions:
Disabled the Mixed Physical Disk Types feature while mixed physical disk types are still present
Enabled or disabled a feature pack resulting in the storage array not supporting Mixed Physical Disk Types.
Imported physical disks of a different technology from those already residing in this storage array (for example, you add SATA physical disks to a storage array that previously contained only Fibre Channel physical disks) while the Mixed Physical Disk Types feature was disabled
Scenario 2 happens because the RAID controller modules were not previously attached to physical disks, so the RAID controller modules 'adopt' the configuration database of the first physical disk they encounter. When physical disks are adopted by the RAID controller modules, the configuration database contained on the physical disks (which includes all of the information about the previous storage array, including the enabled/disabled information of features) is used by the RAID controller modules. Therefore, the information in the configuration database shows that the Mixed Physical Disk Types feature is enabled, but the feature is either disabled on this storage array or not supported by the RAID controller modules. If the RAID controller modules had been previously attached to physical disks and then another set of physical disks are added, then the new physical disks would be 'imported' (overwriting the configuration database) rather than 'adopted' since the RAID controller module is using the configuration database of the existing physical disks.
For Scenario 1, you can fix this problem in two ways:
You can enable the Mixed Physical Disk Types feature key if it is supported by this storage array
You can remove the physical disks you recently inserted into the storage array, so that there is only one type of physical disk in the storage array
For Scenario 2, you can fix this problem in two ways:
You can disable the Mixed Physical Disk Types feature once there is only one physical disk type connected to the RAID controller modules
You can enable the Mixed Physical Disk Types feature key if it is supported by this storage array
While this feature is in an Out of Compliance state, you will NOT be able to:
Create new configuration objects (automatically or manually) - such as virtual disks, snapshots, replication relationships, virtual disk copy pairs, and storage partitions
Assign hot spares
Change the segment size of a virtual disk
Change the RAID level of a disk group
Expand the capacity of a disk pool, disk group or virtual disk
If... | Then... |
This problem occurred due to Scenario 1 | Go to ' Procedure for Scenario 1.' |
This problem occurred due to Scenario 2 | Go to ' Procedure for Scenario 2.' |
Procedure for Scenario 1
1 |
| ||||||||||||||||||
2 | Select the Storage Array > Premium Features... menu option in the Array Management Window.
| ||||||||||||||||||
3 | Click the Use Key File... button to use the feature key file and enable the premium feature, and then go to step 6. | ||||||||||||||||||
4 |
| ||||||||||||||||||
5 | Remove the physical disks or disconnect the expansion enclosures that you recently inserted that contain the different type of physical disks. | ||||||||||||||||||
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. |
Procedure for Scenario 2
1 |
| ||||||||||||||||||
2 | Select the Storage Array > Premium Features... menu option in the Array Management Window.
| ||||||||||||||||||
3 | Click the Use Key File... button to use the feature key file and enable the premium feature, and then go to step 8. | ||||||||||||||||||
4 |
| ||||||||||||||||||
5 |
| ||||||||||||||||||
6 | Remove the physical disks or disconnect the expansion enclosures that you recently inserted that contain the different type of physical disks. | ||||||||||||||||||
7 | Disable the Mixed Physical Disk Types feature.
| ||||||||||||||||||
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. |
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.ABBXMLEvent94" 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>94</EventNumber>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent94.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>