Foreign Drive Refers to Native Drive

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:
  • Each foreign drive in the foreign volume group will report this problem in the Summary area. A foreign volume group is a volume group that has been exported from this storage array or not yet completely imported into the storage array.

  • This problem usually occurs because you inserted one or more drives from the same volume group from a different storage array into this storage array, and that volume group previously contained a drive that is already installed in this storage array.

  • The foreign drive still has logical references to the native drive even though the native drive does not have logical references to the foreign drive (for example, the drive was replaced at some point).

  • The native drive is an Unassigned drive (not part of a native volume group), unless it has been Assigned since this problem was reported.

  • To resolve this problem, you can either initialize the foreign drive in this storage array (erasing all data) or you can insert it into a different storage array to fix the problem (retaining the data). The recovery action that you select below should be the same for every one of the drives that are reporting this problem in the Summary area. The recovery action needs to be the same because the separate problems could involve drives from the same foreign volume group.

  • Do not click the Recheck button until instructed to do so. Otherwise, additional problems might be reported in the Summary area.

  • You can remove the drive while the storage array is receiving I/O.

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:

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

    2. 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.
    3. 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.
    4. 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.

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