H610s ： NVRAM 错误消息

NetApp H610S storage node

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

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 problems detected, metadata drive will be removed. Contact NetApp Support. warning={[Device: 0x1000005, Key: 0x300cc0]} error={[Device: 0x1000005, Key: 0x800000]}

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 不 be ejected, depending on timing factors within Element
Element 11.0 through 11.1	Slice drive 将 be ejected, regardless of timing
Element 11.3.0	Slice drive 5 月 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, itwill not automatically re-add

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