Manuals

Back to Content Page

Running the Dell Diagnostics: Dell™ PowerEdge™ 2300 Systems Installation and Troubleshooting Guide

Unlike many diagnostic programs, the Dell Diagnostics helps you check the computer's hardware without any additional equipment and without destroying any data. By using the diagnostics, you can have confidence in the computer system's operation. And if you find a problem you cannot solve by yourself, the diagnostic tests can provide you with important information you will need when talking to Dell's technical support representative.

CAUTION: Use the Dell Diagnostics to test only Dell computer systems. Using this program with other computers may cause incorrect computer responses or result in error messages.

Features of the Dell Diagnostics

The Dell Diagnostics provides a series of menus and options from which you choose particular test groups or subtests. You can also control the sequence in which the tests are run. The diagnostic test groups or subtests also have these helpful features:

• Options that let you run tests individually or collectively
• An option that allows you to choose the number of times a test group or subtest is repeated
• The ability to display or print test results or to save them in a file
• Options to temporarily suspend testing if an error is detected or to terminate testing when an adjustable error limit is reached
• A menu option, called About, that briefly describes each test and its parameters
• Status messages that inform you whether test groups or subtests are completed successfully
• Error messages that appear if any problems are detected

When to Use the Dell Diagnostics

Whenever a major component or device in the computer system does not function properly, you may have a component failure. As long as the microprocessor and the input and output components of the computer system (the monitor, keyboard, and CD-ROM drive) are working, you can use the Dell Diagnostics. If you know what component(s) you need to test, simply select the appropriate diagnostic test group(s) or subtest(s). If you are unsure about the scope of the problem, read the rest of this chapter.

Starting the Dell Diagnostics

Follow these steps to run the diagnostics:

1. Create a diagnostics diskette using the Dell Server Assistant CD.

See "Create Diskettes" in Chapter 2 of the Dell PowerEdge 2300 Systems User's Guide.

2. Boot the system from the diagnostics diskette.

If the system fails to boot, see Getting Help for instructions on obtaining technical assistance.

3. From the main menu, select the Run System Diagnostics option from Run System Utilities.

NOTE: Before you read the rest of this chapter, you may want to start the Dell Diagnostics so you can see it on the screen of the monitor.

When you start the diagnostics, the Dell logo screen appears, followed by a message telling you that the diagnostics is loading. Before the diagnostics loads into memory, a program tests the random-access memory (RAM) that will be used by the diagnostics.

If no errors are found in RAM, the diagnostics loads, and the Diagnostics Menu appears (see Figure 1). The menu allows you to run all or specific diagnostic tests or to exit the Dell Diagnostics.

For a quick check of the system, select the Run Quick Tests option. This option runs only the subtests that do not require user interaction and that do not take a long time to run. Dell recommends that you choose this option first to increase the odds of tracing the source of the problem quickly. For a complete check of the system, select the Run All Tests option. To check a particular area of the system, select the Run Specific Tests option.

To select an option from the Diagnostics Menu, highlight the option and press <Enter>, or press the key that corresponds to the highlighted letter in the option you choose.

Figure 1. Diagnostics Menu

How to Use the Dell Diagnostics

When you select Run Specific Tests from the Diagnostics Menu, the main screen of the diagnostics appears. Figure 2 shows a sample main screen; the actual text on your system may vary depending on your system configuration.

Information on the main screen of the diagnostics is presented in the following five areas:

• Two lines at the top of the main screen identify the diagnostics and give its version number.
• On the left side of the screen, the Available Test Groups area lists the diagnostic test groups in the order they will run if you select All under the Run submenu. Press the up- or down-arrow key to highlight a test group.
• On the right side of the screen, the System Configuration area lists the computer's current hardware settings.
• Two lines at the bottom of the screen make up the Main Menu area. The first line lists the menu options you can select; press the left- or right-arrow key to highlight an option. The second line gives information about the highlighted option.

Figure 2. Dell Diagnostics Main Screen

NOTE: The options displayed on the screen should reflect the hardware configuration of the computer system.

Confirming the System Configuration Information

When you boot the system from the diagnostics diskette, the Dell Diagnostics checks the system configuration information and displays it in the System Configuration area on the main screen.

The following sources supply this configuration information for the Dell Diagnostics:

• The system configuration information settings (stored in nonvolatile RAM [NVRAM]) that you selected while using the System Setup program
• Identification tests of the microprocessor, the video controller, the keyboard controller, and other key components
• Basic input/output system (BIOS) configuration information temporarily saved in RAM

