A communication path with a drive has been lost. 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.
1 |
Fix any other problems reported by the Recovery Guru before attempting to fix this problem. |
||||||||||
2 |
|
||||||||||
To determine the non-working channel, start at the drive port on the controller enclosure corresponding to the working channel (refer to the labels on the back of the controller enclosure if needed). Trace the cable from the working channel to the ESM canister in the affected drive enclosure reported in the details area.
|
|||||||||||
4 |
Locate the other ESM canister in the affected drive enclosure (this is the canister on the non-working channel). |
||||||||||
5 |
Replace the ESM canister on the non-working channel using the following steps:
|
||||||||||
6 |
Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area.
|
||||||||||
7 |
You must replace the drive. Which procedure you use depends on the RAID level of the array associated with the affected drive. To determine the associated array, highlight the affected drive in the Physical View of the Subsystem Management Window and select View >> Associated Elements. Next highlight the associated array in the Logical View of the Subsystem Management Window.
|
Use the following procedure if the affected array is RAID 0.
Fix any other problems reported by the Recovery Guru before continuing with this procedure. Note that all logical drives in the Logical View of the Subsystem Management Window must be Optimal .
1 |
Stop all I/O to the affected logical drives. |
||||||||||||||||
2 |
Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it. Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO. |
||||||||||||||||
3 |
Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.
|
||||||||||||||||
4 |
Back up all data on the affected logical drives. (Step 7 will destroy all data on the affected logical drives.) Note: To the operating system (OS), a failed logical drive is the same as a failed non-RAID drive. Refer to the OS documentation for requirements concerning failed drives and apply them where necessary. |
||||||||||||||||
5 |
If any of the affected logical drives are also source or target logical drives in a copy operation that is either Pending or In Progress, you must stop the copy operation before continuing. Go to the Copy Manager by selecting Logical Drive >> Copy >> Copy Manager, then highlight each copy pair that contains an affected logical drive and select Copy >> Stop. |
||||||||||||||||
6 |
If you have flashcopy logical drives associated with the affected logical drives, these flashcopy logical drives will no longer be valid once you fail the drive in step 8. If necessary, perform any operations on the flashcopy logical drives and then delete them. |
||||||||||||||||
7 |
Highlight the affected drive in the Physical View of the Subsystem Management Window and select Advanced >> Recovery >> Fail Drive. The affected logical drives become Failed |
||||||||||||||||
8 |
Remove the failed drive (its fault indicator light should be on). Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive. |
||||||||||||||||
9 |
Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less). Note: Wait until the replaced drive is ready (its fault indicator light must be off) before attempting to initialize the logical drives in step 10. |
||||||||||||||||
10 |
Highlight the array associated with the replaced drive in the Logical View of the Subsystem Management Window and select Advanced >> Recovery >> Initialize >> Array.
Important: Make sure you save this procedure by selecting Save As. Once you fix the failure, you will not be able to access the information from Recovery Guru. |
||||||||||||||||
11 |
Click the Recheck button to rerun the Recovery Guru.
The failure should no longer appear in the Summary area.
|
Use the following procedure if the affected array is RAID 1, 3, or 5.
1 |
You should stop all I/O to all logical drives in the array associated with the affected drive to reduce the possibility of data loss. If another drive fails in this array while you are performing this procedure, you will lose data. |
||||||
2 |
Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it. Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO. |
||||||
3 |
Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.
|
||||||
4 |
Although not required, you should back up all data on all logical drives associated with the affected drive. |
||||||
5 |
Highlight the affected drive in the Physical View of the Subsystem Management Window and select Advanced >> Recovery >> Fail Drive. The associated logical drives become Degraded |
||||||
6 |
Remove the failed drive (its fault indicator light should be on). Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive. |
||||||
7 |
Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less). |
||||||
8 |
Click the Recheck button to rerun the Recovery Guru.
The failure should no longer appear in the Summary area.
|
Important: The controller replacement recovery steps should only be attempted after ALL other options have been exhausted.
Use the following procedure to replace a controller to resolve a loss of path redundancy condition.
If... | Then... |
Your storage subsystem has one controller | Go to "Replacing a Controller in a Single-Controller Storage Subsystem." |
Your storage subsystem has two controllers | Go to "Replacing a Controller in a Dual-Controller Storage Subsystem." |
1 |
Ensure that your replacement controller matches the controller in the storage subsystem. If you do not have a controller with the appropriate replacement part number, contact your technical support representative. |
||||||||||||||||||||||
2 |
Stop all I/O to this storage subsystem. |
||||||||||||||||||||||
3 |
Turn off power to the affected enclosure. |
||||||||||||||||||||||
4 |
Remove the affected controller. Refer to the Enterprise Management Window (EMW) to view which management method you are using to manage this storage subsystem.
|
||||||||||||||||||||||
5 |
|
||||||||||||||||||||||
6 |
|
||||||||||||||||||||||
7 |
If you have logical drives mapped to hosts that have Automatic Logical Drive Transfer (ADT) disabled, it may be necessary to redistribute the logical drives to their preferred controller. Use the following steps to determine the ADT status of the hosts connected to your storage subsystem:
|
||||||||||||||||||||||
8 |
Click the Recheck button 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. |
1 |
Determine which is the affected controller by locating the non-working channel. Refer to step 3 at the beginning of this recovery procedure for details on how to locate the non-working channel. |
||||||||
2 |
Place the affected controller offline.
|
||||||||
3 |
Read all of the following steps before taking any action.
|
||||||||
4 |
Click the Recheck button 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. |