A drive has failed.
What Caused the Problem?
A drive in the storage array has failed. 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
No data has been lost.
The failed drive can be an Assigned drive, an Unassigned drive, or a Standby hot spare drive.
One reason for the failure could be that the drive does not have the appropriate signature. Make sure that the affected drive is an authorized drive. Contact your Technical Support Representative if you have any questions.
When replacing a drive, make sure the replacement drive has a capacity equal to or greater than the failed drive you will remove.
You can replace the failed drive while the storage array is receiving I/O.
If the failed drive is a Standby hot spare, you must unassign it before removing it.
If your drive tray contains drawers, then in rare instances the failure could be in the ATA translator that is attached to the drawer component. If completing steps 1 through 5 does not resolve your problem, then contact your Technical Support Representative to resolve this problem.
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
1 | Check the Component requiring service field in the Details area to determine which drive has failed. | ||||||||||||||||
2 |
| ||||||||||||||||
3 | Remove the drive. Its fault indicator light should be lit. | ||||||||||||||||
4 | Wait 30 seconds, then insert a new drive. Its fault indicator light may be lit for a short time (one minute or less). | ||||||||||||||||
5 |
| ||||||||||||||||
6 | 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 | NetAppSANtricity.StorageArray | ||
Parent Monitor | NetAppSANtricity.StorageArrayAvailability | ||
Category | Custom | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | NetAppSANtricity.FailureUnitMonitorType | ||
Remotable | True | ||
Accessibility | Internal | ||
Alert Message |
| ||
RunAs | Default | ||
Comment | Machine generated entity |
<UnitMonitor ID="NetAppSANtricity.FailureID_0023_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppSANtricity.StorageArray" ParentMonitorID="NetAppSANtricity.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppSANtricity.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="NetAppSANtricity.REC_FAILED_DRIVE_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="NetAppSANtricity.StateId4DCEF312AAB6712D1901B432EE569CC0" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppSANtricity.StateId931BAB422A7ED642BE00416E8039B1F6" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>23</FailureID>
<IntervalSeconds>361</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>