Disk Group Cloned

What Caused the Problem?

The storage array is reporting that the same disk group is appearing more than once in the configuration. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Caution: Electronic 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 usually results in two situations:
- Scenario 1 - You removed a disk group from the storage array without using the proper Export procedure. This caused the disk group to be in a Missing state. Then you inserted the physical disks of the disk group in another storage array and later returned the physical disks back into this storage array. The disk group is now different because the configuration data was altered by the other storage array. However, this storage array considers the disk group a duplicate of the one that is missing.
- Scenario 2 - You connected a expansion enclosure containing foreign physical disks to a RAID controller module enclosure that previously did not have any expansion enclosures connected to it. In addition, this action was done while the RAID controller modules were operational (powered up). The problem occurred because a RAID controller module transitioned the first physical disk to be a native physical disk, rebooted, then recognized the remaining physical disks as foreign. The native physical disk and the foreign physical disks contain the same disk group information.
The resolution to this problem will differ based on what caused the problem.
You can remove the physical disks while the storage array is receiving I/O.

Recovery Steps

If...	Then...
This problem was a result of Scenario 1 (refer to the Important Notes, above)	Go to Recovery Steps for Scenario 1.
This problem was a result of Scenario 2 (refer to the Important Notes, above)	Go to Recovery Steps for Scenario 2.

Recovery Steps for Scenario 1

1	Refer to the Details area to find which physical disks are associated with the affected disk group.
2	Remove each physical disk listed in the Details area until all of them have been removed from the storage array.
3	Highlight the Missing Virtual Disk in the Logical View of the Array Management Window (AMW) that corresponds to the affected virtual disk in the Details area.
4	Select the Disk Group >> Delete menu option. Note: By completing this step, you are removing the storage array's reference to the disk group. When you re-insert the physical disks in the next steps, the storage array will view the disk group as a new foreign disk group.
5	Reinsert the physical disks that you removed in step 2.
6	As you insert the physical disks, a Contingent disk group should appear in the Logical View. When ALL of the physical disks are spun up and recognized, the Contingent disk group should transition to an Exported virtual disk. Select the Exported disk group in the Logical View, and then select the Advanced >> Maintenance >> Import Disk Group menu option.
7	Follow the instructions in the Import Disk Group dialog to properly import the disk group into the storage array.
8	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.

Recovery Steps for Scenario 2

If...	Then...
You are certain that the foreign physical disks listed in the details area should be in the same disk group as the native physical disks	Go to step 2.
You are NOT certain that the foreign physical disks listed in the details area should be in the same disk group as the native physical disks	Contact your technical support representative to assist you with fixing this problem. Do not continue with the remaining Recovery Steps.

Mark the physical disks as Native by completing the following steps:

Open a Command Prompt, and type the following command:

SMcli -n <storageArray_name>;

where storageArray_name is the name of the storage array listed in the Details area.

Note: If you receive an error from this command, change your working directory to the directory that contains the SMcli executable.

Execute the following command in order to mark the physical disks as native to this storage array:

Important: The following command should not be used in any other circumstance other than to correct this specific problem. If used in the wrong situation, this command could result in data loss.

set allPhysical Disks toNative;

c When the operation completes, exit the Command Prompt, and go to step 3.

3 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.