Dell™ PowerEdge™ 1650 Systems Service Manual
This section describes system error messages, beep codes, and indicator codes that can occur during system start-up or, in the case of some failures, during normal system operation. The tables in this section list faults that can cause a beep code or system error message to occur and the probable causes of the fault in each case. This section also suggests actions you can take to resolve problems indicated by a message.
If a faulty system does not emit beep codes or display system error messages to indicate a failure, you should run the appropriate tests in the system diagnostics to help isolate the source of the problem.
Several different types of messages can indicate when the system is not functioning properly:
System messages alert you to a possible system problem or to a conflict between the software and hardware. Table 1 lists the system error messages that can occur and the probable cause for each message.
If the table does not lead to the source of the problem, run the
appropriate tests in the system
diagnostics to assist in troubleshooting the problem.
 |
NOTE: If you receive a system message
that is not listed in Table 1, check the documentation for the application program that is
running when the message appears and/or the operating system documentation for an
explanation of the message and recommended action. |
| Message | Cause | Corrective Action |
|---|---|---|
| Address mark not found | Faulty diskette/CD drive or hard-drive subsystem (defective system board). | Replace the system board. |
| Amount of available memory limited to 256 MB! | OS Install Mode is enabled in the System Setup program. | Disable OS Install Mode in the System Setup program. |
|
Auxiliary device failure |
Mouse or keyboard cable connector loose or improperly connected; defective mouse or keyboard. |
Check the mouse and keyboard cable connections. |
|
BIOS Update Attempt Failed! |
Remote BIOS update attempt failed. |
Retry the BIOS update. |
|
Caution! NVRAM_CLR jumper is installed on system board - please run SETUP program |
Incorrect configuration settings in System Setup program, NVRAM_CLR jumper is installed, or faulty system battery. |
Check the System Setup configuration settings. See "Using the System Setup Program." Remove the NVRAM_CLR jumper (see Figure 2 for jumper location). Replace the battery. See "Replacing the System Battery." |
|
CPUs with different cache sizes detected |
Two different types of microprocessors are installed. |
Install a correct version of the microprocessor so that both microprocessors have the same level 2 cache size. See "Adding or Replacing a Microprocessor" |
|
Decreasing available memory |
One or more memory modules improperly seated or faulty. |
Remove and reseat the memory modules. See "Removing Memory Modules." If the problem persists, replace the memory modules. If the problem still persists, replace the system board. |
|
Diskette drive 0 seek failure
|
Faulty or improperly inserted diskette, incorrect configuration settings in System Setup program, or loose diskette interface cable. |
Replace the diskette. Run the System Setup program to correct the diskette drive type. Check that the diskette drive interface cable is connected correctly. See "Replacing Drives." |
|
Diskette read failure |
Faulty diskette, or faulty or improperly connected diskette drive. |
Check that the diskette drive interface cable is connected correctly. See "Replacing Diskette Drives." |
|
Diskette subsystem reset failed |
Faulty diskette/CD drive controller (defective system board). |
Replace the system board. |
|
ECC memory error |
Improperly seated or faulty memory modules. |
Remove and reseat the memory modules. See "Removing Memory Modules." If the problem persists, replace the memory modules. If the problem still persists, replace the system board. |
|
Embedded server management error Embedded server management is not present |
Embedded server management memory may be temporarily corrupted. |
To clear the embedded server management memory, shut down the system, disconnect the power cable(s), wait approximately 30 seconds, and then reconnect the power cable(s) and restart the system. If the problem persists, replace the system board. |
|
Error: Dell Remote Access Card initialization failure |
Defective server management card or system board. |
Replace the expansion card. See "Replacing Expansion Cards." If the problem persists, replace the system board. |
|
Gate A20 failure |
Faulty keyboard controller (defective system board). |
|
|
Hard disk controller failure Hard disk read failure |
Incorrect configuration settings in System Setup program, improperly connected hard drive, faulty hard-drive controller subsystem (defective system board), or loose power cable. |
Check the hard-drive configuration settings in the System Setup program. Reinstall the hard drive. See "Replacing Drives." Check the interface cable and power cable connections to the backplane board. |
|
Invalid configuration information - please run SETUP program |
Incorrect configuration settings in System Setup program, NVRAM_CLR jumper is installed, or faulty system battery. |
Check the System Setup configuration settings. See "Using the System Setup Program." Remove the NVRAM_CLR jumper. See Figure 2 for jumper location. Replace the battery. See "Replacing the System Battery." |
|
Invalid memory configuration detected. Potential for data corruption exists! |
Memory modules are not installed in matched pairs. |
Install memory modules in matched pairs. See "Adding or Installing Memory Modules." |
|
Invalid NVRAM configuration, resource re-allocated |
System configuration data has been ignored. |
Check the System Setup configuration settings. See "Using the System Setup Program.". |
|
I/O parity interrupt at address |
Expansion card(s) is improperly installed or faulty. |
Reinstall the expansion card(s). See "Replacing Expansion Cards." If the problem persists, replace the expansion card(s). |
|
Keyboard controller failure |
Defective keyboard/mouse controller (defective system board). |
|
|
Keyboard data line failure Keyboard stuck key failure Keyboard clock line failure Keyboard failure |
Keyboard cable connector is loose or improperly connected; defective keyboard; defective keyboard/mouse controller (defective system board). |
Check the keyboard cable connection. Replace the keyboard. If the problem persists, replace the system board. |
|
Memory address line failure at address, read value expecting value Memory high data line failure at start address to end address Memory high address line failure at start address to end address Memory double word logic failure at start address to end address Memory odd/even logic failure at start address to end address Memory write/read failure at address, read value expecting value |
Faulty or improperly seated memory modules or defective system board. |
Remove and reseat the memory modules. See "Installing Memory Modules." If the problem persists, replace the memory modules. If the problem still persists, replace the system board. |
|
Memory parity failure at start address to end address Memory parity error at address |
Improperly seated or faulty memory modules. |
Remove and reseat the memory modules. See "Installing Memory Modules." If the problem persists, replace the memory modules. If the problem still persists, replace the system board. |
|
No boot device available |
Faulty diskette, diskette/CD drive subsystem, hard drive, or hard-drive subsystem; no boot disk in drive A. |
Check the boot device configuration settings in the System Setup program. If they were disabled, enable them and reboot. If the problem persists, replace the diskette or the hard drive. See "Replacing Drives." If the problem still persists, replace the system board. |
|
No boot sector on hard-disk |
No operating system on hard drive. |
Check the hard-drive configuration settings in the System Setup program. See "Using the System Setup Program." |
|
No timer tick interrupt |
Defective system board. |
|
|
No PXE-capable device available |
<F12> pressed during POST and no PXE devices are detected. |
Check the cables connected to the NICs. Check the configuration settings in the System Setup program for the NICs. See "Using the System Setup Program." |
|
Not a boot diskette |
No operating system on diskette. |
Use a bootable diskette. |
|
Plug & Play Configuration Error Embedded xxx
|
Error encountered in initializing PCI device, or defective system board. |
Install NVRAM_CLR jumper and reboot the system. See Figure 2 for jumper location. If problem persists, replace the system board. |
|
Plug & Play Configuration Error PCI_n |
Error encountered in initializing PCI adapter. |
Install NVRAM_CLR jumper and reboot the system. See Figure 2 for jumper location. If the problem persists, replace the specified expansion card. See "Installing Expansion Cards." If the problem still persists, replace the system board. |
|
Primary backplane error |
Improperly attached or missing backplane. |
Check that the SCSI backplane board is fully seated. See "Replacing Drives." |
|
Primary IDE device 0 not found Primary IDE device 1 not found |
Improperly connected or missing IDE device. |
Check that the device's interface cable is securely connected to the system board. See "Replacing Drives." |
|
Processor 1 internal error Processor 2 internal error |
Defective microprocessor or system board (reported by the NMI handler).
|
Replace the specified microprocessor. See "Replacing Microprocessors." If the problem still persists, replace the system board. |
|
Processor bus error PCI bus error IMB bus error |
Defective system board (reported by the NMI handler). |
|
|
Processor in socket 1 not installed! |
No microprocessor installed in primary microprocessor socket. |
Install a microprocessor in the primary microprocessor socket. See "Replacing Microprocessors." |
|
Secondary IDE device 0 not found Secondary IDE device 1 not found |
Improperly connected or missing IDE device. |
Check that the device's interface cable is securely connected to the system board. Replace the device. See "Replacing Drives." If the problem persists, replace the system board. |
|
Shutdown failure |
Defective system board. |
|
|
System backplane error |
Improperly attached or missing SCSI backplane. |
Check that the SCSI backplane board is fully seated. See "Replacing the SCSI Backplane." |
|
System halted! Must power down. |
Wrong password entered too many times. |
Reboot the system and enter the correct password. Clear the forgotten password. See "Disabling a Forgotten Password." |
|
System parity error |
Defective expansion card(s) or improperly seated or faulty memory modules (reported by the NMI handler). |
Replace expansion cards one at a time until error is corrected. See "Replacing Expansion Cards." Remove and reseat the memory modules. See "Adding or Installing Memory Modules." If the problem persists, replace the memory modules. If the problem still persists, replace the system board. |
|
Time-of-day clock stopped |
Defective battery or faulty chip (defective system board). |
Replace the system battery. See "Replacing the System Battery." If the problem persists, replace the system board. |
|
Time-of-day not set - please run SETUP program |
Incorrect Time or Date settings or defective system battery. |
Check the Time and Date settings. See "Using the System Setup Program." If the problem persists, replace the system battery. See "Replacing the System Battery." If the problem persists, replace the system board. |
|
Timer chip counter 2 failed |
Defective system board. |
|
|
Unsupported CPU combination |
Microprocessor combination is not supported by system. |
Install a supported microprocessor combination. See "Replacing Microprocessors." |
|
Unsupported CPU stepping detected. |
Microprocessor is not supported by system. |
Install a correct version of the microprocessor in the specified microprocessor socket. See "Replacing Microprocessors." |
|
Utility partition not available |
<F10> key was pressed during POST, but no utility partition exists on the boot hard drive. |
Create a utility partition on the boot hard drive. See "Using the Dell OpenManage Server Assistant CD" in your User's Guide. |
|
Warning: Detected mode change from RAID to SCSI of the embedded RAID subsystem. Warning: Detected missing RAID hardware for the embedded RAID subsystem. Data loss will occur! Press Y to switch mode to SCSI, press any other key to disable both channels. Press Y to confirm the change; press any other key to cancel. |
Type of controller has changed since previous system boot. |
Back up information on the hard drives before changing the type of controller used with the drives. |
|
Warning! Firmware is out-of-date, please update |
Out-of-date firmware. |
Update the system firmware. See "Using the Dell OpenManage Server Assistant CD" in your User's Guide for information on updating the system firmware. |
|
Warning! No microcode update loaded for processor X |
BIOS not up to date. |
Upgrade the BIOS, but do not turn the system off before the upgrade. See "Using the System Setup Program." |
|
Write fault Write fault on selected drive |
Faulty diskette or hard drive. |
Replace the diskette or hard drive. See "Replacing Drives." |
A warning message alerts you to a possible problem and asks you to take corrective action before the system continues a task. For example, before you format a diskette, a message might warn you that you might lose all data on the diskette, as a way to protect against inadvertently erasing or writing over the data. These warning messages usually interrupt the procedure and require you to respond by typing y (yes) or n (no).
|
NOTE: Warning messages are generated by either the application program or the operating system. See your Installation and Troubleshooting Guide and the documentation that accompanied the operating system and application program for more information on warning messages. |
When you run a test group or subtest in the system diagnostics, an error message might result. These particular error messages are not covered in this section. Record the message on a copy of the Diagnostics Checklist (located in "Getting Help" in the Installation and Troubleshooting Guide), and then follow the instructions in that section for obtaining technical assistance.
The optional systems management software generates alert messages for your system. For example, the server agent software generates messages that appear in the SNMP trap log file. Alert messages consist of information, status, warning, and failure messages for drive, temperature, fan, and power conditions. More information about alert messages is provided in the systems management software documentation on the documentation CD that shipped with your system.
When an error that cannot be reported on the monitor occurs during a boot routine, the system may emit a series of beeps that identify the problem. The beep code is a pattern of sounds; for example, one beep followed by a second beep and then a burst of three beeps (code 1-1-3) means that the computer was unable to read the data in NVRAM. This information is valuable if you need to call for technical assistance.
When a beep code is emitted, record it on a copy of the Diagnostics Checklist, and then look it up in Table 2. If you are unable to resolve the problem by looking up the meaning of the beep code, use the system diagnostics to identify a more serious cause.
Table 2. System Beep Codes
| Code | Cause | Corrective Action |
|---|---|---|
| 1-1-2 | CPU register test failure | Replace microprocessor 1. See "Adding or Replacing Microprocessors." If the problem persists, replace microprocessor 2. |
| 1-1-3 | CMOS write/read failure | Replace the system board. |
| 1-1-4 | BIOS checksum failure | Reflash the BIOS firmware. If the problem persists, replace the system board. |
| 1-2-1 | Programmable interval-timer failure | Replace the system board. |
| 1-2-2 1-2-3 1-3-1 |
DMA initialization failure DMA page register write/read failure Main-memory refresh verification failure |
Remove and reseat the memory modules. If the problem persists, replace one or more memory modules. If the problem still persists, replace the system board. |
| 1-3-2 | No memory installed | Remove and reseat the memory modules. If the problem persists, replace the memory modules. If the problem still persists, replace the system board. |
| 1-3-3 1-3-4
2-1-1 |
Chip set or data
line failure in the first 64 KB of main memory Odd/even logic failure in the first 64 KB of main memory Address line failure in the first 64 KB of main memory Parity failure in the first 64 KB of main memory Bit failure in the first 64 KB of main memory |
Remove and reseat the memory modules. If the problem persists, replace the memory modules. If the problem still persists, replace the system board. |
| 3-1-1
3-1-3 3-1-4 |
Slave
DMA-register failure Master DMA-register failure Master interrupt-mask register failure Slave interrupt-mask register failure |
Replace the system board. |
| 3-2-4 | Keyboard-controller test failure | Check the keyboard cable and connector for proper connection. If the problem persists, replace the keyboard. If the problem persists, replace the system board. |
| 3-3-1 | CMOS failure | Replace the system board. |
| 3-3-2 | System configuration check failure | Replace the system board. |
| 3-3-3 | Keyboard controller not detected | Replace the system board. |
| 3-3-4 3-4-2 3-4-3 |
Screen
initialization failure Screen-retrace test failure Search for video ROM failure |
Replace the system board. |
| 4-2-1 4-2-2 |
No timer tick
Shutdown failure |
Replace the system board. |
| 4-2-3 | Gate A20 failure | Replace the system board. |
| 4-2-4 | Unexpected interrupt in protected mode | Ensure that all expansion cards are properly seated, and then reboot the system. |
| 4-3-1 | Improperly seated or faulty memory modules | Remove and reseat the memory modules. If the problem persists, replace the memory modules. If the problem still persists, replace the system board. |
| 4-3-3 | Defective system board | Replace the system board. |
| 4-3-4 | Time-of-day clock stopped | Replace the battery. If the problem persists, replace the system board. |
| 4-4-1 | Super I/O chip failure (defective system board) | Replace the system board. |
| 4-4-4 | Cache test failure (defective microprocessor) | Remove and reseat the specified microprocessor. If the problem still persists, replace the microprocessor. |
The system bezel incorporates a system status indicator divided into blue and amber system status indicators (see Figure 1). The blue indicator lights when the system is operating correctly. The amber caution indicator lights when the system needs attention due to a problem with power, a cooling fan, internal temperature, or a hard drive.
Table 3 lists the system's indicator patterns. Different patterns are displayed as events occur in the system.
Figure 1. Front-Bezel Indicators
 |
