IBM xSeries 300, Hardware Maintenance Manual

Page: 77 / 120

POST error codes
Error Code/Symptom FRU/Action
CMOS battery has failed Cause: CMOS battery is no longer functional. Action: Replace CMOS battery.
CMOS checksum error Cause: Checksum of COMS is incorrect. This can indicate that CMOS has become
corrupt. This error may have been caused by a weak battery. Action: Check the
battery and replace if necessary.
Disk boot failure, insert
system disk and press enter Cause: No boot device was found. This could mean that either a boot drive was not
detected or the drive does not contain proper system boot files. Action: Insert a
system disk into drive A: and press <Enter>. Make sure the controller is inserted
correctly and all cables are properly attached. Also be sure the disk is formatted as a
boot device. Then reboot the system.
Diskette drives or types
mismatch error Cause: Type of diskette drive installed in the system is different from the CMOS
definition. Action: Run Setup to reconfigure the drive type correctly.
Display switch is set
incorrectly Cause: Display switch on the motherboard can be set to either monochrome or color.
This indicates the switch is set to a different setting than indicated in setup.
Action:
Determine which setting is correct, and then either turn off the system and change
the jumper, or enter setup and change the video selection.
Display type has changed
since last boot Cause: Since last powering off the system, the display adapter has been changed.
Action: Configure the system for the new display type.
EISA configuration
checksum error Cause: The EISA non-volatile RAm checksum is incorrect or can not correctly read
the EIS slot. This can indicate either the EISA non-volatile memory has become
corrupt or the slot has been configured incorrectly. Ensure the card is installed firmly
in the slot.
Action: Run EISA configuration utility.
EISA configuration is not
complete Cause: The slot configuration information stored in the EISA non-volatile memory is
incomplete. Action: Run EISA configuration utility.
Error encountered
initializing hard drive Cause:
Hard drive cannot be initialized.
Action:
Ensure adapter is installed correctly
and all cables are correctly and firmly attached. Ensure the correct hard drive type is
selected in setup.
Error initializing hard disk
controller Cause: Cannot initialize controller. Action: Ensure the cable is correctly and firmly
installed in the bus. Ensure the correct hard drive type is selected in setup. Check to
see if any jumper needs to be set correctly on the hard drive.
Floppy disk cntrlr error or
no cntrlr present Cause: Can not find or initialize the floppy disk controller. Action: Make sure the
controller is installed correctly and firmly. If there are no floppy drives installed, be
sure the diskette drive selection in setup is set to None.
Invalid EISA configuration Cause: The non-volatile memory containing EIS configuration information was
programmed incorrectly or has become corrupt. Action: Re-run EIS configuration
utility to correctly program the memory.
Keyboard error or no
keyboard present Cause: Cannot initialize the keyboard. Action: Make sure the keyboard is attached
correctly and no keys are being pressed during the boot. If configuring the system
without a keyboard, set the error halt condition in setup to HALT ON ALL BUT
KEYBOARD. This will cause the BIOS to ignore the missing keyboard and continue
the boot.
Memory address error at ... Cause: Memory address error at specific location. Action: Use this location along
with the memory map for the system to find and replace the failed memory DIMM.
Memory parity error at ... Cause: Memory parity error at a specific location. Action: Use this location along
with the memory map for the system to find and replace the failed memory DIMM.
Memory size has changed
since last boot Cause: Memory has been added or removed since the last boot. Action: In EISA
mode, use configuration utility to reconfigure the memory. In ISA mode, enter setup
and enter the new memory size in the memory fields.
Memory verify error at ... Cause: Error verifying a value already written to memory. Action: Use the location
along with your system memory map to locate and replace the defective DIMM.
Chapter 7. Symptom-to-FRU index
69