Error symptoms - IBM eServer xSeries 360

1. Clean the CD
2. Check cables
3. Run diagnostics
4. CD-ROM drive

1. Insert the end of a paper clip into the manual tray-release opening
2. Run diagnostics
3. CD-ROM drive

1. Run Configuration/Setup, enable primary IDE channel
2. Check cables and jumpers
3. Check for correct device driver
4. Run CD-ROM diagnostics
5. CD-ROM drive
6. System board

1. Verify that Operator Panel cable is attached
2. Power switch assembly
3. System board

1. Make sure Operator Panel is plugged in

1. Make sure CD-ROM drive cable is plugged in

1. If there is a diskette in the drive, verify that:
   1. The diskette drive is enabled in the Configuration/Setup utility program.
   2. The diskette is good and not damaged. (Try another diskette if you have one.)
   3. The diskette is inserted correctly in the drive.
   4. The diskette contains the necessary files to start the server.
   5. The software program is OK.
   6. Cable is installed correctly (proper orientation).
2. Run diskette drive diagnostics
3. Cable
4. Diskette drive
5. System board

1. Remove first disk that does not show up and rerun diagnostic. If remaining drives show up, replace the one that was removed.
2. If remaining drives do not show up, remove successive drives one at a time and rerun diagnostic.

1. Remove hard disk being tested at the time of the hang and rerun the diagnostic. If successful, replace drive that was removed.

Verify that:

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

Verify that:

1. The memory modules are seated properly.
2. You have installed the correct type of memory.
3. If you changed the memory, you updated the memory configuration with the Configuration/Setup utility program.
4. All banks of memory on the DIMMs are enabled. The server might have automatically disabled a DIMM bank if it detected a problem, or a DIMM bank might have been manually disabled.

If these items are correct, run the memory diagnostic program. The server might have detected a bad memory module and automatically reallocated memory to enable the server to continue to operate. Check error log.

1. Monitor
2. Run diagnostics. If diagnostics pass, the problem may be a video driver.
3. Display adapter / System board

Verify that:

1. The server power cords are plugged into the server and a working electrical outlet.
2. The monitor cables are connected properly.
3. The monitor is turned on and the brightness and contrast controls are adjusted correctly
4. Display adapter
5. System board

Important: 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 is set to Enabled (its default setting), you must restart the server three times to force the system BIOS to reset the memory connector or bank of connectors from Disabled to Enabled.

1. Make sure correct machine is selected.
2. Make sure all cables are locked down.

Verify that:

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

1. Make sure that the keyboard cable is properly connected to the server.
2. Make sure that the server and the monitor are turned on.
3. Try using another keyboard.

1. Verify that the mouse or pointing-device cable is securely connected and the device drivers are installed correctly.
2. Try using another mouse or pointing device.

Verify that:

1. The memory modules are seated properly.
2. You have installed the correct type of memory.
3. If you changed the memory, you updated the memory configuration with the Configuration/Setup utility program.
4. All banks of memory on the DIMMs are enabled. The server might have automatically disabled a DIMM bank if it detected a problem, or a DIMM bank might have been manually disabled.

If these items are correct, run the memory diagnostic program. The server might have detected a bad memory module and automatically reallocated memory to enable the server to continue to operate. If the memory tests fail, replace the failing DIMM.

The startup (boot) microprocessor is not working properly.

Verify that the startup microprocessor is seated properly. If it is, replace the startup microprocessor.

Verify that:

1. The primary monitor cable is connected to the video port.
2. You installed the necessary device drivers for the applications.

If the monitor self-tests show the monitor is working correctly, 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 in.) apart. Turn on the monitor.

NOTES:

1. To prevent diskette drive read/write errors, be sure that 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 IBM model 9521 and 9527 monitors.

Verify that:

1. The server supports the option. Refer to the Server Support flowchart for information about obtaining ServerProven compatibility information from the World Wide Web.
2. You followed the installation instructions that come with the option.
3. The option is installed correctly.
4. You have not loosened any other installed options or cables.
5. You updated the configuration information using the Configuration/Setup utility program. Whenever memory or an option is changed, you must update the configuration.

Verify that all of the option hardware and cable connections are secure.

If the option comes with its own test instructions, use those instructions to test the option.

If the failing option is a SCSI option, verify that:

1. The cables for all external SCSI options are connected correctly.
2. The last option in each SCSI chain, or the end of the SCSI cable, is terminated correctly.
3. Any external SCSI option is turned on. You must turn on an external SCSI option before turning on the server.

Verify that:

1. The power cables are properly connected to the server.
2. The electrical outlet functions properly.
3. The type of installed memory is correct.
4. If you just installed an option, remove it, and restart the server. If the server now powers on, you might have installed more options than the power supply supports.
5. The LEDs on the power supply are on.
6. Verify that processors are installed in the correct sequence. See "Microprocessor installation" in the Hardware Maintenance Manual.

Verify that 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 pressing the power-control button.

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

1. Your server has the minimum memory requirements 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.
2. The software is designed to operate on your server.
3. Other software works on your server.
4. 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 solutions to the problem.

If the problem remains, contact your place of purchase.

Verify that:

1. 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.
2. The correct USB device driver is installed.
3. Your operating system supports USB devices.