Home
  •  

Monitor REC_FOREIGN_DRIVE_REFERS_TO_NATIVE_DRIVE (213)

IBMStorageSubsystem.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 array considers a native drive to be a member of the foreign array. Each foreign drive in the foreign array will report this problem in the Summary area. A foreign array is an array that has been exported from this storage subsystem or not yet completely imported into the storage subsystem. 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 array data for the drive listed in the Details area

Important Notes

:

  • You must have an alternate storage subsystem that is running the same revision of firmware or later than this storage subsystem to proceed with this option.  The alternate storage subsystem can be the original source storage subsystem of the array or any other storage subsystem 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 subsystem.

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

Repair the Array

section, below.

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

Important Note

: 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 Array

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 subsystem that are reporting this problem.

3

Insert the drives into the alternate storage subsystem.

4

Complete the following steps using the Subsystem Management Window on the ALTERNATE storage subsystem:

a

When all of the drives are spun up and recognized, a Contingent array should appear in the Logical view. You may see more than one Contingent arrays if the drives you just inserted were members of different arrays .

Select the Contingent array in the Logical View, and then select the Advanced >> Maintenance >> Import Array menu option.

b

Follow the instructions in the Import Array dialog to properly import the array into the storage subsystem.

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

c

After the storage subsystem completes the import process, the array transitions to a Partially Complete Array state since it is missing a drive.

Select the Storage Subsystem >> Recovery Guru menu option, and then select the "Partially Complete Array" problem in the Summary area.  Complete the Recovery Steps for this problem to transition the array 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 array in the Logical View, and then select the

Advanced >> Maintenance >> Export Array

menu option.

f

Follow the instructions in the Export Array dialog to properly export the array from the storage subsystem.

5

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

6

Remove the drives from the Exported Array(s), and insert them back into this storage subsystem.

7

Import any new arrays that appear in the Logical view by using the

Advanced >> Maintenance >> Import Array

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 in the Physical view of the Subsystem Management Window (AMW), then select the

Advanced >> Recovery >> Initialize >> Drive

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:

TargetIBMStorageSubsystem.StorageSubsystem
Parent MonitorIBMStorageSubsystem.StorageSubsystemAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeIBMStorageSubsystem.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="IBMStorageSubsystem.FailureID_0213_Monitor" Accessibility="Internal" Enabled="true" Target="IBMStorageSubsystem.StorageSubsystem" ParentMonitorID="IBMStorageSubsystem.StorageSubsystemAvailability" Remotable="true" Priority="Normal" TypeID="IBMStorageSubsystem.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="IBMStorageSubsystem.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="IBMStorageSubsystem.StateId81D1AFBEAF377CEDC02A34A4AA84CBC7" MonitorTypeStateID="NoIssue" HealthState="Success"/>

    <OperationalState ID="IBMStorageSubsystem.StateIdCB5E2886FF3C4121C51AB0DF56B018C0" MonitorTypeStateID="IssueFound" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <FailureID>213</FailureID>

    <IntervalSeconds>59</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>