Flash Cache is in non-optimal state due to missing or inaccessible drives.
What Caused the Problem?
An SSD cache on the storage array is non-optimal. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps
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
This problem occurs when one or more drives comprising the SSD cache have either failed or been removed from the storage array.
If the SSD cache is Degraded, it was not receiving I/O when the underlying drive problem occurred and it is still usable. However, if the underlying drive problem is not fixed when an I/O request to the SSD cache is attempted, it will transition to a Failed state. If the SSD cache is Failed, it is no longer usable and any SSD-cache enabled volume will no longer have the performance benefits of the SSD cache.
As soon as a failed drive is replaced or a missing drive in inserted back into the storage array, the SSD cache should automatically transition to a functional state.
For failed drives, make sure the replacement drives have a capacity equal to or greater than the failed drives you will remove. You can replace failed drives while the storage array is receiving I/O.
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 | Review the Details area to identify the reason for the non-optimal SSD cache.
| ||||||||||||||||||||||||
2 | 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 |
Home<UnitMonitor ID="NetAppSANtricity.FailureID_0439_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_FLASH_CACHE_NON_OPTIMAL_DRIVES_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.StateId46E9C74694EC7A2C911CB31FCA9CDDD9" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppSANtricity.StateIdEF8E72CDB302EDFFC18415FA655F933E" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>439</FailureID>
<IntervalSeconds>361</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>