Do not be concerned if the System Configuration area does not list the names of all the components or devices you know are part of the computer system. For example, you may not see a printer listed, although you know one is attached to the computer. Instead, the printer is listed as a parallel port. The computer recognizes the parallel port as LPT1, which is an address that tells the computer where to send outgoing information and where to look for incoming information. Because the printer is a parallel communications device, the computer recognizes the printer by its LPT1 address and identifies it as a par­allel port.

How to Use the Main Menu

One of the Main Menu options is already highlighted. You can move the highlight from one option to another by pressing the left- or right-arrow key. As you move from one menu option to another, a brief explanation of the highlighted option appears on the bottom line of the screen.

If you want more information about a test group or subtest, move the highlight to the About option and press <Enter>. After reading the information, press the <Esc> key to return to the previous screen.

Main Menu Options

Eight options are listed in the Main Menu of the diagnostics main screen: Run, Select, Subtest, Options, Test Limits, About, Key-Help, and Quit. (An additional option, Display the Run Menu, returns you to the Diagnostics Menu shown in Figure 1.)

NOTE: Before running any test groups or subtests (by selecting Run), you should consider setting global parameters within the Options option. They offer you greater control over how the test groups or subtests are run and how results are reported.

There are two ways to select a menu option:

• Look on the screen to see which letter in the option is capitalized, and type that letter (for example, type r to select the Run option).
• Move the highlight to the option you wish to select by pressing the left- or right-arrow key, and then press <Enter>.

Whenever one of the eight options is selected, additional choices become available.

The following subsections explain the menu options as listed from left to right in the Main Menu.

Run

Run displays five options: One, Selected, All, Key-Help, and Quit Menu. If you select One, all the subtests within the highlighted test group are run. If you choose Selected, only the selected test groups or the subtests that you selected within the test groups are run. If you select All, all of the subtests in all of the test groups are run. (The test groups or subtests are run in the same order as they are listed.)

The Key-Help option displays a list of key controls available for the particular option you have chosen. The Quit Menu option returns you to the previous menu.

Select

Select allows you to select individual test groups to tailor the testing process to your particular needs. You can choose one or more test groups and run them sequentially or individually. When you choose Select, five options are displayed: All, One, Clear All, Key-Help, and Quit Menu.

To select all the test groups, press <Enter> when All is highlighted in the Select menu.

To select an individual test group, highlight the test group and press <Spacebar> or highlight One and press <Enter>. Press the up- or down-arrow key to change the highlighted test group.

To reverse a test group selection, highlight the test group and press <Spacebar>. To clear all selections, select Clear All.

The Key-Help option displays a list of key controls available for the particular option you have chosen. The Quit Menu option returns you to the previous menu.

Subtest

Most of the test groups consist of several subtests. Use the Subtest option to select individual subtests within the test group(s).

When you select Subtest, many of the same options as those on the Main Menu are displayed: Run, Select, Options, Test Limits, About, Key-Help, and Quit Menu. Each of these options is explained in the following subsections.

Run Under Subtest

Run in the Subtest menu displays five options: One, Selected, All, Key-Help, and Quit Menu. If you select One, only the highlighted subtest is run. If you select Selected, only the selected subtests are run. If you select All, all of the subtests listed on the screen are run. (The subtests are run in the same order as they are listed.)

The Key-Help option displays a list of key controls available. The Quit Menu option returns you to the previous menu.

Select Under Subtest

Select in the Subtest menu allows you to select individual subtests to tailor the testing process to your particular needs. You can choose one or more subtests from the list. When you choose Select, five options are displayed: All, One, Clear All, Key-Help, and Quit Menu.

To select all the subtests, press the <Enter> key when All is highlighted in the Select menu. To select an individual subtest, highlight the subtest and press the <Spacebar> or highlight One and press <Enter>. Press the up- or down-arrow key to highlight a subtest to be selected.

To reverse a subtest selection, highlight the subtest and press the <Spacebar>. To clear all selections, select Clear All.

The Key-Help option displays a list of key controls available. The Quit Menu option returns you to the previous menu.

Options Under Subtest

The Options option in the Subtest menu functions the same way as the Options option in the Main Menu. For information on this option, see Options.

Test Limits Under Subtest

The Test Limits option in the Subtest menu functions the same way as the Test Limits option in the Main Menu. For information on this option, see Test Limits.