|
Table 3. System Status Indicator Patterns
|
Blue Indicator |
Amber Caution Indicator |
Description |
|---|---|---|
|
Off |
Off |
There is no power available to the system, or power is available to the system, but the system is not powered on. |
|
Off |
Blinking |
The system has detected an error. |
|
On |
Off |
Power is on, and the system is operational. |
|
Blinking |
Off |
The indicator has been activated to identify the system in a rack. |
Additional indicators are located behind the bezel. The front-panel blue and amber system status indicator provides the same status information displayed on the bezel. Figure 2 shows the indicators and features of the front-panel, and Table 4 defines the meaning of the indicator patterns displayed.
Figure 2. Front-Panel Features
 |
|
Table 4. Front-Bezel and Front-Panel Indicator Patterns
|
LED Indicator |
Icon |
Description |
|---|---|---|
|
Blue and amber system status indicator |
|
The blue system status indicator lights up during normal system operation. The server management software can also cause the blue system status indicator to flash to identify a particular system. The amber system status indicator flashes when the system needs attention due to a problem with power supplies, fans, system temperature, or hard drives. NOTE: If the system is connected to AC power, the amber system status indicator will flash regardless of whether the system has been powered on. |
|
NIC1 and NIC2 link and activity indicators |
|
The link and activity indicators for the two integrated NICs light when the NICs are in use. |
|
Hard-drive indicator |
|
The green hard-drive activity indicator flashes when the hard drives are in use (see Figure 4 for more information on hard-drive indicators). |
|
Power button |
|
The power button lights when the system power is on. |
|
NOTE: If you turn
off the system using the power button and the system is running an ACPI-compliant
operating system (such as Microsoft® Windows® 2000), the system
performs a graceful shutdown before the power is turned off. If the
system is not running an ACPI-compliant operating system, the power is
turned off immediately after the power button is pressed. |
The front panel also incorporates a USB connector, a video connector, and a PS/2 connector to connect a mouse and keyboard using a Y-cable (see Figure 3).
The following features are on the system's back panel (see Figure 3):
 |
