Dell PowerEdge 850 Systems Installation and Troubleshooting Guide
Baseboard Management Controller Messages
The system, applications, and operating systems can identify problems and alert you to them. Any of the following can indicate when the system is not operating properly:
This section describes each type of message, lists the possible causes, and provides steps to resolve any problems indicated by a message. The system indicators and features are illustrated in this section.
Figure 2-1 shows the controls, indicators, and connectors located behind the optional bezel on the front-panel. (To remove the optional bezel and access the front panel, press the latch at the left end of the bezel. See "Opening the System" in "Troubleshooting Your System" for detailed instructions on removing the bezel.) Table 2-1 describes the front-panel indicators, buttons, and connectors.
Figure 2-1. Front-Panel Features
The optional locking system bezel incorporates blue and amber system status indicators. The blue indicator lights up when the system is operating correctly.
Table 2-1. Front-Panel LED Indicators, Buttons, and Connectors
Feature |
Icon |
Description |
---|---|---|
System status indicator System identification button |
| The blue system status indicator lights up during normal system operation. The amber system status indicator flashes when the system needs attention due to a system problem. You can use the system identification buttons on the front and back panels to locate a particular system within a rack. When one of these buttons is pushed, the blue system status indicators on the front and back panels blink until one of the buttons is pushed again. You can also use the systems management software to cause the indicators to flash to identify a particular system. |
Hard-drive indicator |
| The green hard-drive activity indicator flashes when the SATA hard drives are in use. NOTE: This indicator does not flash when SCSI hard drives are in use. |
NMI button |
| The NMI button is used to troubleshoot software and device driver errors when using certain operating systems. This button can be pressed using the end of a paper clip. Use this button only if directed to do so by qualified support personnel or by the operating system's documentation. |
USB connectors |
| Connect USB 2.0-compliant devices to the system. |
Video connector |
| Connects a monitor to the system.
|
Power-on indicator, Power button |
| The power button turns system power off and on. NOTICE: If you turn off the system using the power button and the system is running an ACPI-compliant operating system, the system can perform an orderly shutdown before power is turned off. If the power button is pressed for more than 4 seconds, the system power will turn off regardless of the current operating system state. If the system is not running an ACPI-compliant operating system, power is turned off immediately after the power button is pressed. The power button is enabled in the System Setup program. When disabled, the button can only turn the system power on. For more information, see "Using the System Setup Program" in your User's Guide. The power-on indicator lights or blinks to indicate the status of power to the system. The power-on indicator lights when the system is on. The indicator is off when the system is off and power is disconnected from the system. The indicator blinks when the system is off but is connected to the power source. |
Diagnostic indicators (4) |
| The diagnostic indicators aid in troubleshooting the system. For more information, see "Diagnostics Indicator Codes." |
Figure 2-2 shows the back-panel features of the system.
Figure 2-2. Back-Panel Features
System messages appear on the screen to notify you of a possible problem with the system. Table 2-3 lists the system messages that can occur and the probable cause and corrective action for each message.
![]() |
NOTE: If you receive a system message that is not listed in Table 2-3, check the documentation for the application that is running when the message appears or the operating system's documentation for an explanation of the message and recommended action. |
Message |
Causes |
Corrective Actions |
---|---|---|
Amount of available memory limited to 256MB | The OS Install Mode option in the System Setup program is set to On. This limits the amount of available memory to 256 MB because some operating systems will not complete installation with more than 2 GB of system memory. | After the operating system is installed, enter the System Setup program and set the OS Install Mode option to Off. See your User's Guide for details. |
Attempting to update Remote Configuration. Please wait.... | Remote Configuration is in progress. | Wait until the process is complete. |
BIOS Update Attempt Failed! | Remote BIOS update attempt failed. | Retry the BIOS update. If the problem persists, see "Getting Help." |
Caution! NVRAM_CLR jumper is installed on system board. | NVRAM_CLR jumper is installed. | Check the System Setup configuration settings. See "Using the System Setup Program" in your User's Guide. Remove the NVRAM_CLR jumper. See Figure A-2 for jumper locations. |
Data error | The diskette drive or hard drive cannot read the data. | For the operating system, run the appropriate utility to check the file structure of the diskette drive or hard drive. See your operating system documentation for information on running these utilities. |
Decreasing available memory | One or more memory modules might be improperly seated or faulty. | Reinstall the memory modules and, if necessary, replace them. See "System Memory" in "Installing System Components." See "Troubleshooting System Memory" in "Troubleshooting Your System." |
Diskette read failure | Faulty or improperly inserted diskette. | Replace the diskette. |
Diskette subsystem reset failed | Faulty diskette drive or optical drive controller. | Ensure that the diskette drive and optical drive cables are properly connected. See "Troubleshooting a USB Device" and "Troubleshooting an Optical Drive" in "Troubleshooting Your System." If the problem persists, see "Getting Help." |
Drive not ready | Diskette missing or improperly inserted in diskette drive. | Reinsert or replace the diskette. |
Error: Incorrect memory configuration. Ensure memory in slots DIMM1_A and DIMM1_B, DIMM2_A and DIMM2_B match identically in size, speed and rank. | The installed memory modules are not matched pairs. | See "Memory Module Installation Guidelines" in "Installing System Components." |
Error: Remote Access Controller initialization failure. | Faulty or improperly installed RAC. | Ensure that the RAC is properly installed. See "Troubleshooting Expansion Cards" in "Troubleshooting Your System." |
Error 8602: Auxiliary device failure. Verify that mouse and keyboard are securely attached to correct connectors. | Loose or improperly connected mouse or keyboard cable; faulty mouse or keyboard. | Replace the mouse. If the problem persists, replace the keyboard. |
Gate A20 failure | Faulty keyboard controller (faulty system board). | See "Getting Help." |
General failure | The operating system is unable to carry out the command. | This message is usually followed by specific information. Take the appropriate action to resolve the problem. |
IDE Primary drive 0 not found | Primary drive 0 set as Auto, no disk. | Run the System Setup program to correct the settings. See "Using the System Setup Program" in your User's Guide. |
Invalid memory configuration detected. Potential for data corruption exists! | Unsupported DIMMs are installed in the system, or the memory configuration is incorrect. | Replace or reconfigure the DIMMs. See "System Memory" in "Installing System Components" for memory configuration guidelines, a list of supported DIMMs, and supported memory configurations. |
Keyboard controller failure | Faulty keyboard controller (faulty system board). | See "Getting Help." |
Keyboard data line failure Keyboard failure Keyboard stuck key failure | Loose or improperly connected keyboard cable; faulty keyboard; faulty keyboard controller. | Ensure that the keyboard is properly connected. If the problem persists, replace the keyboard. If the problem persists, see "Getting Help." |
Keyboard fuse has failed. | Keyboard fuse has failed. | Replace the keyboard. |
Faulty system board. | If the problem persists, the system board is faulty. See "Getting Help." | |
Manufacturing mode detected | System is incorrectly configured. |
|
Memory address line failure at address, read value expecting value Memory double word logic failure at address, read value expecting value Memory odd/even logic failure at start address to end address Memory write/read failure at address, read value expecting value | Faulty or improperly installed memory modules, or faulty system board. | Ensure that all memory modules are properly installed. See "Troubleshooting System Memory" in "Troubleshooting Your System." If the problem persists, see "Getting Help." |
Memory tests terminated by keystroke | The spacebar was pressed during POST to terminate the memory test. | Information only. |
No boot device available | The system cannot find the diskette or hard drive. | If the diskette drive is your boot device, ensure that a bootable disk is in the drive. If the hard drive is your boot device, ensure that the hard drive is installed, properly seated, and partitioned as a boot device. Enter the System Setup program and verify the boot sequence information. See your User's Guide for details. |
No boot sector on hard-disk drive | The system configuration information in the System Setup program might be incorrect. | Enter the System Setup program and verify the system configuration information for the hard drive. See your User's Guide for details. If the message continues to appear after verifying the information in the System Setup program, the operating system might have been corrupted. Reinstall the operating system. See your operating system documentation for reinstallation information. |
No timer tick interrupt | A chip on the system board might be malfunctioning. | Run the system diagnostics. See "Running the System Diagnostics." |
Not a boot diskette | The operating system is trying to boot from a diskette that does not have a bootable operating system installed on it. | Insert a diskette that has a bootable operating system. |
PCI BIOS failed to install | PCI device BIOS (Option ROM) checksum failure is detected during shadowing. | Ensure that all appropriate cables are securely connected to the expansion cards. If the problem persists, see "Troubleshooting Expansion Cards" in "Troubleshooting Your System." |
PCIe Degraded Link Width Error: Embedded Bus#nn/Dev#nn/Funcn Expected Link Width is n Actual Link Width is n | Faulty or improperly installed PCIe card. | Reseat the PCIe cards. See "Expansion Cards" in "Installing System Components." If the problem persists, see "Getting Help." |
PCIe Degraded Link Width Error: Slot n Expected Link Width is n Actual Link Width is n | Faulty or improperly installed PCIe card in the specified slot number. | Reseat the PCIe card in the specified slot number. See "Expansion Cards" in "Installing System Components." If the problem persists, see "Getting Help." |
PCIe Training Error: Embedded Bus#nn/Dev#nn/Funcn | Faulty or improperly installed PCIe card. | Reseat the PCIe cards. See "Expansion Cards" in "Installing System Components." If the problem persists, see "Getting Help." |
PCIe Training Error: Slot n | Faulty or improperly installed PCIe card in the specified slot number. | Reseat the PCIe card in the specified slot number. See "Expansion Cards" in "Installing System Components." If the problem persists, see "Getting Help." |
Plug & Play Configuration Error | Error encountered in initializing PCI device; faulty system board. | Install the NVRAM_CLR jumper and reboot the system. See Figure A-2 for jumper location. Check for a BIOS update. If the problem persists, see "Troubleshooting Expansion Cards" in "Troubleshooting Your System." If the problem persists, see "Getting Help." |
Primary drive 0/1 configuration error | Faulty drive. Parameters failure. | Ensure that the hard drive cables are properly connected. See "Troubleshooting SCSI Hard Drives" in "Troubleshooting Your System." |
Primary drive 0/1 failure | Faulty drive. INT13 call failure from the drive. | Ensure that the hard drive cables are properly connected. See "Troubleshooting SCSI Hard Drives" in "Troubleshooting Your System." |
Read fault Requested sector not found | The operating system cannot read from the diskette or hard drive, the system could not find a particular sector on the disk, or the requested sector is defective. | Replace the diskette. Ensure that the diskette and hard-drive cables are properly connected. See "Troubleshooting a USB Device," "Troubleshooting SATA Hard Drives," or "Troubleshooting SCSI Hard Drives" in "Troubleshooting Your System" for the appropriate drive(s) installed in your system. |
Remote Configuration update attempt failed | System could not implement Remote Configuration request. | Retry Remote Configuration. |
ROM bad checksum = address | Faulty or improperly installed expansion card. | Remove and reseat the expansion cards. See "Troubleshooting Expansion Cards" in "Troubleshooting Your System." |
SATA port 0/1 hard disk drive configuration error | Faulty drive. Parameters failure. | Ensure that the hard drive cables are properly connected. See "Troubleshooting SATA Hard Drives" in "Troubleshooting Your System." |
SATA port 0/1 hard disk drive failure SATA port 0/1 hard disk drive auto-sensing error | Faulty drive. INT13 call failure from the drive. | Ensure that the hard drive cables are properly connected. See "Troubleshooting SATA Hard Drives" in "Troubleshooting Your System." |
SATA Port 0/1 hard disk not found | SATA Port0/1 set as Auto, no disk installed. | Run the System Setup program to correct the settings. See "Using the System Setup Program" in your User's Guide. |
Sector not found Seek error Seek operation failed | Faulty diskette or hard drive. | See "Troubleshooting a USB Device," "Troubleshooting SATA Hard Drives," or "Troubleshooting SCSI Hard Drives" in "Troubleshooting Your System" for the appropriate drive installed in your system. |
Shutdown failure | Shutdown test failure. | Ensure that all memory modules are properly installed. See "Troubleshooting System Memory" in "Troubleshooting Your System." If the problem persists, see "Getting Help." |
The amount of system memory has changed. | Faulty memory module. | See "Troubleshooting System Memory" in "Troubleshooting Your System." If the problem persists, see "Getting Help." |
The amount of tested memory is below the minimum system configuration. System halted! | Invalid memory configuration. | See "Memory Module Installation Guidelines" in "Installing System Components." |
| Faulty memory module. | See "Troubleshooting System Memory" in "Troubleshooting Your System." If the problem persists, see "Getting Help." |
Time-of-day clock stopped | Faulty battery; faulty system board. | See "Troubleshooting the System Battery" in "Troubleshooting Your System." If the problem persists, see "Getting Help." |
Time-of-day not set - please run SETUP program | Incorrect Time or Date settings; faulty system battery. | Check the Time and Date settings. See "Using the System Setup Program" in your User's Guide. If the problem persists, see "Troubleshooting the System Battery" in "Troubleshooting Your System." |
Timer chip counter 2 failed | Faulty system board. | See "Getting Help." |
Unexpected interrupt in protected mode | Faulty or improperly installed memory modules or faulty system board. | Ensure that all memory modules are properly installed. See "Memory Module Installation Guidelines" in "Installing System Components." If the problem persists, see "Troubleshooting System Memory" in "Troubleshooting Your System." If the problem persists, see "Getting Help." |
Utility partition not available | Utility partition is not available on the hard disk | Create a utility partition on the boot hard drive. See the CDs that came with your system. |
Warning! No micro code update loaded for processor 0 | Micro code update failed. | Update the BIOS firmware. See "Getting Help." |
Write fault Write fault on selected drive | Faulty diskette, diskette drive, hard drive. | Replace the diskette. Ensure that the diskette drive and hard-drive cables are properly connected. See "Troubleshooting a USB Device," "Troubleshooting SATA Hard Drives," or "Troubleshooting SCSI Hard Drives" in "Troubleshooting Your System" for the appropriate drive(s) installed in your system. |
The four diagnostics indicators on the system front panel display error codes during system startup. Table 2-4 lists the causes and possible corrective actions associated with these codes.
Table 2-4. Diagnostic Indicator Codes
Code |
Causes |
Corrective Action |
---|---|---|
|
Possible processor failure. |
See "Troubleshooting the Microprocessor" in "Troubleshooting Your System." |
|
Memory failure. |
See "Troubleshooting System Memory" in "Troubleshooting Your System." |
|
Possible expansion card failure.
|
See "Troubleshooting Expansion Cards" in "Troubleshooting Your System." |
|
Possible video card failure. |
See "Troubleshooting Expansion Cards" in "Troubleshooting Your System." |
|
Diskette drive or hard drive failure. |
Ensure that the diskette drive and hard-drive are properly connected. See "Installing Drives" for information on the drives installed in your system. |
|
Possible USB failure. |
See "Troubleshooting a USB Device" in "Troubleshooting Your System."
|
|
No memory modules detected. |
See "Troubleshooting System Memory" in "Troubleshooting Your System."
|
|
System board failure. |
See "Getting Help."
|
|
Memory configuration error. |
See "Troubleshooting System Memory" in "Troubleshooting Your System."
|
|
Possible system board resource and/or system board hardware failure. |
See "Troubleshooting IRQ Assignment Conflicts" in "Troubleshooting Your System." If the problem persists, see "Getting Help."
|
|
Possible expansion card failure. |
See "Troubleshooting Expansion Cards" in "Troubleshooting Your System." |
|
Other failure. |
Ensure that the diskette drive, optical drive, and hard drives are properly connected. See "Troubleshooting Your System" for the appropriate drive installed in your system. If the problem persists, see "Getting Help." |
|
The system is in a normal operating condition after POST. |
Information only. |
If an error that cannot be reported on the screen occurs during POST, the system may emit a series of beeps that identifies the problem.
![]() |
NOTE: If the system boots without a keyboard, mouse, or monitor attached, the system does not issue beep codes related to those peripherals. |
If a beep code is emitted, write down the series of beeps and then look it up in Table 2-5. If you are unable to resolve the problem by looking up the meaning of the beep code, use system diagnostics to identify the possible cause. If you are still unable to resolve the problem, see "Getting Help."
Code |
Cause |
Corrective Action |
---|---|---|
1-1-2 | CPU register test failure | See "Troubleshooting the Microprocessor" in "Troubleshooting Your System." |
1-1-3 | CMOS write/read failure; faulty system board | Faulty system board. See "Getting Help." |
1-1-4 | BIOS error | Reflash the BIOS. |
1-2-1 | Programmable interval-timer failure; faulty system board | Faulty system board. See "Getting Help." |
1-2-2 | DMA initialization failure | See "Troubleshooting System Memory" in "Troubleshooting Your System." |
1-2-3 | DMA page register write/read failure | |
1-3-1 | Main-memory refresh verification failure | |
1-3-2 | No memory installed | |
1-3-3 | Chip or data line failure in the first 64 KB of main memory | |
1-3-4 | Odd/even logic failure in the first 64 KB of main memory | |
1-4-1 | Address line failure in the first 64 KB of main memory | |
1-4-2 | Parity failure in the first 64 KB of main memory | |
1-4-3 | Fail-safe timer test failure | |
1-4-4 | Software NMI port test failure | |
2-1-1 through | Bit failure in the first 64 KB of main memory | |
3-1-1 | Slave DMA-register failure | Faulty system board. See "Getting Help." |
3-1-2 | Master DMA-register failure | |
3-1-3 | Master interrupt-mask register failure | |
3-1-4 | Slave interrupt-mask register failure | |
3-2-2 | Interrupt vector loading failure | |
3-2-4 | Keyboard-controller test failure | |
3-3-1 | CMOS failure | |
3-3-2 | System configuration check failure | |
3-3-3 | Keyboard controller not detected | |
3-3-4 | Video memory test failure | |
3-4-1 | Screen initialization failure | |
3-4-2 | Screen-retrace test failure | |
3-4-3 | Video ROM search failure | |
4-2-1 | No timer tick | Faulty system board. See "Getting Help."
|
4-2-2 | Shutdown test failure | |
4-2-3 | Gate A20 failure | |
4-2-4 | Unexpected interrupt in protected mode | See "Troubleshooting Expansion Cards" in "Troubleshooting Your System." |
4-3-1 | Improperly installed or faulty memory modules | See "Troubleshooting System Memory" in "Troubleshooting Your System." |
4-3-2 | No memory modules installed in the first memory module connector | Install a memory module in the first memory module connector. See "System Memory" in "Installing System Components." |
4-3-3 | Faulty system board | Faulty system board. See "Getting Help." |
4-3-4 | Time-of-day clock stopped | See "Troubleshooting System Memory" in "Troubleshooting Your System." If the problem persists, see "Getting Help." |
4-4-1 | Super I/O chip failure; faulty system board | Faulty system board. See "Getting Help." |
4-4-4 | Cache test failure; faulty processor | See "Troubleshooting the Microprocessor" in "Troubleshooting Your System." |
A warning message alerts you to a possible problem and prompts you to respond before the system continues a task. For example, before you format a diskette, a message will warn you that you may lose all data on the diskette. Warning messages usually interrupt the task and require you to respond by typing y (yes) or n (no).
![]() |
NOTE: Warning messages are generated by either the application or the operating system. For more information, see the documentation that accompanied the operating system or application. |
When you run system diagnostics, an error message may result. Diagnostic error messages are not covered in this section. Record the message on a copy of the Diagnostics Checklist in "Getting Help," and then follow the instructions in that section for obtaining technical assistance.
Systems management software generates alert messages for your system. Alert messages include information, status, warning, and failure messages for drive, temperature, fan, and power conditions. For more information, see the systems management software documentation.
The Baseboard Management Controller (BMC) enables you to configure, monitor, and recover systems remotely. BMC uses the system's serial port and integrated NIC1 to support fault logging and SNMP alerting.
![]() |
NOTE: If the integrated network controller is used in an Ether Channel team or link aggregation team, the BMC management traffic will not function properly. For more information about network teaming, see the documentation for the network controller. |
For additional information on using BMC, see the documentation for the BMC and systems management applications.