About Under Subtest

The About option in the Subtest menu displays information about the highlighted subtest.

Key-Help Under Subtest

The Key-Help option in the Subtest menu displays a list of key controls available.

Quit Menu Under Subtest

The Quit Menu option in the Subtest menu returns you to the previous menu.

Options

Table 1 lists all of the possible values for each global parameter of Options. A brief description of each parameter follows the table. To change Options parameters, press the <Spacebar>, the left- and right-arrow keys, or the plus (+) and minus (-) keys.

Number of Times to Repeat Test(s)

This parameter specifies the number of times the tests run when you select Run. To change the default, type the desired value. If you type 0 (zero), the tests will run indefinitely.

Maximum Errors Allowed

This parameter specifies the maximum number of errors that can occur before testing is stopped. The error count begins from zero each time you run a subtest or test group individually or each time you select All to run all of them. To change the default, type the desired value. If you type 0 (zero), you are specifying that there be no limit on the number of errors that can occur--testing will not be stopped, regardless of the number of errors.

Pause for User Response

If this parameter value is set to Yes, the diagnostics pauses when one of the following occurs:

• Your interaction is needed to verify the Video Test Group screens or the Keyboard Test Group key functions, or another type of interaction, such as inserting a diskette, is required.
• The maximum error limit is reached.

If the Pause parameter is set to No, the diagnostics ignores some subtests that require your interaction; certain subtests can run only if this option is set to Yes because they require user interaction. Use the Pause parameter in situations where you may want to prevent subtests that require user interaction from running--such as when you run the diagnostics overnight.

Output Device for Status Messages

Ordinarily, all status messages appear only on the screen. This parameter allows you to direct status messages to either a printer or a file, in addition to the screen. If you choose the File option, status messages are written to a file named result. This file is automatically created on a diskette in drive A when you run the diagnostics. If the result file already exists on the diskette, then new status messages are added to it.

The result file is an ordinary American Standard Code for Information Interchange (ASCII) text file. You can access the result file with the MS-DOS ® type command as follows:

1. Select Quit to exit the diagnostics and return to the operating system prompt.

2. At the operating system prompt, type the following command and press <Enter>:

type result

The contents of the file appear on the screen.

After running particular diagnostic tests and viewing the status messages generated by the tests in the result file, you can erase the contents of the file so that it is clear for the next set of messages generated. Otherwise, the next messages are added at the end of the previous ones in the file.

Output Device for Error Messages

Ordinarily, all error messages appear only on the screen. The Output Device for Error Messages parameter allows you to direct error messages to either a printer or a file, in addition to the screen. If you choose the File option, error messages are written to the result file used for status messages. This file is automatically created on a diskette in drive A when you run the diagnostics. If the result file already exists on the diskette, then new error messages are added to it.

The result file is an ordinary ASCII text file. You can access and review the result file with the MS-DOS type command as described in the previous subsection, "Output Device for Status Messages."

After running particular diagnostic tests and viewing the error messages generated by the tests in the result file, you can erase the contents of the file so that it is clear for the next set of messages generated. Otherwise, the next messages are added at the end of the previous ones in the file.

Test Limits

NOTE: The diagnostics program sets default limits on all tests. The only reason to change the default would be to limit the amount of testing done.

The RAM Test Group, the Video Test Group, the Diskette Drives Test Group, the Serial/Infrared Ports Test Group, the Parallel Ports Test Group, and the SCSI Devices Test Group allow you to designate limits. Whether you select Test Limits for a highlighted test group (from the Main Menu) or a subtest (from the Subtest menu), you set the limits for all the subtests in that test group. When you select Test Limits, a new screen appears and the Key-Help area lists keys to use with the new screen.

How you change a value for the limits of a test group or subtest depends on the type of parameter associated with it. Different keys are used to change values for different types of parameters. For example, memory address limits specified for the RAM Test Group are changed by typing numbers over the digits of a given limit or by pressing the plus (+) or minus (-) key to increase or decrease the given limit. In contrast, to set limits for the Serial/Infrared Ports Test Group, you use the <Spacebar> to toggle between Yes and No.

After you are satisfied with the limits, return to the main screen of the diagnostics by pressing the <Esc> key. The values you selected under Test Limits remain in effect for all the test groups or subtests you run, unless you change them. However, the values are reset to their defaults when you restart the diagnostics.

About

