900100028
NVDIMM has lost persistence in the chassis ({chassis}). To protect the journal, setting the node to read-only.
Description
This event happens when NVDIMM detects something in its subsystem that will not allow it to persist DRAM through a
power-loss event. This could be related to the DRAM itself or the battery backup unit (BBU).
Administrator action
The node is placed into a read-only state to protect the journal. If the NVDIMM was bad during startup, the node will not be
armed. Therefore, to re-gain persistence, the node automatically restarts (the cluster is notified, the cluster waits 60 seconds,
and then restarts). If the issue does not clear itself, escalate, and determine if the issue is related to the NVDIMM or the
battery.
A service request (SR) has been opened on your behalf. Technical Support will contact you.
900100029
NVDIMM has regained persistence in the chassis ({chassis}). The node will reboot to re-arm NVDIMM.
Description
The node lost persistence but has recovered. The node requires a reboot to re-arm the NVDIMM.
Administrator action
Wait for the node restart (this should happen 60 seconds from when the event occurs), or manually restart the node if the
message continues.
900100030
NVDIMM in the DIMM slot has failed in the chassis ({chassis}). Until the NVDIMM is replaced, setting the node to read-only
Description
NVDIMM has failed. Node will transition to read-only mode until the NVDIMM has been replaced.
Potential causes
●
NVDIMM experiences similar wear to regular DIMMs.
●
The NVDIMM is seated incorrectly, damaged, or not responding.
●
End of supported life duration.
●
Unable to save the data during the previous system shutdown operation, or power loss. The NVDIMM is placed in write-
protect mode.
Administrator action
●
Refer to the error message and follow the OEM instructions.
●
For an unreachable NVDIMM, reseat the DIMM. If the issue continues, replace the NVDIMM.
168
Hardware events