Monitor REC_MISMATCHED_DRIVE_TYPE (78)

Mixed Drive Types - Out of Compliance

What Caused the Problem?

The Mixed Drive 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 drive types (such as Serial ATA (SATA) and Fibre Channel) but the Mixed Drive 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 drive types, however, you connected drives to one or more controllers where 1) the controllers were NOT previously attached to any drives, and 2) the drives were already previously configured while attached to other controllers where the Mixed Drive 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 Drive Types feature while mixed drive types are still present

  • Enabled or disabled a feature pack resulting in the storage array not supporting Mixed Drive Types.

  • Imported drives of a different technology from those already residing in this storage array (for example, you add SATA drives to a storage array that previously contained only Fibre Channel drives) while the Mixed Drive Types feature was disabled

• Scenario 2 happens because the controllers were not previously attached to drives, so the controllers 'adopt' the configuration database of the first drive they encounter. When drives are adopted by the controllers, the configuration database contained on the drives (which includes all of the information about the previous storage array, including the enabled/disabled information of features) is used by the controllers. Therefore, the information in the configuration database shows that the Mixed Drive Types feature is enabled, but the feature is either disabled on this storage array or not supported by the controllers. If the controllers had been previously attached to drives and then another set of drives are added, then the new drives would be 'imported' (overwriting the configuration database) rather than 'adopted' since the controller is using the configuration database of the existing drives.

• For Scenario 1, you can fix this problem in two ways:

  • You can enable the Mixed Drive Types feature key if it is supported by this storage array

  • You can remove the drives you recently inserted into the storage array, so that there is only one type of drive in the storage array

• For Scenario 2, you can fix this problem in two ways:

  • You can disable the Mixed Drive Types feature once there is only one drive type connected to the controllers

  • You can enable the Mixed Drive 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 volumes, snapshots, mirror relationships, volume copy pairs, and storage partitions

  • Assign hot spares

  • Change the segment size of a volume

  • Change the RAID level of a volume group

  • Expand the capacity of a disk pool, volume group or volume

Recovery Steps

Procedure for Scenario 1

Procedure for Scenario 2