About in the Main Menu lists all of the subtests for the selected test group and displays information about the subtest that is highlighted.

Key-Help

Key-Help always displays a list of key controls available for the particular option you have selected.

Quit

Selecting Quit from the Main Menu exits the diagnostics and returns you to your operating system environment.

CAUTION: It is important that you quit the diagnostics program correctly because the program writes data to the computer's memory that can cause problems unless properly cleared.

Tests in the Dell Diagnostics

To troubleshoot components or devices, run the appropriate test (test group or subtest) in the diagnostics. The diagnostics exercises the functional components and devices of the computer system more vigorously and thoroughly than they are exercised during normal operation. The diagnostics is organized by components into test groups and subtests within each test group. Each subtest is designed to detect any errors that may interfere with the normal operation of a specific device of the computer.

NOTE: Some subtests requiring hardware not listed in the System Configuration area of the main screen appear to run, but they conclude with a status message stating Component not present (or disabled).

Table 2 lists the diagnostic test groups, their subtests, and comments concerning their use.

Error Messages

When you run a test group or subtest in the diagnostics, error messages may result. These particular error messages are not covered in this chapter because the errors that generate these messages can be resolved only with Dell technical assistance. Record the messages on a copy of the Diagnostics Checklist found in Chapter 11, "Getting Help;" also see Chapter 11 for instructions on obtaining technical assistance and informing the technical support representative of these messages.

RAM Test Group

The RAM Test Group subtests check all the directly addressable RAM.

Subtests

Three subtests are available for RAM: the Quick Memory Test, the Comprehensive Memory Test, and the Cache Memory Test. The Quick Memory Test performs an address check to determine whether the computer is properly setting and clearing individual bits in RAM and whether the RAM read and write operations are affecting more than one memory address location at one time. This subtest checks all available RAM.

The Comprehensive Memory Test performs an address check as well as the following:

• Data pattern checks, to look for RAM bits that are stuck high or low, short-circuited data lines, and some data pattern problems that are internal to the memory chips
• A parity check that verifies the ability of the memory subsystem to detect errors
• A refresh check, to verify that the dynamic RAM (DRAM) is being recharged properly

The Cache Memory Test confirms the functionality of the computer's cache controller chip and the cache memory.

Why Run a RAM Test?

Faulty memory can cause a variety of problems that may not appear to be happening in RAM. If the computer is displaying one or more of the following symptoms, run the subtests in the RAM Test Group to verify that the memory is not at fault:

• A program is not running as usual, or a proven piece of software appears to malfunction and you confirm that the software itself is not at fault. (You can confirm that the software is functioning properly by moving it to another computer and running it there.)
• The computer periodically locks up (becomes un-usable and must be rebooted), especially at different places and times in different programs.
• You get a parity error (any error message that contains the word parity) at any time during operation. These errors are usually accompanied by a reference to an address--the location of the portion of memory where the error occurred--which you should record on a copy of the Diagnostics Checklist found in Chapter 11, "Getting Help."
• You receive the Memory ECC fault detected message from the Dell Hardware Instrumentation Package (HIP) server management application. See Chapter 3, "Messages and Codes," for more information on this program.

System Set Test Group

The subtests in the System Set Test Group check the computer's basic system board components and verify their related functions.

Subtests

The subtests that constitute the System Set Test Group and the computer functions they confirm follow:

• CMOS Confidence Test

Checks the NVRAM for accessibility and reliability of data storage by performing a data pattern check and verifying the uniqueness of memory addresses.

• DMA Controller Test

Tests the direct memory access (DMA) controller and verifies the correct operation of its page and channel registers by writing patterns to the registers.

• Real-Time Clock Test

Confirms the functionality and accuracy of the computer's real-time clock (RTC).

• System Timers Test

Checks the timers used by the microprocessor for event counting, frequency generation, and other functions. Only the functions that can be activated by software are tested.

• Interrupt Controller Test

Generates an interrupt on each interrupt request (IRQ) line to verify that devices using that line can communicate with the microprocessor and that the interrupt controllers send the correct memory addresses to the microprocessor.

• APIC Test

Tests that the procedure used to boot a multiprocessor system is able to properly receive interrupts from the input/output (I/O) Advanced Peripheral Interrupt Controller (APIC).

• APIC MP Test

Ensures that all microprocessors are able to properly receive interrupts from the I/O APIC.

• System Speaker Test

Checks the functionality of the speaker by generating eight tones.

