DS4700 Logical Drive Not On Preferred Path What Caused the Problem?

DetailsStorage Subsystem: Unnamed
Preferred owner: Controller in slot A
Current owner: Controller in slot B
Affected array: 1
Logical Drive: ora_01, heart_disk

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 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 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 Subsystems 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

1	If... Then... The controller was manually placed Offline Place the controller back Online by highlighting the controller in the Physical View of the Subsystem Management Window and selecting Advanced >> Recovery >> Place Controller >> Online. Go to Step 6. The controller was NOT manually placed Offline Go to Step 2.
2	Check the following components on both ends of the connection for loose connections or visible damage: External cablesHubs and switches If... Then... The connection components are OK Go to Step 3. There is a problem with the connection Fix the connection problem. Then, go to Step 6.
3	Use the information in the following table to determine the action to take. If... Then... The host connected to this storage subsystem is NOT connected to any other storage subsystems Verify that its host adapter is operational. If the host adapter is operational, the controller in the storage subsystem is probably defective. Go to Step 4.If the host adapter is defective, correct the problem, then go to Step 6. The host connected to this storage subsystem is connected to other storage subsystems Check the Enterprise Management Window for storage subsystems showing a Needs Attention status. If one or more storage subsystems connected to this host/host adapter does not have a Needs Attention status, then the controller in the storage subsystem is probably defective. Go to Step 4.If every storage subsystem connected to this host/host adapter has a Needs Attention status, then the associated host adapter is probably defective. Fix the host adapter problem, then go to Step 6.
4	Place the affected controller offline using the following steps. The affected controller is listed in the Details area. a Select the controller in the Subsystem Management Window. b Select Advanced >> Recovery >> Place Controller >> Offline. c Complete the instructions in the dialog, then select Yes.
5	Read all of the following steps before taking any action. a Click the Recheck button to rerun the Recovery Guru. b Select the Offline Controller problem that is being reported in the Summary area. c Complete the Recovery Steps in the Offline Controller to replace the controller.
6	Select 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.

附件：

20100806 eg ds4700.log (739 Bytes)