- Notes, cautions, and warnings
- Introduction
- Change list
- NVDIMM-N Overview
- Hardware
- BIOS
- iDRAC NVDIMM-N Management
- Server Behavior with NVDIMM-Ns
- DIMM Configuration Changes
- Windows
- Linux
- ESXi
- General Errata
In the majority of cases where NVDIMM-N modules have an error, the system level behavior will be for the bad NVDIMM-N module to be put into a read-only state. This will cause any VMs mapped to ANY NVDIMM-N modules in the system to fail to power-on including VMs which are not mapped to the bad NVDIMM-N module. If an NVDIMM-N is flagged as having an error, resolve the issue with that NVDIMM-N then attempt to access VMs connected to the PMEM datastore again. Please see ESXi documentation for more information about migrating data and restoring access to impacted VMs.
Refer to table below for the Overall Health Status message shown on ESXi Web Client in the event of the following errors:
Status | Errors |
---|---|
Save Error – pre OS boot | Maintenance Needed |
Restore Error – pre OS boot | Maintenance Needed |
Erase Error – pre OS boot | Maintenance Needed |
Arm Error – pre OS boot | Maintenance Needed |
Controller Error – pre OS boot | Maintenance Needed |
Controller Error at OS run time | No OHS error until next boot, logged in SEL real time |
Invalid Firmware or Firmware running from Backup Slot | Maintenance Needed |
NVDIMM-N Battery Failure at OS run-time | All Data Loss |
NVDIMM-N Battery Failure – pre OS boot | Maintenance Needed |
All the above error messages are also accompanied by equivalent messages in the System Event Log and Lifecycle Controller Log as described in the Sections 5 and 6 of this User Guide.