Configuration Database Adoption Failed - Multiple Configuration Databases Detected

What Caused the Problem?

The storage subsystem has failed to adopt the configuration database of one or more recently inserted drives because there are multiple configuration databases present among the drives inserted.  In other words, the drives that were inserted into this storage subsystem previously resided in multiple alternate storage subsystems.  This (the destination) storage subsystem 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 drives 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

Recovery Steps

1
If... Then...
You know which drives or drive enclosures came from each alternate storage subsystem
a Power-off both controllers.
b Remove the drives or drive enclosures that contain the configuration database that you DO NOT want the storage subsystem to adopt.
c Power-on the controllers and wait for the drives and logical entities to appear in the storage management software.

Note: The controllers will adopt the configuration database from the set of drives making the drives 'native' to this storage subsystem.

d Insert the drives or drive enclosures that contain the other configuration database.

Note: The drives will be considered 'foreign' to the storage subsystem and the arrays must be imported into the storage subsystem.  Refer to the online help if you require assistance with importing arrays into a storage subsystem.

e Go to step 9.
You DO NOT know which drives or drive enclosures came from each alternate storage subsystem Go to step 2.
2 Remove all of the drives that were recently inserted into this storage subsystem.
3 Select ONE of the original storage subsystems that will be used to help you determine which drives belong together.

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

4
If... Then...
The alternate storage subsystem that you selected still contains drives Insert all of the drives or connect all of the drive enclosures to the controller.
The alternate storage subsystem that you selected DOES NOT contain any drives
a Power-off both controllers.
b Insert all of the drives or connect all of the drive enclosures to the controller.
c Power-on the controllers and wait for the drives and logical entities to appear in the storage management software.
d Go to step 5.
5 Using the storage management software for the alternate storage subsystem, refer to the Drives tab of the Storage Subsystem Profile.
a Determine which drives belong to the same arrays. Drives that belong to the same array (regardless of native or foreign status) will have a common array WWN and/or label.
b Decide which set of drives (that are a part of a common array) that you want to insert to this (the destination) storage subsystem in order to have the controllers adopt the configuration database.
c Go to step 6.
6 Power down the controllers to this (the destination) storage subsystem, and ensure that there are no additional foreign drives attached to them.
7 Re-insert the set of drives into this (the destination) storage subsystem, and then power-on the controllers.

Note: The controllers will adopt the configuration database contained on the drives.

8 Insert the remaining drives into this (the destination) storage subsystem.

Note: The drives will be considered 'foreign' to the storage subsystem and the arrays must be imported into the storage subsystem.  Refer to the online help if you require assistance with importing arrays into a storage subsystem.

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