Monitor REC_NON_PREFERRED_PATH (10)

Logical Drive Not On Preferred Path

What Caused the Problem?

There is a problem accessing the controller listed in the Recovery Guru Details area. Any logical drives that have this controller assigned as their preferred path will be moved to the non-preferred path (alternate controller). This procedure will help you pinpoint the problem along the data path. Because the logical drives will be moved to the alternate controller, they should still be accessible. Therefore, no action is required on the individual logical drives.

Possible causes include:

• The controller failed a manually initiated diagnostic test and was placed Offline.

• The controller was manually placed Offline using the

  Advanced >> Recovery >> Place Controller >> Offline

  menu option.

• There are disconnected or faulty cables.

• A Hub or Fabric switch is not functioning properly.

• A host adapter has failed.

• The storage subsystem contains a defective RAID controller.

The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

 Caution: Possible Loss of Data Access. Do not replace the controller until you are instructed to do so. This procedure will instruct you to check the components along the connection, check the host adapters, and eventually instruct you to replace the controller, if necessary.

Important Notes

• When Auto Logical Drive Transfer (ADT) is enabled, it can take several minutes for the host-based, multi-path failover driver to recognize a restored or modified preferred path (use the Storage Subsystem Profile to determine whether you have ADT enabled on a mapped host; see the Recovery Steps, below). A Logical Drive Not On Preferred Path error will be reported during this time. If you have recently modified the preferred path using the

  Array >> Change >> Ownership/Preferred Path

  or

  Logical Drive >> Change >> Ownership/Preferred Path

  menu options or performed a recovery procedure that has restored a preferred path, wait at least 10 minutes and run the Recovery Guru again using the Recheck button. If this error is reported again, perform the recovery procedures listed below.

• Not all models of storage subsystems contain batteries. If your storage subsystem does not contain batteries, you can ignore any references to them in the following steps. To determine if your storage subsystem contains batteries, use the

  Storage Subsystem >> View >> Profile

  option and select the Enclosures tab. Storage arrays without batteries will not have those components listed.

• If the controllers for this storage subsystem are located in an enclosure containing both controllers and drives, you may have to insert the battery from the old controller canister into the new replacement controller canister. Consult the following steps and your hardware documentation for details.

Recovery Steps