Diagnostic Test Programs. IBM Netfinity 5000 Server, 5000, Netfinity 5000, 5000 Netfinity 5000 Server

Diagnostic Test Programs

POST Error Messages and Beep Codes

POST error messages and beep codes occur during startup when POST finds a problem with the hardware or detects a change in the hardware configuration. For more information, see pages 122 through 124.

Diagnostic Error Messages

Diagnostic error messages occur when a test finds a problem with the server hardware. These error messages are alphanumeric and they are saved in the Test

Log. For more information, see pages 125 through 134.

Software-Generated Error Messages

These messages occur if a problem or conflict is found by an application program, the operating system, or both. Messages are generally text messages, but they also can be numeric. For information about these error messages, refer to the documentation that comes with your software.

Troubleshooting Charts

The charts under “Troubleshooting Charts” on page 143 list symptoms of problems

(for example, a symptom might be “The mouse is not working.”), along with steps to correct the problems.

Option Diskettes

An optional device or adapter might come with an Option Diskette. Option

Diskettes usually contain option-specific diagnostic test programs or configuration files.

If your optional device or adapter comes with an Option Diskette, follow the instructions that come with the option. Different instructions apply depending on whether the Option Diskette is startable or not.

Diagnostic Test Programs

This section includes useful information about navigating through the diagnostic test programs, as well as procedures for starting and stopping them. These programs are designed to test the IBM Netfinity 5000 server. If you want to test a non-IBM product, refer to the information that comes with that product.

You can start the diagnostic test programs from the Startup panel, when the message Press F2 for Diagnostics appears.

Note: When you run the diagnostic test programs, a single problem can cause several error messages to occur. When this happens, work to correct the cause of the first error message. After the cause is corrected, the other error messages probably will not occur the next time you run the tests.

Chapter 6. Solving Problems

111

Diagnostic Test Programs

Navigating Through the Diagnostic Tests

Error messages in the Test Log are stored by diagnostic test session. A diagnostic test session is defined as running one, all, or a selection of tests, one or more times. You can use the following keys to maneuver within the test program:

Enter

Down Arrow (

↓

)

Up Arrow (

↑

)

Left Arrow ( ← )

Right Arrow ( → )

Selects an item.

Moves the cursor down.

Moves the cursor up.

Toggles test selection between Yes and No.

Toggles test selection between Yes and No.

Page Down (PgDn) Moves to the next diagnostic test session in the log (if any).

Page Up (PgUp)

F1

Moves to the previous diagnostic test session in the log (if any).

Displays the appropriate Help information. Use the Up Arrow

(

↑

) or Down Arrow (

↓

) key to scroll through the information.

Pressing F1 from within a Help screen provides a help index from which you can select different categories. Pressing Esc exits Help and returns to where you left off.

Esc Returns to the previous menu.

Running Diagnostic Test Programs

When you start the diagnostic test programs from the Diagnostic Utility menu, you can select the tests, the way the tests run, and the number of times the tests run.

Notes:

1. To run the diagnostic test programs, you must start the server with the highest level password.

That is, if you enter the power-on password, and an administrator password is set, you cannot run the test programs. You can only view the error messages in the test log.

If an administrator password is set, you must enter the administrator password to run the diagnostic test programs.

2. If the server stops during testing and you cannot continue, restart the server and try running the tests again. If the problem persists, have the system serviced.

3. If the diagnostic tests do not find a problem, see “Troubleshooting” on page 143 and look for the problem symptom.

4. You might have to install a wrap connector on your active parallel, serial, or

Ethernet port to obtain accurate test results for these ports. If you do not have a wrap connector, contact your IBM reseller or IBM marketing representative.

5. You might need a scratch diskette to obtain accurate test results when testing the diskette drive.

6. The keyboard and mouse tests assume that a keyboard and mouse are attached to the server.

112

Netfinity 5000 Server Hardware Information and Procedures

Diagnostic Test Programs

To start the diagnostic tests:

1. Turn on the server and watch the screen.

If the system is turned on already, shut down your operating system and restart the server.

2. When the message Press F2 for Diagnostics appears, press F2.

If a power-on password or administrator password is set, the system prompts you for it. Type in the appropriate password; then, press Enter.

3. The Diagnostic Programs screen appears.

4. Select Extended or Basic from the top of the screen.

