经典LogicalDriveNotOnPreferredPath.docVIP

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 AdvancedRecoveryPlace ControllerOffline 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 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. ?CautionElectrostatic discharge can damage sensitive components. Use a grounding wrist strap or other anti-static precautions before removing or handling components. 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 Step 9 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 ArrayChangeOwnership/Preferred Path or Logical DriveChangeOwnership/Preferred Path menu options