Skip to main content

Intermittent problems

Use this information to solve intermittent problems.

  • Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved.
  • See Parts listing, Lenovo System x3550 M3 Type 4254 and 7944 to determine which components are customer replaceable units (CRU) and which components are field replaceable units (FRU).
  • If an action step is preceded by (Trained service technician only), that step must be performed only by a Trained service technician.
  • Go to the IBM support website at Lenovo Data Center Support to check for technical information, hints, tips, and new device drivers or to submit a request for information.
A problem occurs only occasionally and is difficult to diagnose.
  1. Make sure that:
    • All cables and cords are connected securely to the rear of the server and attached devices.
    • When the server is turned on, air is flowing from the fan grille. If there is no airflow, the fan is not working. This can cause the server to overheat and shut down.
  2. Check the system-error log or IMM system event log (see Event logs).
The server resets (restarts) occasionally.
  1. If the reset occurs during POST and the POST watchdog timer is enabled (click System Settings > Integrated Management Module > POST Watchdog Timer in the Setup utility to see the POST watchdog setting), make sure that sufficient time is allowed in the watchdog timeout value (POST Watchdog Timer). If the server continues to reset during POST, see POST error codes and Diagnostic messages.
  2. If the reset occurs after the operating system starts, disable any automatic server restart (ASR) utilities, such as the IBM Automatic Server Restart IPMI Application for Windows, or any ASR devices that are be installed.
    ASR utilities operate as operating-system utilities and are related to the IPMI device driver. If the reset continues to occur after the operating system starts, the operating system might have a problem; see Software problems.
  3. If neither condition applies, check the system-error log or IMM system-event log (see Event logs).