5. Select the test you want to run from the list that appears; then, follow the instructions that appear on the screen. The actions available include specifying the options for the tests to be run, such as the number of times to run the test, whether to stop on error, or whether to use a predefined overlay that describes the tests to be run.

When the tests have completed, you can view the Test Log by selecting Utility from the top of the screen.

Also, you can view server configuration information (such as system configuration, memory contents, interrupt request (IRQ) use, direct memory access (DMA) use, device drivers, and so on) by selecting Hardware Info from the top of the screen.

If the hardware checks out OK but the problem persists during normal server operations, a software error might be the cause. If you suspect a software problem, refer to the information that comes with the software package.

Viewing the Test Log

If you are already running the diagnostic programs, continue with step 4 in this procedure.

To view the Test Log:

1. Turn on the server and watch the screen.

If the system is turned on already, shut down your operating system and restart the server.

2. When the message Press F2 for Diagnostics appears, press F2.

If a power-on password or administrator password is set, the system prompts you for it. Type in the appropriate password; then, press Enter.

3. The Diagnostic Programs screen appears.

4. Select Utility from the top of the screen.

5. Select View Test Log from the list that appears; then, follow instructions on the screen.

6. Press Esc to return to the Diagnostic Programs screen.

7. Select Quit from the top of the screen; then, select Exit Diags to exit from the diagnostic programs. The server restarts.

Chapter 6. Solving Problems

113

POST Messages

Power-on Self Test (POST) Messages

The following table shows error messages that can appear on the screen during the power-on self-test (POST).

Notes:

1. The actions for some of the messages require you to run the

Configuration/Setup Utility. For information about using these programs, see

“Using the Configuration/Setup Utility” on page 22.

2. If a password prompt appears with a POST message, type the administrator or power-on password; then, press Enter.

POST Message Table

POST Message

062

101

102

106

114

129

151

Description

The Netfinity 5000 server failed to boot on three consecutive attempts.

All caches are disabled. This can be caused by repeatedly turning the Netfinity

5000 server on and then off or resetting the Netfinity 5000 server.

Action: Start the Configuration/Setup Utility program and verify that all settings are correct. (See “The Configuration/Setup Utility.”) Use the Cache Control selection in the Advanced Setup menu of the Configuration/Setup Utility program to enable the caches. (See “Advanced Setup” on page 28.)

If the problem persists, have the system serviced. When the problem is corrected, make sure to enable the caches.

An error occurred during the system board and microprocessor test.

Action: Have the system serviced.

An error occurred during the system board and microprocessor test.

Action: Have the system serviced.

An adapter read-only memory (ROM) error occurred.

Action: Remove the options. If you can start the server without the options installed, reinstall each option one at a time and retest after each is reinstalled.

When an option fails, replace it.

If you cannot isolate and correct the problem, have the system serviced.

An error was detected in the L1 cache of one of the microprocessors.

Action:

1. If you just installed a microprocessor, verify that the microprocessor is installed and seated correctly.

2. If the problem persists, check to see if the system has isolated the problem to a microprocessor:

Ÿ If the System Error LED on the information LED panel is on, check to see if any Microprocessor Error LEDs on the system board are on (see “System

Board LEDs” on page 168).

– If a Microprocessor LED is on, run the diagnostic program for the microprocessor indicated by the LED (if the secondary microprocessor error LED is on, run the Alt. CPU diagnostic program). If the tests fail, replace the microprocessor.

– If the microprocessor tests do not fail, have the system serviced.

Ÿ If no error LED is on, the error logs in the Configuration/Setup Utility program might provide additional information on the microprocessor error.

If the problem persists, have the system serviced.

A real-time clock (RTC) error occurred.

Action: Have the system serviced.

114

Netfinity 5000 Server Hardware Information and Procedures

POST Messages

POST Message

161

162

163

164

175

Description

The real-time clock battery has failed.

Action: Have the system serviced or replace the battery yourself. For additional information, see “Replacing the Battery” on page 159 and “Lithium Battery Notice” on page ix before you attempt to change the battery.

You can use the server until you replace the battery. However, you must run the

Configuration/Setup utility programs and set the time and date and other custom settings each time you turn on the server.

A change in device configuration occurred. This error occurs under one or more of the following conditions:

Ÿ A new device has been installed.

Ÿ A device has been moved to a different location or cable connection.