• Coprocessor Calculation Test

Checks the use of different types of numbers and the math coprocessor's ability to calculate correctly.

• Coprocessor Duty Cycle Test

Tests the math coprocessor's ability to perform complex mathematical operations.

• Coprocessor Error Exception Test

Verifies the math coprocessor's ability to handle errors and to send IRQs to the microprocessor.

• Multiprocessor Test

For systems with multiprocessors, confirms that the secondary microprocessor is operational.

Why Run a System Set Test?

The System Set subtests double-check many system board components, such as the computer's I/O circuitry, that are tested by other test groups or subtests in the diagnostics. You should run the System Set Test Group if you are having a problem and cannot isolate the failure or malfunction to a particular system board component.

The System Set Test Group also verifies the proper operation of other computer components, such as the speaker, that are not tested elsewhere in the diagnostics.

The following symptoms usually suggest a problem with a component or subassembly that warrants running a System Set subtest:

• A program is not running as usual, or a proven piece of software appears to malfunction and you confirm that the software itself is not at fault. (You can confirm that the software is functioning properly by moving it to another computer and running it there.)
• An option card you previously accessed can no longer be accessed.
• You get a parity error or page fault failure--any error message that contains the word[s] parity or page fault--at any time during operation. These errors are usually accompanied by a reference to an address, which you should record on a copy of the Diagnostics Checklist found in Chapter 11, "Getting Help."
• Correcting errors in the system configuration information in the System Setup program does not resolve a problem.
• The computer's clock/calendar stops.
• The speaker no longer functions. The problem could be a failure of the system timers as well as a failure of the speaker itself. Run the System Timers Test, followed by the System Speaker Test.
• A peripheral device appears to malfunction. Run the Interrupt Controllers Test.
• A spreadsheet program or other type of mathemat­ical application runs abnormally slow, generates error messages concerning calculations or operations, runs incorrectly, or generates incorrect results, or a proven piece of the program appears to mal­function and you confirm that the software itself is not at fault. (You can confirm that the software is not at fault by moving the program to another computer and running it there.)
• The computer periodically locks up, especially at different places and times in different programs.
• The computer halts in the middle of performing calculations or complex mathematical operations.

Video Test Group

The subtests in the Video Test Group verify the proper operation of the video controller and the video control circuitry installed in the computer. These subtests check for the correct operation of the readable registers in the video circuitry and the controller. They write, read, and verify data patterns in the cursor registers of the controller. The Video Test Group also tests all the video memory and provides additional subtests to test the color features of a color monitor.

Subtests

The eight subtests in the Video Test Group and the video functions they test follow:

• Video Memory Test

Checks the read/write capability of video memory in various video modes.

• Video Hardware Test

Checks the cursor registers and the horizontal and vertical retrace bit registers in the video controller.

• Text Mode Character Test

Checks the video subsystem's ability to present data in text modes.

• Text Mode Color Test

Checks the video subsystem's ability to present color in text modes.

• Text Mode Pages Test

Checks the video subsystem's ability to map and present all available video pages on the screen, one page at a time.

• Graphics Mode Test

Checks the video subsystem's ability to present data and color in graphics modes.

• Color Palettes Test

Checks the video subsystem's ability to display all of the available colors.

• Solid Colors Test

Checks the video subsystem's ability to show screens full of solid colors. Allows you to check for missing color subpixels.

Many of these tests display characters or graphics on the screen for you to verify. Samples of these screens are shown in Diagnostic Video Tests.

NOTE: The default limit for testing super video graphics array (SVGA) modes is No. If you are testing an external monitor, change the default to Yes.

Why Run a Video Test?

Many of the symptoms that would prompt you to run a subtest in the Video Test Group are obvious, because the monitor is the visual component of the computer system. Before you run the Video Test Group or any of its subtests, you should make sure that the problem is not in the software or caused by a hardware change. You should also try running all of the software support utilities provided for the monitor and the video subsystem.

If the following symptoms still occur, run the appropriate test(s) as follows:

• If the monitor shows a partially formed or distorted image, run all of the subtests in the Video Test Group.
• If the alignment of text or images is off, regardless of the program you are running, run the Text Mode Character Test, Text Mode Pages Test, and Graphics Mode Test.
• If you have a color monitor or a program that runs in color, but the color is intermittent or not displayed at all, run the Text Mode Color Test, Color Palettes Test, and Solid Colors Test.
• If the monitor malfunctions in one mode but works fine in another (for example, text is displayed correctly, but graphics are not), run the Text Mode Character Test, Text Mode Color Test, Text Mode Pages Test, and Graphics Mode Test.

