Skip to main content

Observable problems

Use this information to solve observable problems.

Server hangs during the UEFI boot process​

If the system hangs during the UEFI boot process with the message UEFI: DXE INIT on the display, make sure that Option ROMs were not configured with a setting of Legacy. You can remotely view the current settings for Option ROMs by running the following command using the Lenovo XClarity Essentials OneCLI:

onecli config show EnableDisableAdapterOptionROMSupport --bmc xcc_userid:xcc_password@xcc_ipaddress

To recover a system that hangs during the boot process with Legacy Option ROM settings, see the following Tech Tip:

ThinkSystem server hangs during UEFI boot with "UEFI:DXE INIT" when option ROM settings configured for legacy

If legacy Option ROMs must be used, do not set slot Option ROMs to Legacy on the Devices and I/O Ports menu. Instead, set slot Option ROMs to Auto (the default setting), and set the System Boot Mode to Legacy Mode. Legacy option ROMs will be invoked shortly before the system boots.

The solution immediately displays the POST Event Viewer when it is turned on​

Complete the following steps until the problem is solved.

  1. Correct any errors that are indicated by the light path diagnostics LEDs.

  2. 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.

  3. (Trained technician only) Make sure that processor 1 is seated correctly

  4. (Trained technician only) Remove processor 2 and restart the solution.

  5. Replace the following components one at a time, in the order shown, restarting the solution each time:

    1. (Trained technician only) Processor

    2. (Trained technician only) System board

Solution is unresponsive (POST is complete and operating system is running)​

Complete the following steps until the problem is solved.

  • If you are in the same location as the compute node, complete the following steps:

    1. If you are using a KVM connection, make sure that the connection is operating correctly. Otherwise, make sure that the keyboard and mouse are operating correctly.

    2. If possible, log in to the compute node and verify that all applications are running (no applications are hung).

    3. Restart the compute node.

    4. If the problem remains, make sure that any new software has been installed and configured correctly.

    5. Contact your place of purchase of the software or your software provider.

  • If you are accessing the compute node from a remote location, complete the following steps:

    1. Make sure that all applications are running (no applications are hung).

    2. Attempt to log out of the system and log back in.

    3. Validate the network access by pinging or running a trace route to the compute node from a command line.

      1. If you are unable to get a response during a ping test, attempt to ping another compute node in the enclosure to determine whether it is a connection problem or compute node problem.

      2. Run a trace route to determine where the connection breaks down. Attempt to resolve a connection issue with either the VPN or the point at which the connection breaks down.

    4. Restart the compute node remotely through the management interface.

    5. If the problem remains, verify that any new software has been installed and configured correctly.

    6. Contact your place of purchase of the software or your software provider.

Solution is unresponsive (cannot press F1 to start System Setup)​

Configuration changes, such as added devices or adapter firmware updates, and firmware or application code problems can cause the solution to fail POST (the power-on self-test).

If this occurs, the solution responds in either of the following ways:

  • The solution restarts automatically and attempts POST again.

  • The solution hangs, and you must manually restart the solution for the solution to attempt POST again.

After a specified number of consecutive attempts (automatic or manual), the solution to reverts to the default UEFI configuration and starts System Setup so that you can make the necessary corrections to the configuration and restart the solution. If the solution is unable to successfully complete POST with the default configuration, there might be a problem with the system board. You can specify the number of consecutive restart attempts in System Setup. Click System Settings > Recovery > POST Attempts > POST Attempts Limit. Available options are 3, 6, 9, and 255.

Voltage planar fault is displayed in the event log​

Complete the following steps until the problem is solved.

  1. Revert the system to the minimum configuration. See Specifications for the minimally required number of processors and DIMMs.

  2. 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.

Unusual smell​

Complete the following steps until the problem is solved.

  1. An unusual smell might be coming from newly installed equipment.
  2. If the problem remains, contact Lenovo Support.

Solution seems to be running hot​

Complete the following steps until the problem is solved.

Multiple compute nodes or chassis:

  1. Make sure that the room temperature is within the specified range (see Specifications).
  2. Check the management processor event log for rising temperature events. If there are no events, the compute node is running within normal operating temperatures. Note that you can expect some variation in temperature.

Cracked parts or cracked chassis​

Contact Lenovo Support.