Ÿ A device has been removed or disconnected from a cable.

Ÿ A device is failing and is no longer recognized by the server as being installed.

Ÿ An external device is not turned on.

Ÿ An invalid checksum is detected in the battery-backed memory.

Action: Verify that all external devices are turned on. You must turn on external devices before turning on the server.

If you did not add, remove, or change the location of a device, a device is probably failing. Running the diagnostic test programs might isolate the failing device, but you must have the system serviced.

The time of day has not been set.

Action: Set the correct date and time. If the date and time are set correctly and saved, but the 163 error message reappears, have the system serviced.

The server can be used until the system is serviced, but any application programs that use the date and time will be affected.

A change in the memory configuration occurred. This message might appear after you add or remove memory.

Note: The server can be used with decreased memory capacity.

Action:

1. If POST error message 289 also occurred, follow the instructions for that error message first.

2. If you have installed or removed memory, run the Configuration/Setup Utility program; then, exit, saving the new configuration settings. For information about using the Configuration/Setup utility programs, see “Using the

Configuration/Setup Utility” on page 22.

If the message appears again, shut down the Netfinity 5000 server, reseat the memory modules, and restart the Netfinity 5000 server.

3. If the problem persists, check to see if the system has isolated the problem to a memory module:

Ÿ If the System Error LED on the information LED panel is on, check the

DIMM Error LEDS next to the memory sockets on the system board (see

“System Board LEDs” on page 168). If a DIMM Error LED is on, run the diagnostic program for the memory.

– If the tests fail, replace the DIMM. If the problem persists after you replace the DIMM, have the system serviced.

– If the memory tests do not fail, have the system serviced.

Ÿ If no error LED is on, the error logs in the Configuration/Setup Utility program might provide additional information on the memory error.

If the problem persists, have the system serviced.

A vital product data (VPD) error occurred.

Action: Have the system serviced.

Chapter 6. Solving Problems

115

POST Messages

POST Message

176

177

178

184

185

186

187

188

189

201

Description

A security hardware error occurred.

Action: Check for indications that someone has tampered with the server. If no one has tampered with the server, have the system serviced.

The power-on password information stored in your server has been removed.

Action: From the Configuration/Setup Utility program main menu, select System

Security. Then, follow the instructions on the screen. For information about using the Configuration/Setup utility programs, see “Using the Configuration/Setup Utility” on page 22.

If this information cannot be restored, have the system serviced.

A power failure damaged the stored information about the drive-startup sequence.

Action: From the Configuration/Setup Utility program main menu, select Start

Options; then, follow the instructions on the screen. For information about using the Configuration/Setup utility programs, see “Using the Configuration/Setup Utility” on page 22.

If this information cannot be restored, have the system serviced.

A system board or hardware error occurred.

Action: Have the system serviced.

The VPD serial number is not set.

Action: The system serial number is set in the VPD EEPROM at the time of manufacturing. If the system board has been replaced, the system serial number will be invalid and should be set. From the main menu of the Configuration/Setup

Utility program, select System Information, then select Product Data. If the problem persists, have the system serviced.

A vital product data (VPD) error occurred.

Action: Have the system serviced.

An attempt has been made to access the server with invalid passwords. After three incorrect attempts, the server locks up; that is, the logon data fields are no longer available to the user.

An error occurred during the memory controller test. This error can be caused by:

Ÿ Incorrectly installed memory

Ÿ A failing memory module

Ÿ A processor-board problem

Ÿ A system board problem

Action:

1. If you just installed memory, see “Installing or Removing Memory Modules” on page 54 to verify that the new memory is correct for your server. Verify that the memory modules are installed and seated correctly.

2. If the problem persists, check to see if the system has isolated the problem to a memory module:

Ÿ If the System Error LED on the information LED panel is on, check the

DIMM Error LEDS next to the memory sockets on the system board (see

“System Board LEDs” on page 168). If a DIMM Error LED is on, run the diagnostic program for the memory.

Ÿ If the tests fail, replace the DIMM. If the problem persists after you replace the DIMM, have the system serviced.

Ÿ If the memory tests do not fail, have the system serviced.

3. If no error LED is on, the error logs in the Configuration/Setup Utility program might provide additional information on the memory error.

If the problem persists, have the system serviced.

116

Netfinity 5000 Server Hardware Information and Procedures

POST Messages

