Errors symptoms - IBM eServer xSeries 235

1. Verify that:

   • The IDE channel to which the CD-ROM drive is attached (primary or secondary) is enabled in the Configuration/Setup Utility program.
     
     NOTE: On a server with a single IDE channel, only the primary channel can be used.
     
     
   • All cables and jumpers are installed correctly.
   • The correct device driver is installed for the CD-ROM drive.
     
     
2. Run CD-ROM drive diagnostics.
3. CD-ROM drive.

1. If there is a diskette in the drive, verify that:

   • The diskette drive is enabled in the Configuration/Setup utility program.
   • The diskette is good and not damaged. (Try another diskette if you have one.)
   • The diskette is inserted correctly in the drive.
   • The diskette contains the necessary files to start the server.
   • The software program is working properly.
   • The cable is installed correctly (in the proper orientation).
     
     
2. Run diskette drive diagnostics
3. Cable
4. Diskette drive
5. System board

1. Verify that:

   • The cables for all external SCSI options are connected correctly.
   • The last option in each SCSI chain, or the end of the SCSI cable, is terminated correctly.
   • Any external SCSI option is turned on. You must turn on an external SCSI option before turning on the server.
     
     
2. For more information, see your SCSI expansion enclosure documentation.

1. Remove the first drive not recognized and try the hard disk drive diagnostic test again.
2. If the remaining drives are recognized, replace the drive you removed with a new one.

1. Remove the hard disk drive being tested when the server stopped responding and try the diagnostic test again.
2. If the hard disk drive diagnostic test runs successfully, replace the drive you removed with a new one.

Broken CRU/FRU

1. Verify that:
   • All cables and cords are connected securely to the rear of the server and attached options.
   • When the server is turned on, air is flowing from the rear of the server at the fan grill. If there is no airflow, the fan is not working. This causes the server to overheat and shut down.
   • Ensure that the SCSI bus and devices are configured correctly and that the last external device in each SCSI chain is terminated correctly.
     
     
2. Check the system error log.

1. Verify that:

   • The keyboard cable is securely connected to the system, and the keyboard and mouse cables are not reversed.
   • The server and the monitor are turned on.
     
     
2. Keyboard
3. System board

1. Verify that:

   • The mouse or pointing-device cable is securely connected, and that the keyboard and mouse cables are not reversed.
   • The mouse device drivers are installed correctly.
     
     
2. Mouse or pointing device
3. System board

1. Verify that:
   • The memory modules are seated properly.
   • You have installed the correct type of memory.
   • If you changed the memory, you updated the memory configuration with the Configuration/Setup Utility program.
   • All banks of memory on the DIMMs are enabled. The server might have automatically disabled a DIMM bank when it detected a problem or a DIMM bank could have been manually disabled.
     
     
2. Check POST error log for error message 289:
   • If the DIMM was disabled by a system-management interrupt (SMI), replace the DIMM.
   • If the DIMM was disabled by the user or by POST:
     • Start the Configuration/Setup Utility program.
     • Enable the DIMM.
     • Save the configuration and restart the server.
       
       
3. DIMM
4. System board

1. Verify that the startup microprocessor is seated properly.
2. Startup microprocessor.

1. Verify that:

   • The server power cord is plugged into the server and a working electrical outlet.
   • The monitor cables are connected properly.
   • The monitor is turned on and the Brightness and Contrast controls are adjusted correctly.
   • If the servers are C2T chained together, verify that:
     • The C2T chain cables are securely connected to the servers.
     • The C2T breakout cable is connected properly.
     • A server that is turned on is selected.
       
       NOTE: In some memory configurations, the 3-3-3 beep code might sound during POST followed by a blank display screen. If this occurs and the Boot Fail Count feature in the Start Options of the Configuration/Setup Utility program is set to Enabled (its default setting), you must restart the server three times to force the system BIOS to reset the CMOS values to the default configuration (memory connector or bank of connectors enabled).
       

2. If you have verified these items and the screen remains blank, replace:
   • Monitor
   • Video adapter, if installed
   • System board

See “Undetermined problems” on page 151 in the HMM.

