Use this information to resolve issues related to memory.
Displayed system memory less than installed physical memory
- Make sure that:
No error LEDs are lit on the operator information panel.
Memory mirrored channel does not account for the discrepancy.
The memory modules are seated correctly.
You have installed the correct type of memory module (see Specifications for requirements).
If you changed the memory, you updated the memory configuration in the Setup utility.
All banks of memory are enabled. The solution might have automatically disabled a memory bank when it detected a problem, or a memory bank might have been manually disabled.
There is no memory mismatch when the solution is at the minimum memory configuration.
When DCPMMs are installed:
If the memory is set in App Direct or Mixed Memory Mode, all the saved data have been backed up, and created namespaces are deleted before any DCPMM is replaced.
Refer to DC Persistent Memory Module (DCPMM) setup and see if the displayed memory fits the mode description.
If DCPMMs are recently set in Memory Mode, turn it back to App Direct Mode and examine if there is namespace that has not been deleted (see DC Persistent Memory Module (DCPMM) setup).
Go to the Setup Utility, select, and make sure all the DCPMM units are unlocked.
Reseat the memory modules, and then restart the solution.
Check the POST error log:
If a memory module was disabled by a systems-management interrupt (SMI), replace the memory module.
If a memory module was disabled by the user or by POST, reseat the memory module; then, run the Setup utility and enable the memory module.
Run memory diagnostics. When you start a solution and press the key according to the on-screen instructions, the LXPM interface is displayed by default. (For more information, see the “Startup” section in the LXPM documentation compatible with your solution at Lenovo XClarity Provisioning Manager portal page.) You can perform memory diagnostics with this interface. From the Diagnostic page, go to or DCPMM test.When DCPMMs are installed, run diagnostics based on the current DCPMM mode:
App Direct Mode
Run DCPMM Test for DCPMMs.
Run Memory Test for DRAM DIMMs.
Memory Mode and Mixed Memory Mode
NoteDRAM DIMMs in these two modes act as cache, and are not applicable to memory diagnostics.
Run DCPMM Test for App Direct capacity of DCPMMs.
Run Memory Test for memory capacity of DCPMMs.
- Reverse the modules between the channels (of the same processor), and then restart the solution. If the problem is related to a memory module, replace the failing memory module.NoteWhen DCPMMs are installed, only adopt this method in Memory Mode.
Re-enable all memory modules using the Setup Utility, and restart the system.
(Trained technician only) Install the failing memory module into a memory module connector for processor 2 (if installed) to verify that the problem is not the processor or the memory module connector.
(Trained technician only) Replace the node.
Multiple memory modules in a channel identified as failing
- Reseat the memory modules; then, restart the solution.
- Remove the highest-numbered memory module of those that are identified and replace it with an identical known good memory module; then, restart the solution. Repeat as necessary. If the failures continue after all identified memory modules are replaced, go to step 4.
- Return the removed memory modules, one at a time, to their original connectors, restarting the solution after each memory module, until a memory module fails. Replace each failing memory module with an identical known good memory module, restarting the solution after each memory module replacement. Repeat step 3 until you have tested all removed memory modules.
- Replace the highest-numbered memory module of those identified; then, restart the solution. Repeat as necessary.
- Reverse the memory modules between the channels (of the same processor), and then restart the solution. If the problem is related to a memory module, replace the failing memory module.
- (Trained technician only) Install the failing memory module into a memory module connector for processor 2 (if installed) to verify that the problem is not the processor or the memory module connector.
- (Trained technician only) Replace the system board.
Attempt to change to another DCPMM mode fails
After the DCPMM mode is changed and the system is successfully restarted, if the DCPMM mode stays the same instead of being changed, check the DRAM DIMMs and DCPMM capacity to see if it meets the requirement of the new mode (see DC Persistent Memory Module (DCPMM) setup).
Extra namespace appears in an interleaved region
If there are two created namespaces in one interleaved region, VMware ESXi ignores the created namespaces and creates an extra new namespace during system booting. To solve this problem, delete the created namespaces in either the Setup Utility or the operating system before the first booting with ESXi.