POST Message

229

289

301

303

604

662

Description

An error was detected in the L2 cache of one of the microprocessors.

Action:

1. If you just installed a microprocessor, verify that the microprocessor is installed and seated correctly.

2. If the problem persists, check to see if the system has isolated the problem to a microprocessor:

Ÿ If the System Error LED on the information LED panel is on, check the

Microprocessor Error LEDs next to the microprocessor sockets on the system board (see “System Board LEDs” on page 168).

– If a Microprocessor LED is on, run the diagnostic program for the microprocessor indicated by the LED. If the tests fail, replace the microprocessor.

– If the microprocessor tests do not fail, have the system serviced.

Ÿ If no error LED is on, the error logs in the Configuration/Setup Utility program might provide additional information on the microprocessor error.

If the problem persists, have the system serviced.

An error occurred during POST memory tests and a failing DIMM was disabled.

Note: The Netfinity 5000 server can be used with decreased memory.

Action:

1. If you just installed memory, see “Installing or Removing Memory Modules” on page 54 to verify that the new memory is correct for your server. Verify that the memory modules are installed and seated correctly. Start the

Configuration/Setup Utility program (see “The Configuration/Setup Utility” on page 21). In the Advanced Setup menu, select Memory Settings and enable the DIMM. (See “Advanced Setup” on page 28.)

2. If the problem persists, try the DIMM in a different memory socket. If the error occurs in the new location, the DIMM is faulty; replace the failing DIMM.

Otherwise, have the system serviced.

An error occurred during the keyboard and keyboard controller test. These error messages also might be accompanied by continuous beeping.

Action: Ensure that:

1. Nothing is resting on the keyboard and pressing a key.

2. No key is stuck.

3. The keyboard cable is connected correctly to the keyboard and to the correct connector on the server.

Running the diagnostic tests can isolate the server component that failed, but you must have your system serviced. If the error message remains, have the keyboard, cable, and system serviced.

Note: If you have just connected a new mouse or other pointing device, turn off the server and disconnect that device. Wait at least five seconds, and then, turn on the server. If the error message goes away, replace the device.

An error occurred during a diskette drive test.

Action:

1. Verify that the Configuration/Setup utility programs correctly reflect the type of diskette drive that you have installed.

2. Run the diagnostic tests. If the diagnostic tests fail, have the system serviced.

A diskette drive configuration error occurred.

Action: If you removed a diskette drive, make sure that the diskette drive setting is correct in the Configuration/Setup utility programs. If the setting is not correct, change it. For information about using the Configuration/Setup utility programs, see

“Using the Configuration/Setup Utility” on page 22.

If the problem persists, have the system serviced.

Chapter 6. Solving Problems

117

POST Messages

POST Message

962

11 xx

1162

1600

1601

1800

Description

A parallel port configuration error occurred.

Action: If you changed a hardware option, make sure that the parallel port setting is correct in the Configuration/Setup utility programs. If the setting is not correct, change it. For information about using the Configuration/Setup utility programs, see

“Using the Configuration/Setup Utility” on page 22.

If the problem persists, have the system serviced.

An error occurred during the system-board serial port test.

Action: If you have a modem, serial printer, or other serial device attached to your server, verify that the serial cable is connected correctly. If it is, use the following procedure:

1. Turn off the server.

2. Disconnect the serial cable from the serial port.

3. Wait five seconds; then, turn on the server.

If the POST error message does not reappear, either the serial cable or the device is probably failing. See the documentation that comes with the serial device for additional testing information.

If the POST error message reappears, have the system serviced.

The serial port configuration conflicts with another device in the system.

Action:

1. Make sure the IRQ and I/O port assignments needed by the serial port are available. (See “The Configuration/Setup Utility” on page 21.)

2. If all interrupts are being used by adapters, you might need to remove an adapter to make an interrupt available to the PCI adapter, or force other adapters to share an interrupt. For information about removing adapters, see

“Installing or Removing Adapters” on page 50. For information about setting interrupts, see “The Configuration/Setup Utility.”

POST is unable to communicate with the system-management processor.

Action:

1. If the Service Processor Error LED (CR49) on the system board is on, have your system serviced. (See “System Board LEDs” on page 168 for the location of the LED.)

2. If the Service Processor Error LED is not on, disconnect the Netfinity 5000 server from all electrical sources, wait for 30 seconds, reconnect the Netfinity

