Skip to main content
NetApp Knowledge Base

H610S: erroneous NVRAM error messages

Views:
2,358
Visibility:
Public
Votes:
4
Category:
h-series
Specialty:
hci
Last Updated:

Applies to

NetApp H610S storage node

Issue

This article addresses sporadic logging of NVRAM faults on H610S nodes, which often results in eviction of node's slice (metadata) drive

  • The node logs a variation of one of the following NVRAM (NVDIMM) faults:
  • NVRAM device critical={Device: 0x1000004 Key: armStatusSaveNArmed, Device: 0x1000004 Key: notEnoughEnergyForCatastrophicSave}
  • NVRAM device error={Device: 0x1000004 Key: energySourceTemperatureStatus Device: 0x1000004 CurTemp: Unknown HighTemp: Unknown LowTemp: Unknown Device: 0x1000104 CurTemp: Unknown HighTemp: Unknown LowTemp: Unknown} critical={Device: 0x1000004 Key: armStatusSaveNArmed, Device: 0x1000004 Key: notEnoughEnergyForCatastrophicSave, Device: 0x1000004 Key: warningThresholdExceeded}
  • NVRAM device problems detected, metadata drive will be removed. Contact NetApp Support.  error={Device: 0x1000004 Key: energySourceLifetimeStatus} critical={Device: 0x1000004 Key: armStatusSaveNArmed, Device: 0x1000004 Key: energySourceHardwareFailure, Device: 0x1000004 Key: energySourceHealthAssessmentError, Device: 0x1000004 Key: noEnergySourcePresent, Device: 0x1000004 Key: notEnoughEnergyForCatastrophicSave, Device: 0x1000004 Key: warningThresholdExceeded}
  • NVRAM device warning={[Device: 0x1000105, Key: 0x700cc0]}
  • NVRAM device problems detected, metadata drive will be removed. Contact NetApp Support. warning={[Device: 0x1000005, Key: 0x300cc0]} error={[Device: 0x1000005, Key: 0x800000]}
  • platformHardwareEvent: Suppressing Nvdimm status result 1/3 as false positive
  • platformHardwareEvent: Nvdimm status has stabilized after 1 failed result(s)
  • The node's slice/metadata drive (drive 0) may be ejected, depending on error that is logged and Element OS version the node is running
If node is running  
Element 10.x Slice drive will most likely not be ejected, depending on timing factors within Element
Element 11.0 through 11.1 Slice drive will be ejected, regardless of timing
Element 11.3.0 Slice drive may be ejected, depending on which of the above mentioned faults was experienced
  • NVRAM (NVDIMM) fault resolves on its own less than 5 minutes later
  • If node's slice/metadata drive (drive 0) was ejected, it will not automatically re-add

Note: If these alerts are resolved, no further action from support is required

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.