Keyboard Test Group

The subtests in the Keyboard Test Group verify the correct operation of the keyboard and the keyboard controller chip.

Subtests

The five keyboard subtests and the keyboard functions they test follow:

• Keyboard Controller Test

Confirms the ability of the keyboard controller chip to communicate with the keyboard and the programming of the controller chip

• Keyboard Key Sequence Test

Verifies that the keys on the keyboard function correctly when you press the keys in a predefined order

• Keyboard Interactive Test

Checks the internal microcode of the keyboard and the external interface of the keyboard controller chip for a malfunctioning key

• Stuck Key Test

Checks the internal microcode of the keyboard and the external interface of the keyboard controller chip for a repeating-key signal

• External Key Pad Test

Checks the contact beneath each key for an electrical impulse to ensure that each key is working properly

Why Run a Keyboard Test?

Keyboard problems are not always caused by the keyboard. For example, if the computer system locks up, rendering the keyboard inoperable, the problem is most likely not caused by the keyboard. There are three symptoms that are likely to be keyboard-related. Sometimes, the configuration of a program changes the function of a key or key combination. Likewise, key configuration programs can change a key's function. Because these programs are memory resident, you should be sure to clear them out of the computer's memory before running a subtest in the Keyboard Test Group. (Clear them from memory by rebooting the computer from the diagnostics diskette.) When these possibilities have been eliminated, and if the following symptoms occur, you should run one or more of the subtests in the Keyboard Test Group:

• When you press a key, the character represented by that key appears repeatedly; the key seems to be stuck. Run the Stuck Key Test.
• When you press a key and the response is different from the usual response or the response you anticipated, the key contact may be damaged. Run the Keyboard Interactive Test.
• When a key does not work at all, run all of the subtests in the Keyboard Test Group.

Mouse Test

The Mouse Test checks the functionality of the mouse controller (which coordinates cursor movement on the screen with corresponding movement of the mouse or touch pad) and the operation of the mouse keys/touch pad.

Subtests

There are no subtests for the Mouse Test Group.

Why Run the Mouse Test?

Mouse or touch pad problems are as likely to originate in RAM as they are to be caused by a faulty mouse or touch pad. Three sources of RAM-related problems include the configuration of a program (which changes the function of the mouse or touch pad), memory-resident programs, and failure of a device driver (the software that controls the function of the mouse or touch pad). If these possibilities have been eliminated and the following symptoms persist, run the Mouse Test:

• When you press a mouse button or the touch pad, the function of the button (or touch pad) continues; that is, the button (or touch pad) seems to be stuck.
• When you press a mouse button or the touch pad, the response is different from the usual or anticipated response, which indicates the button (or touch pad) contact may be damaged.
• A mouse button or the touch pad does not work at all.
• The cursor does not respond on the screen in accordance with the movements you make with the mouse or touch pad.

Diskette Drives Test Group

The subtests in the Diskette Drives Test Group allow you to test 3.5-inch diskette drives of all capacities.

Subtests

The four diskette drive subtests in the Diskette Drives Test Group and the drive functions they test follow:

• Change Line Test

Checks for bent pins on the diskette drive controller and for defective lines on the diskette cable

• Seek Test

Checks the drive's ability to search for a specified track on the diskette and to position its read/write heads to all tracks

• Read Test

Positions the read/write heads at each cylinder of the diskette for reading data and verifies that all tracks on the diskette can be read correctly

• Write Test

Positions the read/write heads at each cylinder of the diskette and verifies that all tracks on the diskette can be written to correctly

Why Run a Diskette Drives Test?

Very often, a diskette drive problem may first appear to be a diskette problem. A box of defective diskettes might produce faulty-drive error messages. The test results can be confusing, so Dell suggests running the subtests in the Diskette Drives Test Group more than once using diskettes from different sources.

A command that is typed in an incorrect form (usually called a syntax error) is another possible cause of diskette drive problems. Be sure you have entered the command in the proper form.

If the diskette(s) and command syntax are eliminated as causes, the following symptoms usually suggest a drive problem and warrant running a subtest in the Diskette Drives Test Group:

• An error message appears on the screen stating that the computer cannot read from or write to a diskette.
• A diskette cannot be properly formatted, or format error messages appear on the screen.
• Data on diskettes is corrupted or lost; these problems may be intermittent.