5000 server to the electrical sources, and restart the Netfinity 5000 server.

If the problem persists, have the system serviced.

The Advanced System Management controller BIOS needs to be updated.

Action:

1. Disconnect the server from all electrical sources, wait for 30 seconds, reconnect the server to the electrical sources, and restart the server.

2. If the problem persists, update the Advanced System Management controller

BIOS. Refer to the “Getting Help Information” section of this Server Library for information about obtaining updates.

A PCI adapter has requested a hardware interrupt that is not available.

Action:

1. Make sure that the PCI adapter and all other adapters are set correctly in the

Configuration/Setup utility programs. If the interrupt resource settings are not correct, change the settings. See “PCI Bus Control” on page 29.

2. If all interrupts are being used by other adapters, you might need to remove an adapter to make an interrupt available to the PCI adapter, or force other adapters to share an interrupt. For information about removing adapters, see

“Installing or Removing Adapters” on page 50. For information about setting interrupts, see see “PCI Bus Control” on page 29.

118

Netfinity 5000 Server Hardware Information and Procedures

POST Messages

POST Message

1801

1802

1803

1804

1805

1806

Description

A PCI adapter has requested memory resources that are not available.

Action:

1. Make sure that the PCI adapter and all other adapters are set correctly in the

Configuration/Setup utility programs. If the memory resource settings are not correct, change the settings. For information about using the

Configuration/Setup utility programs, see “Using the Configuration/Setup Utility” on page 22.

2. If all memory resources are being used, you might need to remove an adapter to make memory available to the PCI adapter. For information about removing adapters, see “Installing or Removing Adapters” on page 50. Disabling the adapter BIOS on the adapter might correct the error. Refer to the documentation provided with the adapter.

A PCI adapter has requested an I/O address that is not available, or the PCI adapter might be defective.

Action:

1. Make sure that the I/O address for the PCI adapter and all other adapters are set correctly in the Configuration/Setup utility programs. For information about using the Configuration/Setup utility programs, see “Using the

Configuration/Setup Utility” on page 22.

2. If the I/O port resource settings are correct, the PCI adapter might be defective.

Have the system serviced.

A PCI adapter has requested a memory address that is not available, or the PCI adapter might be defective.

Action:

1. Make sure that the memory address for all other adapters are set correctly in the Configuration/Setup utility programs. If the memory resource settings are not correct, change the settings. For information about using the

Configuration/Setup utility programs, see “Using the Configuration/Setup Utility” on page 22.

2. If the memory resource settings are correct, the PCI adapter might be defective.

Have the system serviced.

A PCI adapter has requested a memory address that is not available.

Action: If all memory addresses are being used, you might need to remove an adapter to make memory address space available to the PCI adapter. For information about removing adapters, see “Installing or Removing Adapters” on page 50. Disabling the adapter BIOS on the adapter might correct the error. Refer to the documentation provided with the adapter.

A PCI adapter ROM error occurred.

Action: Remove the PCI adapters. If you can start the server without the adapters, reinstall each adapter one at a time and retest after each is reinstalled.

When an adapter fails, replace it.

If you cannot isolate and correct the problem, have the system serviced.

A PCI-to-PCI bridge error occurred. More than one PCI bus tried to access memory below 1 MB.

Action: Remove the PCI adapter that has the PCI bridge. If you can start the server without the adapter, reinstall and retest the adapter. If the adapter fails, replace it.

If you cannot isolate and correct the problem, have the system serviced.

Chapter 6. Solving Problems

119

POST Messages

POST Message

1962

2400

2462

5962

8603

Description

No valid startup devices were found. The system cannot find the startup drive or operating system.

Action: Be sure that the drive you want to start from is in the startup sequence.

1. Select Start Options from the Configuration/Setup utility program main menu.

If you are unable to set the startup sequence, have the system serviced.

2. Check the list of startup devices in the Startup device data fields. Is the drive you want to start from in the startup sequence?

Yes Exit from this screen; then select Exit Setup to exit the

Configuration/Setup menu. Go to step 3.

No Follow the instructions on the screen to add the drive; then save the changes and exit the Configuration/Setup menu. Restart the server.

3. Is an operating system installed?

Yes Turn off the server. Go to step 4.

No Install the operating system in your server; follow your operating system instructions to shut down and restart the Netfinity 5000 server.