1. Verify that:
2. • The application program is not setting a display mode higher than the capability of the monitor.
   • The primary monitor cable is connected to the C2T device breakout cable.
   • You installed the necessary device drivers for the applications.
     
     
3. If you have verified these items and the screen remains blank, replace the monitor.

1. If the monitor self-tests show the monitor is working properly, consider the location of the monitor. Magnetic fields around other devices (such as transformers, appliances, fluorescent lights, and other monitors) can cause screen jitter or wavy, unreadable, rolling, or distorted screen images. If this happens, turn off the monitor. (Moving a color monitor while it is turned on might cause screen discoloration.) Then move the device and the monitor at least 305 mm (12 inch) apart. Turn on the monitor.

NOTES:

2. 1. To prevent diskette drive read/write errors, be sure the distance between monitors and diskette drives is at least 76 mm (3 in.).
   2. Non-IBM monitor cables might cause unpredictable problems.
   3. An enhanced monitor cable with additional shielding is available for the 9521 and 9527 monitors. For information about the enhanced monitor cable, contact your IBM reseller or IBM marketing representative.
      
      
3. Video adapter, if installed.
4. System board.

1. If the wrong language is displayed, update the BIOS code with the correct language.
2. Video adapter, if installed.
3. System board.

1. Verify that:

2. Option you just installed.

1. Verify that all of the option hardware and cable connections are secure.
2. If the option comes with its own test instructions, use those instructions to test the option.
3. If the failing option is a SCSI option, verify that:
   • The cables for all external SCSI options are connected correctly.
   • The last option in each SCSI chain, or the end of the SCSI cable, is terminated correctly.
   • Any external SCSI option is turned on. You must turn on an external SCSI option before turning on the server.
     
     
4. Failing option.

1. Verify that:

   • The power cables are properly connected to the server.
   • The electrical outlet functions properly.
   • The type of memory installed is correct.
   • If you just installed an option, remove it, and restart the server. If the server now turns on, you might have installed more options than the power supply supports.
     
     
2. If LEDs for CPUs or VRMs are on, verify that:
   1. A VRM is populated for each microprocessor.
   2. All microprocessors have the same speed.
   3. Override front panel pushbutton by turning on switch 7 of SW1; if power comes on:
      1. Service processor error.
      2. Power reset card.
         
         
3. See “Undetermined problems” on page 151 in the HMM.

1. Verify whether you are using an ACPI or non-ACPI operating system. If you are using a non-ACPI operating system:

   1. Press Ctrl+Alt+Delete.
   2. Turn off the system by holding the power-control button for 4 seconds.
   3. If server fails during BIOS POST and power-control button does not work, remove the AC power cord.
      
      
2. If the problem remains or if you are using an ACPI-aware operating system, suspect the system board.

1. Verify that:

   • Each port is assigned a unique address by the Configuration/Setup Utility program and none of the serial ports is disabled.
   • The serial port adapter, if you installed one, is seated properly.
     
     
2. Failing serial port adapter.

1. Verify that:

   • The device is compatible with the server.
   • The serial port is enabled and is assigned a unique address.
   • The device is connected to the correct port (see "Input/output connectors" on page 104).
     
     
2. Failing serial device.
3. Serial adapter, if installed.
4. System board.

1. To determine if problems are caused by the software, verify that:

   • Your server has the minimum memory needed to use the software. For memory requirements, see the information that comes with the software.
     
     NOTE: If you have just installed an adapter or memory, you might have a memory address conflict.
     
     
   • The software is designed to operate on your server.
   • Other software works on your server.
   • The software that you are using works on another system.
     If you received any error messages when using the software program, see the information that comes with the software for a description of the messages and suggested solutions to the problem.

    

2. If you have verified these items and the problem remains, contact your place of purchase.

Verify that:

• You are not trying to use a USB device during POST if you have a standard (non-USB) keyboard attached to the keyboard port.
  
  NOTE: If a standard (non-USB) keyboard is attached to the keyboard port, the USB is disabled and no USB device will work during POST.
  
  
• The correct USB device driver is installed.
• Your operating system supports USB devices.