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
Electrostatic discharge can damage sensitive components. Use a grounding wrist strap or other anti-static precautions before removing or handling components.
1 |
Fix any other problems reported by the Recovery Guru before attempting to fix this problem. |
||||||||||
2 |
|
||||||||||
3 |
To determine the non-working channel, start at the drive minihub 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 |
Select Recheck to rerun the Recovery Guru to ensure that the problem has been fixed. |
||||||||||
|
|||||||||||
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 Components. 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.
Caution
Use the Recovery Guru to fix any other reported problems 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. Therefore, locate the affected drive, remove and re-insert it. |
||||||
3 |
Wait 40 seconds, and then select Recheck to rerun the Recovery Guru to ensure that the problem has been fixed. |
||||||
|
|||||||
4 |
Back up all data on the affected logical drives. (Step 6 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 |
Note: 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 6. Perform any necessary operations on the FlashCopy logical drives and then delete them. |
||||||
6 |
Highlight the affected drive in the Physical View of the Subsystem Management Window and select Drive>>Fail. The affected logical drives become Failed |
||||||
7 |
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. |
||||||
8 |
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 9. |
||||||
9 |
Highlight the array associated with the replaced drive in the Logical View of the Subsystem Management Window and select Array>>Initialize.
Important: Make sure you save this procedure by selecting Save As. Once you perform step 11 and fix the failure, you will not be able to access the information in steps 12 and 13 from Recovery Guru. |
||||||
10 |
If desired, create any FlashCopys that you deleted in Step 5. |
||||||
11 |
Select Recheck to rerun the Recovery Guru to ensure that the failure has been fixed. |
||||||
12 |
Add the affected logical drives back to the operating system. You may need to reboot the system to see the re-initialized logical drives. Note: Do not start I/O to these logical drives until you have restored data from backup. |
||||||
13 |
Restore the data for the affected logical drives from backup. |
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. Therefore, locate the affected drive, remove and re-insert it. |
||||||
3 |
Wait 40 seconds, and then select Recheck 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 Drive>>Fail. 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 |
Select Recheck to rerun the Recovery Guru to ensure that the failure has been fixed. |