Monitor REC_DRIVE_BYPASSED_CAUSE_UNKNOWN (64)

NetAppESeries.FailureID_0064_Monitor (UnitMonitor)

A drive has been bypassed
and the cause is unknown.

Knowledge Base article:

Bypassed Drive

What Caused the Problem?

A drive or drive port has been bypassed. This problem can occur for the following reasons:

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

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.

If...

Then...

One ESM canister is bypassing the drive

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

If...

Then...

There IS an ESM Configuration Settings Version Mismatch

Follow the ESM Configuration Settings Version Mismatch recovery steps first, and then return to this recovery procedure.

There is NOT an ESM Configuration Settings Version Mismatch

The is probably a problem with the ESM that is bypassing the drive. Perform the following steps to collect the necessary support data:

a

Select the

Monitor > Health > Collect Support Data Manually

menu option in the Array Management Window.

b

Save the support data to a .zip file.

c

Contact your Technical Support Representative. Indicate that the reported problem was a bypassed drive for only one ESM.

d

Send the support data .zip file and the ESM state capture .zip file to the Technical Support Representative.

e

Wait for further instruction. Do not perform any other recovery actions until instructed to do so by your Technical Support Representative.

A controller or a drive component is bypassing the drive

OR

Two ESM canisters are bypassing the drive

Go to step 2.

2

If...

Then...

The bypassed drive recently replaced another drive, or was inserted into an empty drive slot

Go to step 3.

The bypassed dive did NOT recently replace another drive, or was NOT inserted into an empty drive slot

Go to

Replacing the Bypassed Drive

.

3

Determine whether the bypassed drive is appropriate for the drive tray. An appropriate replacement drive has the following characteristics:

  • It can operate at the same data rate as the drive it is replacing

  • It has a capacity equal to, or greater than, the bypassed drive

  • It is the correct technology type

  • It is capable of operating at the drive channel link speed

If...

Then...

The drive is appropriate

Go to step 4.

The drive is NOT appropriate

Go to

Replacing the Bypassed Drive

.

4

Perform the following steps to reinsert the drive:

a

Remove the bypassed drive from the drive tray.

b

Wait at least 30 seconds.

c

Reinsert the 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.

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:

  • It can operate at the same data rate as the drive it is replacing

  • It has a capacity equal to, or greater than, the bypassed drive

  • It is the correct technology type

  • It is capable of operating at the drive channel link speed

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.

Element properties:

TargetNetAppESeries.StorageArray
Parent MonitorNetAppESeries.StorageArrayAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeNetAppESeries.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_DRIVE_BYPASSED_CAUSE_UNKNOWN
A drive has been bypassed
and the cause is unknown. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<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>