4. During server startup, watch for messages indicating a hardware problem.

If the same error message appears, have the system serviced.

An error occurred during the video controller (on the system board) test. This error can be caused by a failing monitor, a failing system board, or, if a video adapter is installed, a failing video adapter.

Action: Verify that the monitor is connected correctly to the video connector. If the monitor is connected correctly, have the system serviced.

A video memory configuration error occurred.

Action:

1. Make sure that the monitor cables are correctly and securely connected to the server.

2. If the problem persists, have the system serviced.

An IDE CD-ROM configuration error occurred.

Action: Check the signal and power cable connections to the CD-ROM drive. See

“System Board Connectors” on page 169 for the locations of the cable connectors on the system board.

If the problem persists, have the system serviced.

An error occurred during the mouse (pointing device) and mouse (pointing device) controller test. This error can be caused by the addition or removal of a mouse, or by a failing system board.

Note: This error also can occur if electrical power was lost for a very brief period and then restored. In this case, turn off the server for at least 5 seconds, and then, turn it back on.

Action: Ensure that the keyboard and mouse (pointing device) are attached to the correct connectors. If they are connected correctly, use the following procedure:

1. Turn off the server.

2. Disconnect the mouse from the server.

3. Turn on the server.

If the POST error message does not reappear, the mouse is probably failing. See the documentation that comes with the mouse for additional testing information. If the problem remains, have the mouse (pointing device) serviced.

If the POST error message reappears, run the diagnostic tests to isolate the problem. If the diagnostic tests do not find a problem and the POST error message remains, have the system serviced.

120

Netfinity 5000 Server Hardware Information and Procedures

POST Messages

POST Message

00019501

00019502

00019701

00019702

01298001

01298002

01298101

01298102

I

I

9990301

9990305

I9990650

Other Numbers

Description

Processor 1 is not functioning.

Action: Replace the primary microprocessor. (The Primary Microprocessor Error

LED on the system board will be on. See “System Board LEDs” on page 168 for the location of the LED.)

If the problem persists, have the system serviced.

Processor 2 is not functioning.

Action: Replace the secondary microprocessor. (The Secondary Microprocessor

Error LED on the system board will be on. See “System Board LEDs” on page 168 for the location of the LED.)

If the problem persists, have the system serviced.

Processor 1 failed the built-in self test.

Action: Replace the primary microprocessor. (The Primary Microprocessor Error

LED on the system board will be on. See “System Board LEDs” on page 168 for the location of the LED.)

If the problem persists, have the system serviced.

Processor 2 failed the built-in self-test.

Action: Replace the secondary microprocessor. (The Secondary Microprocessor

Error LED on the system board will be on. See “System Board LEDs” on page 168 for the location of the LED.)

If the problem persists, have the system serviced.

No update data for the processor 1 (the primary microprocessor).

Action: Update the system BIOS to a level that supports the microprocessors installed in the server. See the “Getting Help Information” section of this Server

Library for information about obtaining updates from the World Wide Web.

No update data for processor 2 (the secondary microprocessor).

Action: Update the system BIOS to a level that supports the microprocessors installed in the server. See the “Getting Help Information” section of this Server

Library for information about obtaining updates from the World Wide Web.

Bad update data for processor 1 (the primary microprocessor).

Action: Update the system BIOS to a level that supports the microprocessors installed in the server. See the “Getting Help Information” section of this Server

Library for information about obtaining updates from the World Wide Web.

Bad update data for processor 2 (the secondary microprocessor).

Action: Update the system BIOS to a level that supports the microprocessors installed in the server. See the “Getting Help Information” section of this Server

Library for information about obtaining updates from the World Wide Web.

A hard disk drive error occurred.

Action: Have the system serviced.

POST could not find an operating system.

Action: Install an operating system. If you have already installed the operating system, check the drive startup sequence (see “Start Options” on page 28). If the drive sequence is correct, run the diagnostic tests to verify that the hard disk drive is functioning correctly. If there is a problem with the hard disk drive (such as a bad sector), you might have to reinstall the operating system.

If you cannot reinstall the operating system, have the system serviced.

AC power has been restored.

Action: No action is required. This message appears each time AC power is restored to the server after an AC power loss.

POST found an error.

Action: Follow the instructions on the screen.

Chapter 6. Solving Problems

121