Security Physical Disk Needed
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 failure occurred in a physical disk security feature and operation of a storage array. This problem can occur for the following reasons:
Scenario 1 - A Self-Encrypting Disk (SED) physical disk that is a part of a security-enabled disk group was removed from a source storage array and inserted into the target storage array. The SED physical disk is locked to protect the physical disk data from unauthorized access.
Scenario 2 - An SED physical disk that is a part of a security-enabled disk group was removed from the source storage array and inserted into the target storage array. Although Physical Disk Security was enabled, no security key was created for the target storage array.
Scenario 3 - The only RAID controller module in a one-RAID controller module storage array or both RAID controller modules in a two-RAID controller module storage array were replaced. When the new RAID controller modules were powered on, all physical disks in the storage array were SED physical disks that belong to a security-enabled disk pool or disk group; therefore, all physical disks in the storage array are locked to protect the physical disk data from unauthorized access.
Scenario 4 - The only RAID controller module in a one-RAID controller module storage array or both RAID controller modules in a two-RAID controller module storage array were replaced. When the new RAID controller modules were powered on, at least one physical disk was not a member of a security enabled disk pool or disk group; therefore, the RAID controller modules adopted the database of the non-security enabled physical disk. The non-security enabled physical disk could be either an SED or a non-SED physical disk type. The SED physical disks that belong to a security-enabled disk pool or disk group are locked to protect the physical disk data from unauthorized access.
Scenario 5 - The storage array expected a security key to be returned to validate an operation, but the Enterprise Security Physical Disk Manager did not return the security key. Either the Enterprise Security Physical Disk Manager did not have a security key, or the request timed out.
The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
All Scenarios
All locked physical disks that have the same security key identifier will be unlocked at the same time after the unlock procedure is complete.
The storage array will remain in a Needs Attention state until the problem is resolved.
Alerts will be sent if they have been configured.
Scenario 1
After the security key is imported, the security information from the RAID controller modules replaces the security information for the SED physical disk. The security information consists of the security key, the security key identifier, and the pass phrase. You might be able to import the disk group after the unlock procedure is complete.
Scenario 2
You might be able to import the disk group after the unlock procedure is complete.
Scenario 3
After the security key is imported, the security information of the SED physical disk is applied to the RAID controller module in a one-RAID controller module storage array or to both RAID controller modules in a two-RAID controller module storage array. The security information consists of the security key, the security key identifier, and the pass phrase.
Scenario 4
After a new security key is created and the original security key is imported, the security information from the RAID controller modules replaces the security information for the SED physical disk. The security information consists of the security key, the security key identifier, and the pass phrase.
If... | Then... |
The problem occurred due to scenario 1, 3 or 5 | Go to ' Procedure for Scenario 1, 3 and 5.' |
The problem occurred due to scenario 2 or 4 | Go to 'Procedure for Scenario 2 and 4' |
Procedure for Scenario 1, 3 and 5
To fix the problem in scenarios 1, 3, and 5, import the security key file that matches the security key identifier.
1 | Review the Recovery Guru Details area to identify the security key identifier that is missing a matching security key. |
2 | On the menu bar in the Array Management Window, select the Storage Array > Security > Physical Disk Security > Import Key... menu option. |
3 | Complete the instructions in the dialog to import the security key file. NOTE: Be sure to choose the security key file that matches the security key identifier. You were prompted to record this information when the security key file was created, changed, or saved. |
4 | If the Recovery Guru Details area shows that additional security key files are required, perform steps 1 through 3 until all security key files are imported. |
5 | Click Recheck 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 and 4
To fix the problem in Scenario 2, create the security key for the target storage array, and then import the security key file that matches the security key identifier associated with the physical disks shown in the Recovery Guru Details Area.
1 | On the menu bar in the Array Management Window (AMW), select the Storage Array > Security > Physical Disk Security > Create Key... menu option. |
2 | Complete the instructions in the dialog to create the security key and to save it to a file. |
3 | After the physical disk security key has been created, review the Recovery Guru Details area to identify the security key identifier that is missing a matching security key. |
4 | On the menu bar in the AMW, select the Storage Array > Security > Physical Disk Security > Import Key... menu option. |
5 | Complete the instructions in the dialog to import the security key file. NOTE: Be sure to choose the security key file that matches the security key identifier. You were prompted to record this information when the security key file was created, changed, or saved. |
6 | If the Recovery Guru Details area shows that additional security key files are required, perform steps 1 through 5 until all security key files are imported. |
7 | Click Recheck 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.ABBXMLEvent370" 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>370</EventNumber>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent370.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>