Resolving installation issues
Use this information to resolve issues that you might have when setting up your system.
Solution does not power on
Check XCC web page can be logged in via out-of-band network interface.
Check the power button LED. If the power button LED is flashing slowly, press the power button to turn on the solution.
Check power supplies are installed correctly and power supply LEDs are lit normally.
If one or more sets of shared PCIe dual adapters are installed in the enclosure, reseat the nodes and the shared PCIe adapters that are installed in the enclosure, and reboot the nodes.
If the error recurs, check FFDC logs for more details.NoteTo collect FFDC logs, see
Collecting event logs for more details.
The solution immediately displays the POST Event Viewer when it is turned on
Correct any errors that are indicated by the light path diagnostics LEDs.
Make sure that the solution supports all the processors and that the processors match in speed and cache size.
You can view processor details from system setup.
To determine if the processor is supported for the solution, see Lenovo ServerProven website.
(Trained technician only) Make sure that processor 1 is seated correctly
(Trained technician only) Remove processor 2 and restart the solution.
Replace the following components one at a time, in the order shown, restarting the solution each time:
(Trained technician only) Processor
(Trained technician only) System board
Solution cannot recognize a drive
Verify that the drive is supported for the solution. See Lenovo ServerProven website for a list of supported hard drives.
Make sure that the drive is seated in the drive bay properly and that there is no physical damage to the drive connectors.
Run the diagnostics tests for the SAS/SATA adapter and hard disk drives. When you start a server 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 server at Lenovo XClarity Provisioning Manager portal page.) You can perform hard drive diagnostics from this interface. From the Diagnostic page, click .
Depending on the LXPM version, you may see HDD test or Disk Drive Test.Based on those tests:
If the adapter passes the test but the drives are not recognized, replace the backplane signal cable and run the tests again.
Replace the backplane.
If the adapter fails the test, disconnect the backplane signal cable from the adapter and run the tests again.
If the adapter fails the test, replace the adapter.
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. Power on the system and press F1 when the logo screen appears, the Lenovo XClarity Provisioning Manager interface will start. Perform memory diagnostics with this interface. 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.
A Lenovo optional device that was just installed does not work.
- Make sure that:
The device is supported for the solution (see Lenovo ServerProven website).
You followed the installation instructions that came with the device and the device is installed correctly.
You have not loosened any other installed devices or cables.
You updated the configuration information in the Setup utility. Whenever memory or any other device is changed, you must update the configuration.
Reseat the device that you just installed.
Check XCC event log for related errors, and follow the instructions to fix them. Go to List of XClarity Controller events and follow the instructions to fix the errors.
Replace the device that you just installed.
Voltage planar fault is displayed in the event log
Revert the system to the minimum configuration. See Specifications for the minimally required number of processors and DIMMs.
Restart the system.
If the system restarts, add each of the items that you removed one at a time, restarting the system each time, until the error occurs. Replace the item for which the error occurs.
If the system does not restart, suspect the system board.