|
The system status indicator connector (13 in Figure 3) is used to extend the blue and amber system status indicator (4 in Figure 3) to the cable-management arm when the system is installed in a rack.
If your system has SCSI hard drives and if the integrated RAID controller is activated, two indicators on each of the hard-drive carriers provide information on the status of the hard drives (see Figure 4). The SCSI backplane firmware controls the drive power-on/fault indicator.
Figure 4. Hard Drive Indicators
 |
|
Table 5 lists the drive indicator patterns. Different patterns are displayed as drive events occur in the system. For example, in the event of a hard-drive failure, the "drive failed" pattern appears. After the drive is selected for removal, the "drive being prepared for removal" pattern appears, followed by the "drive ready for insertion or removal" pattern. After the replacement drive is installed, the "drive being prepared for operation" pattern appears, followed by the "drive online" pattern.
|
NOTE: If the optional
ROMB card is not installed, you will see
only the "drive online" indicator patterns. You will also see the
drive-activity indicator blink when the drive is being accessed. |
Table 5. SCSI Hard-Drive Indicator Patterns
| Condition | Indicator Pattern |
|---|---|
| Identify drive | The green power-on/fault indicator blinks 4 times per second. |
| Drive being prepared for removal | The green power-on/fault indicator blinks 2 times per second. |
| Drive ready for insertion or removal | Both drive indicators are off. |
| Drive being prepared for operation | The green power-on/fault indicator is on. |
| Drive predicted failure | The power-on/fault indicator slowly blinks green, amber, and off. |
| Drive failed | The amber power-on/fault indicator blinks 4 times per second. |
| Drive rebuilding | The green power-on/fault indicator blinks slowly. |
| Drive online | The green power-on/fault indicator is on. |
Your system may have one or two power supplies installed. Your system may require AC input power or it may require –48 VDC input power. A system designed for –48 VDC input power has power subsystem components that are not compatible with a system designed for AC power input.
Each power supply has three indicators that indicate the power on status, fault, and whether the proper input power is present. If two power supplies are installed, the power supplies are hot-pluggable (see Figure 5 and Table 6).
Figure 5. Redundant Power-Supply Features
 |
|
Table 6. Power-Supply Indicator Patterns
| Indicator | Description |
|---|---|
| Power-supply status | Green indicates that the power supply is operational. |
| Power-supply fault | Red indicates a problem with the power supply. |
| Power input line status | Green indicates that a valid source voltage is connected to the system. |
