Bypassed Drive

What Caused the Problem?

The ESM has reported that the drive has been bypassed to maintain the integrity of the fibre channel loop. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

 Caution: Possible loss of data accessibility. Do not remove a component when either (1) the Service action (removal) allowed (SAA) field in the Details area of this recovery procedure is NO (), or (2) the SAA LED on the affected component is OFF (note that some products do not have SAA LEDs). Removing a component while its SAA LED is OFF may result in temporary loss of access to your data. Refer to the following Important Notes for more detail.

Caution: Electrostatic discharge can damage sensitive components. Always use proper antistatic protection when handling components. Touching components without using a proper ground may damage the equipment.

Important Notes

Recovery Steps

1

Check the Details area to identify the bypassed drive and to determine what component is bypassing the reported drive.

2
If... Then...
A controller or drive component is bypassing the reported drive Go to step 6.
Two ESM canisters are bypassing the reported drive Go to step 6.
Only one ESM canister is bypassing the reported drive

Check the Summary area of Recovery Guru to see if there is also an ESM Configuration Settings Version Mismatch.

If... Then...
There is an ESM Configuration Settings Version Mismatch

Follow the Recovery Guru steps to resolve that problem first.

There is not an ESM Configuration Settings Version Mismatch There is likely a problem with the ESM that is bypassing the drive. Go to step 3 to collect all support data and then contact your technical support representative.
3 Select the Advanced >> Troubleshooting >> Support Data >> Collect menu option from the Subsystem Management Window (AMW), and take the appropriate steps to save the support data to a .zip file.
4 Save the ESM State Capture information. You will send this to your technical support representative in a later step.
a Open a Command Prompt, and type the following command:

SMcli -n <storageSubsystem_name>;

where storageSubsystem_name is the name of the storage subsystem listed in the Details area.

Note: If you receive an error from this command, change your working directory to the directory that contains the SMcli executable.

b Execute the following command in order to save the ESM State Capture information:

save storageSubsystem diagnosticData esm file=?fileToSave.zip?;

where fileToSave.zip is the full directory path and name of the file you want to save.

c When the operation completes, exit the Command Prompt, and go to step 5.
5 Contact your technical support representative and indicate that a "Bypassed Drive" problem is being reported by only one ESM. Send the files you saved in steps 3 and 4 to your representative and wait for further instruction.  Do not continue with the remaining Recovery Steps.
6 Remove the bypassed drive. If the bypassed drive was recently used to replace another drive in this same drive slot or was inserted into an empty drive slot, go to step 7. Otherwise, go to step 8.
7 Check to make sure that the bypassed drive is appropriate for the drive enclosure (see the Important Notes section). If the drive is NOT appropriate, go to step 8. Otherwise, go to step 9.
8 Obtain a replacement drive for the bypassed drive that is appropriate for the drive enclosure (see the Important Notes section). Wait 30 seconds and then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less). Go to step 10.
9 Wait 30 seconds and then re-insert the drive. Its fault indicator light may be lit for a short time (one minute or less). Go to step 10.
10 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.