Monitor REC_FOREIGN_DRIVE_INCONSISTENT (212)

NetAppESeries.FailureID_0212_Monitor (UnitMonitor)

The configuration
data stored on a foreign drive indicates that it is part of a volume
group in the same storage array; however, the drive's configuration
data is inconsistent with that of the volume group in one of the
following ways: (1) the volume group is in the complete state and
has no indication of drives missing, or (2) the volume group is
in the exported state, but the drive's configuration data is older
than that of the volume group's drives.

Knowledge Base article:

Foreign Drive Has Inconsistent Configuration

What Caused the Problem?

A foreign drive considers itself to be a member of a native volume group. However, the volume group is optimal, and not currently missing any drives. A foreign drive is a drive that has been exported from this storage array or not yet completely imported into the storage array. 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 from inserting a drive (from a different storage array into this storage array) that might have previously been a member of the native volume group. However, the foreign drive has been replaced with a different drive in this storage array at some point.
This problem does not affect the performance of the native volume group.
To resolve this problem, you will need to initialize the foreign drive or remove it from the storage array. Follow the recovery steps below to fix the problem.
You can remove the drive while the storage array is receiving I/O.

Recovery Steps

Refer to the Details area to find which drive slot is reporting the problem.

If...

Then...

You want to retain the data on the foreign drive

Remove the foreign drive from the system and return it to the storage array that from which it was removed.

Go to step 4.

You do NOT want to retain the data on the foreign drive (you want the drive to become an Unassigned drive in this storage array)

Go to step 2.

Highlight the foreign drive on the

Hardware

tab in the Array Management Window, then select the

Hardware > Drive > Advanced > Initialize

menu option.

Follow the instructions in the Initialize Drive dialog to initialize the drive.

When the initialization completes, the drive will be an Optimal, Unassigned drive.

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.

Element properties:

Target

NetAppESeries.StorageArray

Parent Monitor

NetAppESeries.StorageArrayAvailability

Category

Custom

Enabled

True

Alert Generate

True

Alert Severity

Error

Alert Priority

Normal

Alert Auto Resolve

True

Monitor Type

NetAppESeries.FailureUnitMonitorType

Remotable

True

Accessibility

Internal

Alert Message

Alert: REC_FOREIGN_DRIVE_INCONSISTENT

RunAs

Default

Comment

Machine generated entity

Source Code:

<UnitMonitor ID="NetAppESeries.FailureID_0212_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppESeries.StorageArray" ParentMonitorID="NetAppESeries.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppESeries.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="NetAppESeries.REC_FOREIGN_DRIVE_INCONSISTENT_AlertMessageResourceID">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/Property[@Name='FailureDescription']$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="NetAppESeries.StateIdF5616630F15759824B99B21B2BCEA6CC" MonitorTypeStateID="NoIssue" HealthState="Success"/>

    <OperationalState ID="NetAppESeries.StateId6994DCFC0CF0BB38C40C47AEC9B260DF" MonitorTypeStateID="IssueFound" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <FailureID>212</FailureID>

    <IntervalSeconds>59</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>