Serial/Infrared Ports Test Group

The subtests in the Serial/Infrared Ports Test Group check the computer's interface with external devices, such as a printer and a mouse, that are connected to the computer through a serial or infrared port. The subtests in this test group are not intended as a diagnostic test for the actual peripheral attached to each port.

NOTES: With certain modems installed, the subtests in the Serial/Infrared Ports Test Group may fail because the modem appears to the diagnostics as a serial or infrared port, but it cannot be tested as a serial or infrared port. If a modem is installed and one of the subtests in the Serial/Infrared Ports Test Group fails, remove the modem and run the diagnostic tests again. If an external loopback connector is not attached to a serial or infrared port, the Serial External Transmission Test will fail for that port and the results of this test should be ignored. An external modem connected to the port does not substitute for an external loopback connector.

Subtests

The four subtests in the Serial/Infrared Ports Test Group and the port functions they test follow:

• Serial/Infrared Baud Rate Test

Checks the baud rate generator in each serial communications chip against the computer's clock

• Serial/Infrared Interrupt Test

Checks the serial port's ability to send IRQs to the microprocessor

• Serial/Infrared Internal Transmission Test

Checks several internal functions of the serial port using the internal loopback mode of the serial communications chip

• Serial External Transmission Test

If a loopback device is attached, checks the line control bits of the serial port and sends a test pattern at several baud rates, checking the returned values

Why Run a Serial/Infrared Ports Test?

If the diagnostics does not recognize the computer's serial or infrared ports, enter the System Setup program and check the Serial/Infrared Port option to see whether the port has been disabled. (See Chapter 4, "Using the System Setup Program," in the Dell PowerEdge 2300 Systems User's Guide for instructions.) The subtests in the Serial/Infrared Ports Test Group cannot test a port unless it is enabled.

When a port is faulty, it may not be immediately evident that the port, and not the device connected to the port, is faulty. Instead, the peripheral might behave erratically or not operate at all. If the external device is not properly installed through the software, it also may not function properly. Try operating the peripheral from different programs or through the operating system. If it still does not work, you can eliminate the software configuration as the cause of the problem.

Another possible cause for errors is the external device. Use the documentation that came with the peripheral to troubleshoot the device and confirm that it is working properly.

After you eliminate incorrect system configuration information settings, peripheral malfunctions, and software errors as potential causes of port problems, you can run the subtests in the Serial/Infrared Ports Test Group to check the hardware. Although the following symptoms can be caused by faulty peripherals or software errors, they might also suggest a port problem:

• If a peripheral works intermittently or produces intermittent errors, the port may be faulty.
• If the computer displays an error message that is related to the external device connected to a port but corrections to the device do not resolve the error, run the appropriate subtest in the Serial/Infrared Ports Test Group.
• If the software and the diagnostics do not recognize that you have a serial or infrared port, you should check the Serial/Infrared Port option in the System Setup program and, if necessary, run the appropriate subtest in the Serial/Infrared Ports Test Group.

Parallel Ports Test Group

The subtests in the Parallel Ports Test Group check the computer's interface with external devices, such as a printer, that are connected to the computer through a parallel port. The subtests in this test group are not intended as diagnostic tests for the actual peripheral attached to each port. (The only exception is a printer, as described in the following subsection.)

NOTE: If an external loopback connector is not attached to the parallel port, the Parallel External Loopback Test will fail for that port and the results of the test should be ignored.

Subtests

The four subtests in the Parallel Ports Test Group and the port functions they test follow:

• Parallel Internal Test

Checks several internal functions of the parallel port

• Parallel External Loopback Test

Tests the functionality of the control lines through an external loopback connector, if an external loopback connector is available

• Parallel External Interrupt Test

Tests the parallel port's ability to generate interrupts from all possible sources, if an external loopback connector or printer is available

• Parallel Printer Pattern Test

Tests a printer and tests the parallel port's ability to send a pattern to the printer, if a printer is connected

Why Run a Parallel Ports Test?

If the diagnostics does not recognize the computer's parallel port, enter the System Setup program and check the Parallel Port option to see if the port has been disabled. (See Chapter 4, "Using the System Setup Program," in the Dell PowerEdge 2300 Systems User's Guide for instructions.) The subtests in the Parallel Ports Test Group cannot test a port unless it is enabled.

