Configuration Database Adoption Failed - Multiple Configuration Databases Detected

What Caused the Problem?

The storage array has failed to adopt the configuration database of one or more recently inserted physical disks because there are multiple configuration databases present among the physical disks inserted. In other words, the physical disks that were inserted into this storage array previously resided in multiple alternate storage arrays. This (the destination) storage array does not select a configuration database to adopt when there are multiple configuration databases present.

Due to the nature of the failure the Recovery Guru Details area does not provide specific information about the problem or the physical disks causing the problem.

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 typically results when you 1) insert more than one physical disk to or connect multiple expansion enclosures into a storage array that did not previously contain any physical disks, and 2) the RAID controller modules failed to adopt the configuration database because the physical disks came from multiple alternate storage arrays. As a result of this failure, the physical disks are recognized only as unassigned physical disks and are locked out of usage by this storage array in order to protect any data on the physical disks.
Every physical disk in a storage array holds a copy of the configuration database, which contains information about the entire storage array, not just what applies to the individual physical disk.
The RAID controller modules 'adopt' the configuration database from a set of physical disks ONLY when there were no physical disks previously attached to the RAID controller modules.
You must choose which configuration database for the RAID controller modules to adopt using the Recovery Steps, below.

Recovery Steps

If...

Then...

You know which physical disks or expansion enclosures came from each alternate storage array

a	Power-off both RAID controller modules.
b	Remove the physical disks or expansion enclosures that contain the configuration database that you DO NOT want the storage array to adopt.
c	Power-on the RAID controller modules and wait for the physical disks and logical entities to appear in the storage management software. Note: The RAID controller modules will adopt the configuration database from the set of physical disks making the physical disks 'native' to this storage array.
d	Insert the physical disks or expansion enclosures that contain the other configuration database. Note: The physical disks will be considered 'foreign' to the storage array and the disk groups must be imported into the storage array. Refer to the online help if you require assistance with importing disk groups into a storage array.
e	Go to step 9.

You DO NOT know which physical disks or expansion enclosures came from each alternate storage array

Go to step 2.

Remove all of the physical disks that were recently inserted into this storage array.

Select ONE of the original storage arrays that will be used to help you determine which physical disks belong together.

Note: Even though the physical disks came from multiple alternate storage arrays previously, you will insert ALL of the physical disks into only ONE of the original storage arrays. The storage array will recognize the physical disks that were previously attached to it as 'native' physical disks, and the rest will be considered 'foreign' physical disks, but you will still be able to get enough information about the physical disks to see which physical disks contain the same configuration database.

If...

Then...

The alternate storage array that you selected still contains physical disks

Insert all of the physical disks or connect all of the expansion enclosures to the RAID controller module.

The alternate storage array that you selected DOES NOT contain any physical disks

a	Power-off both RAID controller modules.
b	Insert all of the physical disks or connect all of the expansion enclosures to the RAID controller module.
c	Power-on the RAID controller modules and wait for the physical disks and logical entities to appear in the storage management software.
d	Go to step 5.

Using the storage management software for the alternate storage array, refer to the Physical Disks tab of the Storage Array Profile.

a	Determine which physical disks belong to the same disk groups. Physical Disks that belong to the same disk group (regardless of native or foreign status) will have a common disk group WWN and/or label.
b	Decide which set of physical disks (that are a part of a common disk group) that you want to insert to this (the destination) storage array in order to have the RAID controller modules adopt the configuration database.
c	Go to step 6.

Power down the RAID controller modules to this (the destination) storage array, and ensure that there are no additional foreign physical disks attached to them.

Re-insert the set of physical disks into this (the destination) storage array, and then power-on the RAID controller modules.

Note: The RAID controller modules will adopt the configuration database contained on the physical disks.

Insert the remaining physical disks into this (the destination) storage array.

Note: The physical disks will be considered 'foreign' to the storage array and the disk groups must be imported into the storage array. Refer to the online help if you require assistance with importing disk groups into a storage array.

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.