Home
  •  

Monitor REC_FOREIGN_DRIVE_REFERS_TO_NATIVE_DRIVE (213)

NetAppESeries.FailureID_0213_Monitor (UnitMonitor)

The volume
group information on an incoming foreign drive refers to a native
drive in the storage array as being a member of the group.

Knowledge Base article:

Foreign Drive Refers to Native Drive

What Caused the Problem?

A foreign volume group considers a native drive to be a member of the foreign volume group. 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

Recovery Steps

If...

Then...

You want to retain the volume group data for the drive listed in the Details area

Important

:

  • You must have an alternate storage array that is running the same revision of firmware or later than this storage array to proceed with this option.  The alternate storage array can be the original source storage array of the volume group or any other storage array that meets the firmware requirements.

  • You should save and print these recovery steps because some of the steps involve actions that you will take on the alternate storage array.

If you have an appropriate alternate storage array, go to the

Repair the Volume Group

section, below.

You do NOT want to retain the volume group data for the drive listed in the Details area

Important

: This option will erase all data contained on the drives.

If you are sure you want to erase all data on these drives, go to the Initialize the Drives section, below.

Repair the Volume Group

1

Refer to the Details area to find which drive slot is reporting the problem.  In addition, refer to the Summary area to see if there are other drives that are reporting this same problem.

2

Remove all of the drives from this storage array that are reporting this problem.

3

Insert the drives into the alternate storage array.

4

Complete the following steps using the Array Management Window (AMW) on the ALTERNATE storage array:

a

When all of the drives are spun up and recognized, a Contingent volume group should appear on the

Storage and Copy Services

tab in the AMW. You may see more than one Contingent volume groups if the drives you just inserted were members of different volume groups.

Select the Contingent volume group, and then select the Storage > Volume Group > Advanced > Import menu option.

b

Follow the instructions in the Import Volume Group dialog to properly import the volume group into the storage array.

Note: You will need to use the FORCE option since this volume group is missing a drive.

c

After the storage array completes the import process, the volume group transitions to a Partially Complete Volume Group state since it is missing a drive.

Select the Monitor > Health > View Health (Recovery Guru) menu option, and then select the "Partially Complete Volume Group" problem in the Summary area.  Complete the recovery steps for this problem to transition the volume group to an Optimal state.

Note: Choose the option in the recovery steps that explains how to replace the missing drive using the Replace Drives dialog.

e

Select the volume group on the

Storage and Copy Services

tab in the AMW, and then select the

Storage > Volume Group > Advanced > Export

menu option.

f

Follow the instructions in the Export Volume Group dialog to properly export the volume group from the storage array.

5

If applicable, repeat step 4 for each additional volume group that appeared as a result of inserting the drives in step 3.

6

Remove the drives from the Exported Volume Group(s), and insert them back into this storage array.

7

Import any new volume groups that appear on the

Storage and Copy Services

tab by using the

Storage > Volume Group > Advanced > Import

menu option.

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.

Initialize the Drives

1

Refer to the Details area to find which drive slot is reporting the problem.  In addition, refer to the Summary area to see if there are other drives that are reporting this same problem.

2

Highlight the affected drive on the

Hardware

tab in the Array Management Window (AMW), then select the

Hardware > Drive > Advanced > Initialize

menu option.

3

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

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

4

Repeat steps 1 through 3 for each additional drive that is reporting this problem in the Summary area.  When you have initialized all of the drives, go to step 5.

5

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:

TargetNetAppESeries.StorageArray
Parent MonitorNetAppESeries.StorageArrayAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeNetAppESeries.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_FOREIGN_DRIVE_REFERS_TO_NATIVE_DRIVE
The volume
group information on an incoming foreign drive refers to a native
drive in the storage array as being a member of the group. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="NetAppESeries.FailureID_0213_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_REFERS_TO_NATIVE_DRIVE_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.StateIdCD7ED21F35876629EF9434A774EF1E1" MonitorTypeStateID="NoIssue" HealthState="Success"/>

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

  </OperationalStates>

  <Configuration>

    <FailureID>213</FailureID>

    <IntervalSeconds>59</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>