When a port is faulty, it may not be immediately evident that the port, and not the device connected to the port, is faulty. Instead, the peripheral might behave erratically or not operate at all. If the external device is not properly installed through the software, it also may not function properly. Try operating the peripheral from different programs or through the operating system. If it still does not work, you can eliminate the software setup as the cause of the problem.

Another possible cause for errors is the external device. Use the documentation that came with the peripheral to troubleshoot the device and confirm that it is working properly. (Most printers have a self-test.)

After you eliminate incorrect system configuration information settings, peripheral malfunctions, and software errors as potential causes of port problems, you can run the subtests in the Parallel Ports Test Group to check the hardware. Although the following symptoms can be caused by faulty peripherals or software errors, they might also suggest a port problem:

• If a peripheral works intermittently or produces intermittent errors, the port may be faulty.
• If the computer displays an error message that is related to the external device connected to a port but corrections to the device do not resolve the error, run the appropriate subtest in the Parallel Ports Test Group.
• If the software and the diagnostics do not recognize that you have a parallel port, check the Parallel Port setting in the System Setup program and, if necessary, run the appropriate subtest in the Parallel Ports Test Group.

SCSI Devices Test Group

The subtests in the SCSI Devices Test Group check the functionality of up to four small computer system interface (SCSI) host adapters and all the SCSI devices attached to them.

NOTES: Before conducting these subtests on CD-ROM drives, insert a CD with audio and data tracks (such as a multimedia CD) into each CD-ROM drive. All of the subtests, except for the Audio Output Test, require a CD with data tracks. The Audio Output Test requires a CD with audio tracks. If a CD-ROM drive is empty or if it contains a CD that does not have the required data or audio tracks (depending on the subtest[s] being conducted), the subtest(s) will fail.

Subtests

The seven subtests in the SCSI Devices Test Group and the drive functions they test follow:

• Internal Diagnostic

Causes the device to run its internal self-test.

• Seek Test

Checks the device's ability to search for a specified track on the device and to position its read/write heads to all tracks.

• Read Test

Positions the read/write heads at each block of the device for reading data and verifies that all tracks on the device can be read correctly.

• Write Test

Positions the read/write heads at each block of the device for writing data and verifies that all tracks on the device can be written to correctly.

• Audio Output Test

Causes the CD-ROM drive to begin playing the first audio track on an audio CD. To determine whether the test passed, listen to the audio output of the drive.

NOTE: To conduct the Audio Output Test, you must select it individually. It will not run as part of the test group.

• Eject Removable Media

Causes a CD-ROM drive to eject its CD or a SCSI tape drive to eject its tape cartridge.

• Display Information

Displays a screen of information about each SCSI host adapter in the computer, the resources allocated to each SCSI host adapter, and a list of target devices attached to the SCSI host adapter.

Why Run a SCSI Devices Test?

If you check the SCSI hard-disk drive to determine the amount of available space, the operating system will probably report problem areas. Problem areas on hard-disk drives are common, because most hard-disk drives have a small amount of space that is not usable. The hard-disk drive keeps a record of this space so that the computer will not attempt to use it. Identification of unusable disk space, unless it is an unusually large amount (over five percent of the possible total), should not be regarded as a cause for testing the hard-disk drive.

These are the most common symptoms that might prompt you to test a SCSI device:

• A SCSI hard-disk drive fails during the boot routine.
• Seek errors are reported by the operating system or applications.
• An error message appears on the screen stating that the computer cannot read from or write to a SCSI device.
• Data on a SCSI device is corrupted or lost; this problem may be intermittent. Once saved by a program, files cannot be properly recalled.

Other Test Group

The subtests in the Other Test Group verify that the embedded server management (ESM) system is working properly. The ESM system interacts with the system BIOS and operating system to ensure that critical parameters, such as temperature, are monitored and that appropriate action is taken if a problem is detected.

Subtests

The three subtests in the Other Test Group and the functions they test follow:

• ESM Firmware Status

Tests to make sure the ESM software was downloaded correctly and that the system is operational.

• ESM Interface Test

Tests the interface between the host system and the ESM system to ensure that all bits in the data port function correctly.

• ESM Sensor Test

Verifies the current measurements of the ESM sensors.

Why Run an Other Test?

These are the most common symptoms that might prompt you to run the ESM subtests in the Other Test Group:

• If the Dell HIP server management application returns a warning dealing with server management
• If you want to verify that all voltages in the system are being reported properly

Back to Content Page