A drive has been bypassed
and the cause is unknown.
What Caused the Problem?
A drive or drive port has been bypassed. This problem can occur for the following reasons:
The ESM is defective
The drive is defective
The drive is not appropriate for the drive tray
The drive is not the correct technology type
The drive is not able to operate at the drive channel link speed
An interposer is defective
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 charges 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
When a drive is bypassed by only one ESM, the ESM is defective. When a drive is bypassed by both ESMs, the drive is defective.
No data has been lost.
When only one drive port is bypassed:
Access to only one drive port is lost.
The drive has an Optimal status until both drive ports report the drive as bypassed.
Loss of path redundancy is indicated. The drive Loss of Path Redundancy failure will also appear in the Recovery Guru Summary area.
When both drive ports are bypassed, the drive has a Bypassed status.
If a replacement drive is bypassed again soon after it was installed, the fault might be with the interposer, rather than the drive. In this case, perform the following steps:
Perform an ESM state capture from the command line interface.
Contact your Technical Support Representative for assistance.
When replacing a drive, verify that the replacement drive is the same as the original model or is a compatible model.
The new drive can operate at the same data rate as the drive it is replacing.
The new drive must have a capacity equal to, or greater than, the bypassed drive.
Service Action Allowed Important Information:
The
Service action (removal) allowed
field in the Details area indicates whether or not you can safely remove the component. If the SAA field is NO (
), then the affected component must remain in place until you service another component first.
The
Service action LED on Component
field in the Details area indicates whether or not a physical SAA LED is present on the hardware component. This field does NOT indicate whether the LED is ON or OFF (that indication is provided by the Service action (removal) allowed field).
If a component does not have an SAA LED, then it is OK to remove the component when its fault LED is lit and the
Service action (removal) allowed
field = YES (
) in the Details area.
The
Service action (removal) allowed
field shown in the Details area and the physical SAA LED on the hardware component (if supported) MUST match before you remove the affected component. In rare cases (such as multiple problems), the status of the LED and the SAA field may not match. If there is a mismatch, then you should NOT remove the component until these indications match.
Recovery Steps
Identifying the Bypassed Drive
1 | In the Recovery Guru Details area, identify the bypassed drive and the component that is bypassing the drive.
| ||||||||||||||||||||||
2 |
| ||||||||||||||||||||||
3 | Determine whether the bypassed drive is appropriate for the drive tray. An appropriate replacement drive has the following characteristics:
| ||||||||||||||||||||||
4 | Perform the following steps to reinsert the drive:
| ||||||||||||||||||||||
5 | 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. |
Replacing the Bypassed Drive
Note: You can replace the bypassed drive while the storage array is performing I/O operations.
1 | Obtain a replacement drive that is appropriate for the drive tray. An appropriate replacement drive has the following characteristics:
|
2 | Remove the bypassed drive from the drive tray. |
3 | Wait at least 30 seconds. |
4 | Insert the replacement drive. Its fault indicator light may be lit for a short time (one minute or less). |
5 | 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. |
Target | NetAppESeries.StorageArray | ||
Parent Monitor | NetAppESeries.StorageArrayAvailability | ||
Category | Custom | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | NetAppESeries.FailureUnitMonitorType | ||
Remotable | True | ||
Accessibility | Internal | ||
Alert Message |
| ||
RunAs | Default | ||
Comment | Machine generated entity |
<UnitMonitor ID="NetAppESeries.FailureID_0064_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppESeries.StorageArray" ParentMonitorID="NetAppESeries.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppESeries.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="NetAppESeries.REC_DRIVE_BYPASSED_CAUSE_UNKNOWN_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Property[@Name='FailureDescription']$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="NetAppESeries.StateIdA83A56787B25F393EAFB3C0B4A928236" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateIdA68710EEE5C9135756232F3B681EEC5F" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>64</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>