Data Domain: NVRAM Failure Detected | Error or Faulty Condition
Summary: The NVRAM and its Battery Backup Unit (BBU) are critical components of the Data Domain Data Invulnerability Architecture. The Data Domain Operating System (DDOS) monitors these components. If a hardware fault occurs, DDOS generates an alert that must be addressed immediately to maintain system integrity. ...
Symptoms
⚠️ Important: Do not replace an NVRAM card or BBU 'proactively'. Failed components in the NVRAM assembly must be confirmed by reviewing DDOS alerts, NVRAM status and TSR logs. Replace the NVRAM card or BBU only after DDOS reports a failure condition or Dell Support determines replacement is required.
Applies to:
- All Data Domain systems
- All DDOS software versions
Possible Alerts:
NVRAM-00001: File system is disabled due to a problem with the NVRAM subsystemNVRAM-00002: Battery at low charge and not chargingNVRAM-00003: Excessive PCI or memory errorsNVRAM‑00201: Hardware fault detected with NVRAM cardNVRAM-00202: Hardware fault detected with NVRAM remote batteryNVRAM-00204: Invalid condition detected with NVRAM battery
Cause
DDOS monitors the NVRAM subsystem continuously. When it detects a fault in the NVRAM card or BBU, it posts an alert.
The alert typically includes diagnostic details, but further investigation may be required to determine the correct component to replace in an NVRAM assembly.
Resolution
Resolving the alert involves identifying the affected component of the NVRAM assembly.
- Legacy Data Domain systems have "all-in-one' PCIe NVRAM cards - ie. the card contains the Processor, Storage and Battery
- Any reported failure generally requires an NVRAM card replacement.
- Systems may PANIC after encountering an NVRAM issue; the resulting reboot may recover the system and NVRAM successfully.
- Current Data Domain systems (for example, DD9910, 9410, 6410, 9910F) use SDPM/VOSS NVRAM (Software Defined Persistent Memory / Vault-Optimized Storage System), which is fundamentally different from legacy NVRAM systems. SDPM consists of 9 separate, individual components actively monitored by iDRAC.
Customer actions:
- Confirm the NVRAM failure
- Generate a Support Bundle
- Raise a Service Request with your support provider.
Useful CLI Commands:
-
# alerts show current # Check for active NVRAM or battery alerts # system show nvram # Review card errors and battery status # system show hardware # Confirm NVRAM card presence
Additional Information
Example:
- Here we see a good NVRAM - Zero 'Errors' & all Battery Statuses are 'OK' (even though charge is at ~96%)
sysadmin@itsaDD# system show nvram
NVRAM Cards:
Card Component Value
---- ------------------- -----------------------------------------------
1 Slot 10
Firmware version 2.0.4
Memory size 3.93 GiB
Errors 0 memory (0 uncorrectable), 0 PCI, 0 controller
Board temperature 35 C
CPU temperature 41 C
Number of batteries 4
Card model no 313-163-100A-02
Card serial no FLA011301nnnnn
Battery model no 313-164-100A-01
Battery serial no FLA021242nnnnn
---- ------------------- -----------------------------------------------
NVRAM Batteries:
Card Battery Status Charge Charging Time To Temperature Voltage
Status Full Charge
---- ------- ------ ------ -------- ----------- ----------- -------
1 1 ok 96 % enabled 0 mins 26 C 8.088 V
2 ok 95 % enabled 0 mins 27 C 8.082 V
3 ok 97 % enabled 0 mins 25 C 8.084 V
4 ok 95 % enabled 0 mins 26 C 8.072 V
---- ------- ------ ------ -------- ----------- ----------- -------