DOC

fastT

By Edna Morris,2014-11-13 13:30
6 views 0
fastT ...

    更多相关资料;

    http:///mydoc-4354614-1.html&folderId=62450

    Drive - Loss of Path Redundancy What Caused the Problem?

    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.

    Important Notes

    ; Correct this failure as soon as possible. The drive is still

    operational, but a level of path redundancy has been lost. If the

    drive's other port or any other component fails on the working

    channel, the drive will be failed. The Recovery Guru Details area

    reports the affected enclosure, drive, and the working channel over

    which it can communicate with the drive.

    ; The fault indicator light on the affected drive will be off because

    the drive has not failed.

    Recovery Steps

    1 Fix any other problems reported by the Recovery Guru before attempting to fix this problem.

    2 If... Then...

    The affected enclosure Go to Step 7.

    listed in the Recovery Guru

    Details area contains both

    controllers and drives

The affected enclosure Go to step 3.

    listed in the Recovery Guru

    Details area contains only

    drives

    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.

    Caution

    Do not disconnect any cables on the working channel. Doing so will cause data loss!

    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:

    a Label the interface transceivers (GBICs or SFPs). The labels will

    help you correctly reconnect the cables to the new ESM canister.

    While the cables are still connected, remove the interface

    transceivers from the ESM canister you are replacing.

    b Remove the ESM canister.

    c Set all switches on the new ESM canister to the same values as the

    old ESM canister.

    d Insert the new ESM canister into the drive enclosure.

    e Using the labels created in Step a, reconnect the cables to the

    replaced canister. Wait 40 seconds, then go to Step 6.

    6 Select Recheck to rerun the Recovery Guru to ensure that the problem has been fixed.

    If... Then...

    The problem has been fixed You are finished with this procedure. Do

    NOT go to step 7!

    The problem has not been Go to step 7.

    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.

    If... Then...

    The array is RAID 0 Go to "Recovery Steps for Replacing a Drive

    in a RAID 0 Array."

    The array is RAID 1, 3, or Go to "Recovery Steps for Replacing a Drive 5 in a RAID 1, 3, or 5 Array."

    Recovery Steps for Replacing a Drive in a RAID 0 Array

    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.

    If... Then...

    The problem has been fixed You are finished with this procedure. Do

    NOT go to step 4!

    The problem has not been Go to step 4.

    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.

    Caution

    Transitioning logical drives to failed will cause the loss of all data

    on the logical drives. Make sure that you back up all data on the 6 affected logical drives before starting this step.

    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.

    ; The logical drives in the array are initialized, one at a time.

    ; To monitor initialization progress for a logical drive,

    highlight the logical drive in the Logical View of the

    Subsystem Management Window and select Logical

    Drive>>Properties. Note that when the initialization is

    completed, the progress bar is no longer displayed.

    ; When initialization is completed, all logical drives in the

    array are Optimal .

    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.

    Recovery Steps for Replacing a Drive in a RAID 1, 3, or 5 Array

    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.

    If... Then...

    The problem has been fixed You are finished with this procedure. Do

    NOT go to step 4!

    The problem has not been Go to step 4.

    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.

Report this document

For any questions or suggestions please email
cust-service@docsford.com