Troubleshooting
Problem
Diagnostics The following tools are available to help you identify and resolve hardware-related problems: Power-on self-test (POST) POST beep codes Test programs Error messages Error Log (Event Log) Option Diskettes
Resolving The Problem
DiagnosticsThe following tools are available to help you identify and resolve hardware-related problems:
Power-on self-test (POST)
POST beep codes
Test programs
Error messages
Error Log (Event Log)
Option Diskettes
Power-On Self-Test (POST)
Each time you power-on the system, it performs a series of tests that check the operation of the system and some options. This series of tests is called the power-on self-test, or POST. POST does the following:
- Checks some basic system-board operations
- Checks the memory operation
- Starts the video operation
- Detects and initializes ISA devices
- Detects and configures EISA devices
- Detects and configures PCI devices
- Verifies that the diskette drive, hard disk drive, and other installed devices are working
Check the indicator lights on the front of the server and the back of the power supplies. Verify that all of the amber lights are off. If an amber lights are on, see Status Indicators on page 18 Verify that both green LEDs on the back of the power supplies are on. Verify that all server devices are operating properly. If a device is not operating properly, ensure that it is not defective and is installed correctly. Replace defective devices and reinstall any device that is not installed correctly.
If POST finishes without detecting any problems, a single beep sounds and the first screen of the operating system or application program appears. If no operating system is installed, the system prompts you to insert bootable media. Refer to the information that came with the ServerGuide package for instructions on installing an operating system.
If POST detects a problem, an error message appears on the screen. A single problem can cause several error messages to appear. When you correct the cause of the first error message, the other error messages probably will not appear on the screen the next time you power-on the system.
POST Beep Codes
POST generates one or more beeping sounds to indicate that the tests detect an error. One beep and the appearance of text on the monitor indicate successful completion of the POST. If the server halts before POST completes, one or more beeps are emitted to indicate that POST detects an error. For a complete list of beep codes, see Beep Codes below.
Test Programs
Use the test (diagnostic) programs to test the IBM components of the system and some external devices. The amount of time required to test all components depends on the number of components. The more optional adapters and devices attached to the system, the longer the testing takes.
If you cannot determine whether a problem is caused by the hardware or by the software, you can run the test programs to confirm that the hardware is working correctly.
The Server diagnostic programs identify most problems associated with the major components of the system. These programs test the system board, hard disk drives, diskette drives, CD-ROM drives, RAM, serial and parallel ports, video adapter, printer, keyboard, and mouse.
Test options let you run groups of tests in a batch, specify parameters to use for each test (for example, video modes, port addresses, and so on), specify the number of passes you want to run (one to continuous), log the test results to a text format file, and save all test settings for future use.
Error Log
The error log (VIEWLOG.EXE) contains all the POST, system, and intermittent errors that occur in the server.
NOTE: The error log's default configuration setting is enable.
Use the ViewLOG.exe program located in the root directory on IBM Netfinity 7000 System CD-ROM to:
- View the error log
- Copy the error log to a diskette.
To reset the error log (when full), use the Resetlog.exe program located in the root directory on IBM Netfinity 7000 System CD-ROM. The program will prompt you for a yes/no to confirm the action before deleting the log.
Error Messages
Messages generated by the software the operating system or application programs generally are text messages, but they also can be numeric. Basically, there are four types of error messages. These include POST error messages, diagnostic error messages, POST beep codes, and software-generated messages.
|
Error message
|
Description
|
|---|---|
| POST Error Messages | Appear when, during startup, POST finds problems with the hardware or detects a change in the hardware configuration. A list of these error messages is given in Symptom-to-FRU Index on page 156 in the HMM. |
| POST Beep Codes |
Are sounds emitted from the speaker, if POST finds a problem. One beep indicates the POST completed successfully. If the server halts while running POST, one or more beeps indicate that a problem was found by the POST. A list of the beep error codes is given in Symptom-to-FRU Index on page 156 in the HMM. |
| Diagnostic Error Messages | Appear when a test program finds a problem with a hardware option. Normally, these messages are text, but they can be numeric. The test programs will generate one of the following return codes: 0 - A return code of 0 indicates that the device passed its test. 1 - A return code of 1 indicates that the device failed its test. 2 or higher - A return code of 2 or higher indicates that the test stopped. |
| Software-Generated Error Messages | Appear if a problem or conflict is found by an application program, the operating system, or both. For an explanation of these messages, refer to the information that comes with your software package. |
Option Diskettes
An optional device or adapter might come with a diskette. Option Diskettes usually contain diagnostic files or configuration files that the system needs to recognize and activate the option.
If the optional device or adapter comes with an Option Diskette, you might need to install some configuration (.CFG) files or diagnostic files (.EXE or .COM). See ISA or EISA Option Diskettes for instructions on installing the configuration files.
The Startup Menu of the Diagnostic Tests
The Startup Menu is the starting point for all of the diagnostic tests. It contains the following selections:
Run Netfinity 7000 Diagnostics When you select this choice from the Startup Menu, the Diagnostics Menu appears. The Diagnostics Menu contain the following selections:
- Test allows you to specify an individual module (or device such as a diskette drive) for testing, or specify a group of tests for several modules. In addition, you can specify how many times to run an individual test and how the test program should note and log any errors it finds.
- Errors displays the error messages that the system has captured.
- Summary lists all tests that have been run, the run times, the number of times passed, the number of times failed, and the error messages.
- Configuration allows you to save a test configuration to run at a later time.
- Options allows you to set or change defaults that affect the reporting, error logging, and presentation of the error information.
Run Netfinity 7000 Memory Test (Quick - 5 min/64 MB): Provides a quick test of the system memory.
Run Netfinity 7000 Memory Test (Extensive - 15 min/64 MB): Provides a more extensive test of the system memory.
Run Advanced System Management Adapter Diagnostics. Provides a more extensive test of the processor(s).
Program Navigation
You can maneuver within the test programs by typing the first letter of a menu choice, or using the function keys.
|
Function key
|
Description
|
|---|---|
| Enter | Selects an item |
| Down arrow | Moves the cursor down |
| Up arrow | Moves the cursor up |
| Right arrow | Moves the cursor to the right |
| Left arrow | Moves the cursor to the left |
| F1 | Displays the appropriate Help information. Use the Up arrow or Down arrow key to scroll through the information. |
| ESC | Returns to the previous menu |
The following additional keys are active on the Test window. Press the TAB key from the Test window to view a description of all keys.
|
Function key
|
Description
|
|---|---|
| Enter | Selects a test module and displays the sub-test menu, or runs an enabled sub-test. |
| Space | Toggles (switches) test modules and sub-tests between enabled or disabled. |
| F2 | Runs the current enabled sub-test. |
| F3 | Disables the current test module or sub-test. |
| F4 | Enables the current test module or sub-test. |
| F5 | Accesses global run-time flags and module run-time flags. Refer to Run-Time Flags on page 13 of the HMM for information. |
| F6 | Accesses test module .CFG parameters. |
| F7 | Displays the error messages that the system has captured. |
| F8 | Displays all tests that have been run, the run times, the number of times passed, the number of times failed, and the error messages. |
| F9 | Displays the version number of the test module. |
| ALT+F2 | Runs all enabled sub-tests in all test modules. |
| ALT+F3 | Disables all sub-tests and all test modules. |
| ALT+F4 | Enables all sub-tests and all test modules. |
| ALT+F6 | Displays the .PKG parameters. |
Command Line Options
The Command Line Options allow you to define specific conditions for running the diagnostic programs from the DOS command line or at startup time.
At the operating system prompt, type t xxxx yyyy (where xxxx represents a test and yyyy is a flag.
The test can be identified either by the module name or by it's position in the .PKG file, for example:
|
Module name
|
Description
|
|---|---|
| Floppy | Run all enabled sub-tests in the floppy test module |
| Floppy-1 | Run the first sub-test of the floppy test module, if enabled |
| 1-5 | Run all enabled sub-tests of the first 5 test modules in the.PKG file |
A command line option can contain the following flags:
|
Option
|
Description
|
|---|---|
| /? | Prints the contents of the help file. |
| /AUTO (filename) | Configures the test menu based on the hardware detected in the system. The system saves the configuration in the file name you provide. |
| /CF (filename) | Specifies the configuration file to use. |
| /DT (nn) | Displays all sub-tests. If the sub-test is enabled, a + displays next to the sub-test. If disabled, a - displays next the sub-test. nn is the number of lines to display. Press Enter to display the next screen of sub-tests. |
| /GROUP (chars) | Runs the sub-tests that have the character string that you specify. |
| /HOURS (nn.n) | Defines the length of time to continue testing. |
| /N (n) | Defines the number of times the test will loop. |
| /OVER | Overrides the disable flag on each sub-test. |
| /PC (product code) | Provides the diagnostics program product code. |
| /PKG (filename) | Processes the file name you provide instead of the default, T.PKG. |
| /Q | No output to screen during testing. |
| /SAVE (filename) | Saves the configuration to the file name you provide. |
| /SELF (filename) | Configures the test menu based on the hardware detected in the system and saves it to the file name you provide. |
| /SHUFFLE (nn) | Shuffles the run-list on each pass. nn is the number of passes. |
Run-Time Flags: The run-time flags are the commands that control execution of the tests. The Edit Run-Time Flags selection on the Options Menu provides access for editing the run-time flags.
|
Flag
|
Description
|
|---|---|
| /T | Required flag. |
| /CF (filename) | The file name you provide contains parameters that supplement or override parameters in the .PKG file. |
| /HE | Halt on error. |
| /PE | Prompt on error. |
| /(n) | Number of loops to execute. |
| /Q | No messages to console. |
| /RR (filename) | Redirects error messages, advisory messages, and status messages to the file name you provide. |
| /RE (filename) | Redirects error messages to the file name you provide. |
| /RA (filename) | Redirects advisory messages to the file name you provide. |
| /RS (filename) | Redirects status messages to the file name you provide. |
| /RX (filename) | Redirects statistics to the file name you provide. |
| /SF (filename) | Redirects the summary file to the file name you provide. |
| /SS (filename) | Summarize loops and failures after each test to the file or printer. |
| /W (nn) | Wait only nn seconds if the test is defined to halt on error. |
Starting the Diagnostic Programs
To start the test programs from the System CD-ROM:
- Use the Setup program to define the CD-ROM drive as the First Boot Device. Refer to Defining the Startup Device.
- Insert the System CD-ROM into the CD-ROM drive.
- Power-on the system. Or, if the system is powered on, press Ctrl+Alt+Del.
- Use the Up Arrow or Down Arrow key to select Run System Diagnostics from the Startup Menu.
- Use the Up Arrow or Down Arrow key to move the highlight bar to your desired Startup Menu selection.
- Press Enter.
NOTES:
- If a user password is set, you must enter it to access thetest programs. If you have set user and administrative passwords, you can enter either one.
- If a configuration error occurs, a prompt appears before the operating system starts (see Configuration Conflicts ).
- To stop running a specific test or stop testing after you have started a test, press CNTL+Break while the test is running. The test stops at the first possible opportunity.
Using the Test Selection
To start the Test selection from the Startup Menu:
- Start the diagnostic programs, see Starting the Diagnostic Programs on page 13 of the HMM.
- Select Run Server Diagnostics from the Startup Menu; then, press Enter.
- Use the Left and Right arrow keys to select Test. Use the Up Arrow or Down Arrow key to move the highlight barfrom one selection to the next within the Test window. You can also enter the number of your desired test to move the highlight bar.
- Press Enter at the highlight bar of the desired test module.
- Press the Spacebar at the highlight bar to enable the desired sub-test.
- Press F2 to run the selected sub-test.
- Select the number of passes and the length of processing time; then, press Enter. If you want to run all enabled sub-tests, you can do so by pressing ALT+F2.
To set up a test script:
- Select Run Server Diagnostics from the Startup Menu; then press Enter.
- Select Test from the Diagnostics Menu.
- Select the tests, sub-tests, and parameters.
- Select Configuration from the Diagnostics Menu.
- Select Save Test Configuration.
- Type in a file name and press Enter.
- To load and run the test program with this test setting, type: T /CF filename and then, press Enter.
|
Option
|
Description
|
|---|---|
| Line Printer | Sends error messages to a line printer. |
| Halt on Error | If you select Yes, you can resume testing after a halt by pressing any key. If you select No, any error detected is logged (only if you enabled the Test Log) and the program continues testing without halting. |
| Prompt on Error | If you select Yes, a beep sounds whenever the test program detects an error. |
| Summarize Loops/Fails | Summarize the number of times the test has been run and the number of failures. Can optionally redirect to file or printer. |
| Interactive Waiting | This option allows you to define a period of time after which tests defined to halt on error will continue. |
| Edit Run-Time Flags | Gives access for editing of all global run-time flags. |
| Run All Tests | Automatically enables all tests. |
| Use Run-List | Allows you to specify a sequence of tests and loops. |
| Run DOS Command | Allows you to enter a DOS command. |
Configuration Menu: The following is a brief description of each option that appears on the Configuration Menu.
|
Option
|
Description
|
|---|---|
| Configure Test Menu from List | Provides a menu of configuration files. |
| Configure Test Menu from File | Prompts you to enter the file name of the configuration. |
| Self-Configure Test Menu | Automatically configures the test menu based on the hardware detected in the system. |
| Auto-Integrate Test Pack | Automatically configures the test menu based on the hardware detected in the system and runs integration utilities. |
| Display System Hardware | Lists all system hardware. |
| Save Test Configuration | This selection allows you to save the test configuration. |
| Change Menu Color | Provides access to the menu colors. |
| Change Test View.INI Parameters | Provides access to all Test View parameters maintained in the .INI file. |
POST Error Codes and Messages
Error Codes and Messages might appear on the screen during the power-on self-test (POST).
Sometimes the first error to occur causes additional errors. In this case, the system displays more than one error message. Always follow the suggested action instructions for the first error message that appears.
POST error codes are also written to the error log in the Extended BIOS Data Area and can be viewed using the event log utility. For a complete list of error codes and messages, see Symptom-to-FRU Index .
SCSI Messages
NOTE: If the server has a CD-ROM drive, but does not have a hard disk drive, ignore any message that indicates that the BIOS is not installed.
|
SCSI Message
|
Description
|
|---|---|
| All |
One or more of the following might be causing the problem.
Action: Verify that:
If the above are correct, run the diagnostics for additional information about the failing device. |
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
23 January 2019
UID
ibm1DDSE-43TR9N