Diagnostic programs, messages, and error codesThe server diagnostic programs are the primary method of testing the majorcomponents of the server. As you run the diagnostic programs, text messages anderror codes are displayed on the screen and are saved in the test log. A diagnostictext message or error code indicates that a problem has been detected; todetermine what action you should take as a result of a message or error code, seethe table in “Diagnostic error codes” on page 60.Running the diagnostic programsTo run the diagnostic programs, complete the following steps:1. If the server is running, turn off the server and all attached devices.2. Turn on all attached devices; then, turn on the server.3. When the prompt F2 for Diagnostics appears, press F2. If you have set both apower-on password and an administrator password, you must type theadministrator password to run the diagnostic programs.4. From the top of the screen, select either Extended or Basic.5. From the diagnostic programs screen, select the test that you want to run, andfollow the instructions on the screen.When you are diagnosing hard disk drives, select SCSI Fixed Disk Test for themost thorough test. Select Fixed Disk Test for any of the following situations:v You want to run a faster test.v The server contains RAID arrays.v The server contains SATA or IDE hard disk drives.To determine what action you should take as a result of a diagnostic text messageor error code, see the table in “Diagnostic error codes” on page 60.If the diagnostic programs do not detect any hardware errors but the problemremains during normal server operations, a software error might be the cause. Ifyou suspect a software problem, see the information that comes with your software.A single problem might cause more than one error message. When this happens,correct the cause of the first error message. The other error messages usually willnot occur the next time you run the diagnostic programs.Exception: If there are multiple error codes or light path diagnostics LEDs thatindicate a microprocessor error, the error might be in a microprocessor or in amicroprocessor socket. See “Microprocessor problems” on page 42 for informationabout diagnosing microprocessor problems.If the server stops during testing and you cannot continue, restart the server and tryrunning the diagnostic programs again. If the problem remains, replace thecomponent that was being tested when the server stopped.The keyboard and mouse (pointing device) tests assume that a keyboard andmouse are attached to the server. If no mouse or a USB mouse is attached to theserver, you cannot use the Next Cat and Prev Cat buttons to select categories. Allother mouse-selectable functions are available through function keys. You can usethe regular keyboard test to test a USB keyboard, and you can use the regularmouse test to test a USB mouse. You can run the USB interface test only if no USBdevices are attached. The USB test will not run if a Remote Supervisor Adapter IISlimLine is installed.Chapter 2. Diagnostics 59