Skip to main content

Diagnosing a problem

Before you , follow these procedures in the order in which they are presented to diagnose a problem with your server.

  1. Return the server to the condition it was in before the problem occurred.
    If any hardware, software, or firmware was changed before the problem occurred, if possible, reverse those changes. This might include any of the following items:
    • Hardware components
    • Device drivers and firmware
    • System software
    • UEFI firmware
    • System input power or network connections
  2. View the light path diagnostics LEDs and event logs.
    The server is designed for ease of diagnosis of hardware and software problems.
    • Light path diagnostics LEDs: See Light path diagnostics for information about using light path diagnostics LEDs.
    • Event logs: See Event logs for information about notification events and diagnosis.
    • Software or operating-system error codes: See the documentation for the software or operating system for information about a specific error code. See the manufacturer's website for documentation.
  3. Run Dynamic System Analysis (DSA) and collect system data.

    Run Dynamic System Analysis (DSA) to collect information about the hardware, firmware, software, and operating system. Have this information available when you . For instructions for running DSA, see the Dynamic System Analysis Installation and User's Guide.

  4. Check for and correct an incorrect configuration.

    If the server is incorrectly configured, a system function can fail to work when you enable it; if you make an incorrect change to the server configuration, a system function that has been enabled can stop working.

    1. Make sure that all installed hardware and software are supported.

      See Lenovo ServerProven website to verify that the server supports the installed operating system, optional devices, and software levels. If any hardware or software component is not supported, uninstall it to determine whether it is causing the problem. You must remove nonsupported hardware before you .

    2. Make sure that the server, operating system, and software are installed and configured correctly.

      Many configuration problems are caused by loose power or signal cables or incorrectly seated adapters. You might be able to solve the problem by turning off the server, reconnecting cables, reseating adapters, and turning the server back on. For information about performing the checkout procedure, see About the checkout procedure. For information about configuring the server, see Configuring the server.

  5. See controller and management software documentation.

    If the problem is associated with a specific function (for example, if a RAID hard disk drive is marked offline in the RAID array), see the documentation for the associated controller and management or controlling software to verify that the controller is correctly configured.

    Problem determination information is available for many devices such as RAID and network adapters.

  6. Use the troubleshooting tables.

    See Troubleshooting by symptom to find a solution to a problem that has identifiable symptoms.

    A single problem might cause multiple symptoms. Follow the troubleshooting procedure for the most obvious symptom. If that procedure does not diagnose the problem, use the procedure for another symptom, if possible.

    If the problem remains. Be prepared to provide information about any error codes and collected data.