Sun Java Workstation W1100z and W2100z User Guide

This chapter assists you with using the Diagnostics section of the Sun Java Workstation W1100z and W2100z Supplemental CD that came with your system. If you are having specific problems with your system, use the Pc-Check Diagnostics software to diagnose and solve these issues.

The following sections are included in this chapter:

• Section 3.1, Diagnostics Main Menu
• Section 3.2, System Information Menu
• Section 3.3, Advanced Diagnostics
• Section 3.4, Immediate Burn-In Testing
• Section 3.5, Deferred Burn-In Testing
• Section 3.6, Create Diagnostic Partition
• Section 3.7, Show Results Summary
• Section 3.8, Print Results Report
• Section 3.9, About Pc-Check
• Section 3.10, Exit to DOS

---

3.1 Diagnostics Main Menu

To access the Pc-Check Diagnostics Main Menu:

1. Insert the Sun Java Workstation W1100z and W2100z Supplemental CD into your CD-RW drive and reboot the system.

The system boots to the Sun Java Workstation W1100z and W2100z Supplemental CD Main Menu.

2. Type 1 to run the Hardware Diagnostics Software.

The system information loads, then the Diagnostics Main Menu opens and the following menu options are displayed:

• System Information Menu
• Advanced Diagnostics Tests
• Immediate Burn-in Testing
• Deferred Burn-in Testing
• Create Diagnostic Partition
• Show Results Summary
• Print Results Report
• About PC-CHECK
• Exit to DOS

---

3.2 System Information Menu

TABLE 3-1 describes each option in the System Information menu.

---

3.3 Advanced Diagnostics

TABLE 3-2 gives the name and a brief description of each option in the Advanced Diagnostics Tests Menu.

3.3.1 Hard Disk Testing

To test the hard disk:

1. From the Main Menu, choose Advanced Diagnostics Tests.

2. From the Advanced Diagnostics Menu, choose Hard Disks.

3. From the Select Drive Menu, choose the hard disk you are testing.

The Hard Disk Diagnostics screen opens, showing both the information for the hard disk you have selected and the Hard Disk Tests Menu.

Within the Hard Disk Tests Menu, there are the following options:

• Select Drive
• Test Settings
• Read Test
• Read Verify Test
• Non-Destructive Write Test
• Destructive Write Test
• Mechanics Stress Test
• Internal Cache Test
• View Error Log
• Utilities Menu
• Exit

The Media Test options include the Read Test, the Read Verify Test, the Non-Destructive Write Test, and the Destructive Write Test. These tests are relevant to testing the media associated with the hard drive hardware, such as the physical disk.

Caution - Running the Destructive Write Test destroys any data that is on the disk.

The Device Test options include the Mechanics Stress Test and the Internal Cache Test. These tests are relevant to testing nonmedia-related devices associated with the hard drive hardware, such as the head and internal cache.

As well as choosing any of these tests, you can also define several parameters of the test.

You can change the parameters within the Test Settings option. Your options within Test Settings include the following:

• Media Test Settings

Enables you to choose the test time duration, the percentage of the hard disk to test, and the sectors to be tested on the hard disk.

• Device Test Settings

Enables you to select the test time durations of the devices and the test level.

• Number of Retries

Enables you to select the number of times to retry testing a device before terminating the test.

• Maximum Errors

Enables you to select the number of errors allowed before terminating the test.

• Check SMART First

SMART stands for Smart Monitoring Analysis Reporting Test.

• HPA Protection

HPA stands for Host Protected Area.

• Exit

---

3.4 Immediate Burn-In Testing

The Immediate Burn-In Testing option enables you to run burn-in test scripts on your workstation. Three scripts have already been created for testing your system:

• quick.tst - Performs a quick overview test to determine the operating status of your system. This test can take up to twenty minutes and requires some user input.
• noinput.tst - Performs a quick overview test to determine the operating status of your system. This test does not require user input. The time for this test varies according to how much memory is in the system. It can take up to one hour and twenty minutes.
• full.tst - Performs a complete test on all components to determine the operating status of your system. This test can take several hours, depending upon your system configuration.

When you choose the Immediate Burn-in Testing menu option, the Continuous Burn-in Testing screen opens. The screen includes the list of options shown in TABLE 3-3 for running the tests. When a quick.tst, noinput.tst or full.tst script is loaded, the defaults indicated in the third column are automatically loaded

:

To load one of the scripts available to test the devices on your system, do the following:

From the Main Menu, choose Immediate Burn-in Testing.

The top portion of the screen lists the option described in TABLE 3-3, and the bottom portion of the screen lists the Burn-in Menu options described below.

• Load Burn-in Script

Enter one of the following:

• quick.tst, noinput.tst, or full.tst
• If you have created and saved your own script, enter d:\testname.tst

Where testname is the name of the script that you have created.

• Save Burn-in Script

To save a burn-in script that you have created, enter d:\testname.tst

Where testname is the name of the script that you have created.

• Change Options

Opens the Burn-in Options menu, which enables you to modify the various options listed in TABLE 3-3 for the currently loaded test script.

• Select Tests

Opens a listing of the tests available for your workstation configuration to run for the currently loaded test script.

• Perform Burn-in Tests

Starts to run the currently loaded burn-in test script.

---

3.5 Deferred Burn-In Testing

Deferred Burn-in Testing allows you to create and save your own scripts to run at a later time.

From the Main Menu, choose Deferred Burn-in Testing.

The top portion of the screen lists the option described in TABLE 3-3, and the bottom portion of the screen lists the Burn-in Menu options described below.

• Load Burn-in Script

Enter one of the following:

• quick.tst, noinput.tst, or full.tst
• If you have created and saved your own script, enter d:\testname.tst

Where testname is the name that you have created.

• Save Burn-in Script

To save a burn-in script that you have created, enter d:\testname.tst

Where testname is the name of the script that you have created.

• Change Options

Opens the Burn-in Options menu, which enables you to modify the various options listed in TABLE 3-3 for the currently loaded test script.

• Select Tests

Opens a listing of all of the possible types of tests available for you to run for the currently loaded test script.

---

3.6 Create Diagnostic Partition

The Create Diagnostic Partition option will install a diagnostic partition on the first bootable disk seen by the Sun Java Workstation W1100z or W2100z platform.

On an IDE system, the first bootable disk is on the primary/master IDE device. On a SCSI system, the first bootable disk is the first disk found on the SCSI A channel. If a disk is not found on the SCSI A channel, then it will search the SCSI B channel for the first hard disk found.

The following subsections explain how to create and access the diagnostic partition on the Sun Java Workstation W1100z and W2100z:

• Removing Existing Partitions on a Hard Disk
• Adding a Diagnostic Partition to the First Bootable Disk
• Creating a Log File on the Diagnostic Partition
• Accessing the Diagnostic Partition Under Red Hat Linux
• Accessing the Diagnostic Partition Under Solaris x86
• Accessing the Diagnostic Partition Under Windows

3.6.1 Removing Existing Partitions on a Hard Disk

The Create Diagnostic Partition option will only create a diagnostic partition on a hard disk if that hard disk is completely empty of any partitions. You will need to delete any existing partitions on a hard disk if you plan on using the hard disk to create a diagnostic partition on it.

Caution - Removing all hard disk partitions will destroy all data on the disk.

You can clear the partitions using the following procedure:

1. Insert the Supplemental CD into the CD-RW/DVD-ROM tray.

2. Reboot the workstation.

3. At the Supplemental CD Main Menu, type 3 to exit to DOS.

4. Type fdisk at the command prompt and press the Enter key.

5. Type 4 to select alternate fixed disk.

The second hard disk as seen from fdisk is the first bootable disk of the system. The first hard disk as seen from fdisk is the bootable Supplemental CD.

Caution - When performing the following tests, be careful not to delete any operating system partitions that you want to keep. Removing hard disk partitions will destroy all data on the disk.

6. Type 2 to Delete DOS partition.

7. Type 1 or 2 depending on the type of partition you want to delete.

8. Type the number of the partition you want to delete.

9. Type Y to erase the data and the partition.

10. Repeat Step 6 through Step 9 until all partitions have been removed.

11. Press the Esc key to exit and strike any key to reboot the workstation.

3.6.2 Adding a Diagnostic Partition to the First Bootable Disk

Pc-Check can only view the first or second hard disk on the system from the boot loader. The software automatically installs the diagnostic partition on the first bootable disk. To add the diagnostic partition on the first bootable disk:

1. Insert the Supplemental CD into the CD-RW/DVD-ROM tray.

2. Reboot the workstation.

3. At the Supplemental CD Main Menu, type 1 to run Hardware Diagnostics.

4. Select Create Diagnostic Partition at the Main Menu.

• If the first bootable disk is clear of partitions then the Sun Microsystems Partitioning Utility window will appear. It states: Your primary hard disk is not partitioned. Would you like to partition it now?
• Select Yes and press Enter.
• A window will appear stating, Partitioning complete. Your machine will now be restarted.

• If the first bootable disk is not clear of partitions then a window will appear stating that it is unable to create a hardware diagnostic partition because there are already partitions on the disk.
• If this happens, then go to Section 3.6.1, Removing Existing Partitions on a Hard Disk to clear the partitions from the disk.
• Repeat Step 1 through Step 4 of this procedure.

5. Press Enter to reboot your workstation.

3.6.3 Creating a Log File on the Diagnostic Partition

All the scripts that are loadable with the hardware diagnostics software come predefined with logging to the Diagnostic Partition enabled. The names of log files will correspond to the name of the script. For example, a script named noinput.tst will create a log file named noinput.jrl.

The following instructions show an example of how to create and access a log file on the diagnostic partition for the noinput.tst script:

1. Insert the Supplemental CD into the CD-RW/DVD-ROM tray.

2. Reboot the workstation.

3. At the Supplemental CD Main Menu select 1 to run Hardware Diagnostics.

4. At at the Hardware Diagnostics Main Menu select Immediate Burn-In Testing.

5. Select the Load Burn-in Script.

6. Type noinput.tst and press Enter.

If you are using a test you have created yourself, you will need to enter
d:\testname.tst into the Load Burn-in Script field.

Where testname is the name of the test you have created.

7. Select Perform Burn-in Tests to run the script.

8. When the tests have completed, press the Esc key to exit the Display Results window.

9. Select Exit to DOS and press Enter.

10. At the DOS prompt, type the following:

C:> d:

11. Type the following to list the contents of the Diagnostic Partition.

D:> dir

The noinput.jrl log will appear.

3.6.4 Accessing the Diagnostic Partition Under Red Hat Linux

To access the diagnostic partition when you are running a Red Had Linux operating system:

1. Remove the Supplemental CD from the CD-RW/DVD-ROM tray.

2. Reboot the workstation and start the Linux Red Hat operating system.

3. Become superuser.

4. Determine if your diagnostic partition has been configured to be mounted by typing the following command:

# ls /diagpart

• If this command fails to list the log files created by the hardware diagnostics software then the operating system has never been configured to mount the diagnostic partition. Continue to Step 5.
• If this command succeed in listing the log files created by the hardware diagnostics software, then the operating system has already been configured to mount the diagnostic partition. All users have read access to this partition. Only the super user has read/write access to this partition. You do not need to continue this procedure.

5. Insert the Supplemental CD into the CD-RW/DVD-ROM tray.

6. When the CD is mounted, open up a terminal window.

7. Type the following command:

# cd /mnt/cdrom/drivers/linux/red_hat

8. Type the following to install the diagnostic partition:

# ./install.sh

9. Press Enter.

The following lines appear if the diagnostic partition is mounted successfully:

Mounting Diagnostic Partition

Installation Successful

10. Type the following command:

# ls /diagpart

This will list the contents of the diagnostic partition.

3.6.5 Accessing the Diagnostic Partition Under
Solaris x86

To access the diagnostic partition when you are running a Solaris x86 operating system:

1. Remove the Supplemental CD from the CD-RW/DVD-ROM tray.

2. Reboot the machine and start Solaris x86.

3. Become superuser.

4. Determine if your diagnostic partition has been configured to be mounted by typing the following command:

# ls /diagpart

• If this command fails to list the log files created by the hardware diagnostics software then the operating system has never been configured to mount the diagnostic partition. Continue to Step 5.
• If this command succeed in listing the log files created by the hardware diagnostics software, then the operating system has already been configured to mount the diagnostic partition. All users have read access to this partition. Only the super user has read/write access to this partition. You do not need to continue this procedure.

5. Insert the Supplemental CD into the CD-RW/DVD-ROM tray.

6. When the CD is mounted open up a terminal window.

7. Type the following:

# cd /cdrom/cdrom0/drivers/sx86

8. Type the following to install the diagnostic partition:

# ./install.sh

9. Press the Enter key.

The following lines should appear if the diagnostic partition is mounted successfully:

Mounting Diagnostic Partition

Installation Successful

10. Type the following command to list the contents of the diagnostic partition:

# ls /diagpart

3.6.6 Accessing the Diagnostic Partition Under Windows

The Windows operating system does not allow the mounting of a diagnostic partition. There is no way to view or gain access to the diagnostic partition if you are running Windows on a Sun Java Workstation W1100z or W2100z.

The only way to retrieve the contents (log files) on the diagnostic partition is to attach a USB floppy drive to the Sun Java Workstation W1100z or W2100z and complete the following procedure:

1. Insert the USB floppy drive into any USB port on the Sun Java Workstation W1100z or W2100z.

2. Insert the Supplemental CD into the CD-RW/DVD-ROM tray.

3. Reboot the workstation.

4. At the Supplemental CD Main Menu, type 3 to exit to DOS.

5. Type the following at the DOS command prompt:

C:> d:

6. To copy file a file named noinput.jrl to the USB floppy drive, type:

D:> copy d:\noinput.jrl a:\

The journal file is now saved to the floppy diskette in the USB floppy drive.

---

3.7 Show Results Summary

The summary lists the tests run and shows the results. Either Pass, Fail or N/A is listed for each option.

The following list is a complete listing of all possible options available with the Supplemental CD. If your own system does not have all of these options, they might not show up when the Show Results Summary displays.

• Processor

This section shows the following tests conducted against the processor: Core Processor Tests, AMD 64 Bit Core Tests, Math Co-Processor Tests - Pentium Class FDIV and Pentium Class FIST, MMX Operation, 3DNow! Operation, SSE Instruction Set, SSE2 Instruction Set, and MP Symmetry.

• Motherboard

This section shows the following tests conducted against the motherboard: DMA Controller Tests, System Timer Tests, Interrupt Test, Keyboard Controller Tests, PCI Bus Tests, and CMOS RAM/Clock Tests.

• Memory, Cache Memory, and Video Memory

This section shows the following tests conducted against the various types of memory: Inversion Test Tree, Progressive Inv. Test, Chaotic Addressing Test, and Block Rotation Test.

• Input Device

This section shows the following tests conducted against the input device: Verify Device, Keyboard Repeat, Keyboard LEDs, and Turbo Switch .

• Mouse

This section shows the following tests conducted against the mouse: Buttons, Ballistics, Text Mode Positioning, Text Mode Area Redefine, Graphics Mode Positions, Graphics Area Redefine, and Graphics Cursor Redefine.

• Video

This section shows the following tests conducted against the video: Color Purity Test, True Color Test, Alignment Test, LCD Test, and Test Cord Test.

• Printer

The Verify Output test is conducted against the printer.

• Multimedia

This section shows the following tests conducted against the multimedia components: Internal Speaker Test, FM Synthesizer Test, PCM Sample Test, CD/DVD Drive Read Test, CD/DVD Transfer (KB/Sec), CD/DVD Transfer Rating, CD/DVD Drive Seek Test, CD/DVD Seek Time (ms), CD/DVD Test Disk Read, and CD/DVD Tray Test.

• ATAPI Devices

This section shows the following tests conducted against ATAPI devices: Linear Read Test, Non-Destructive Write, and Random Read/Write.

• Floppy Disk

This section shows the following tests conducted against the floppy disk: Linear Read Test, Write Protect Test, Non-Destructive Write, and Random Read/Write.

• Hard Disk

This section shows the following tests conducted against the hard disk: Read Test, Read Verify Test, Non-Destructive Write Test, Destructive Write Test, Mechanics Stress Test, and Internal Cache Test.

• Serial Port

This section shows the following tests conducted against the serial port: IRQ Test, Line Control Test, Handshake Test, Loopback Test, and Internal FIFO Test.

• Modem

This section shows the following tests conducted against the modem: Data Collection, Register Test, Loopback Test, Carrier Test, and Dial Tone Test.

• Parallel

This section shows the following tests conducted against the parallel: Verify Controller, Check Status Port, and Interrupt Test.

• USB

This section shows the following tests conducted against the USB: Controller Tests and Functional Tests.

• Hardware ID

The compare test is used to determine the machine ID for the system. This test is not available for the Sun Java Workstation W1100z and W2100z.

---

3.8 Print Results Report

This option enables you to print results of the diagnosis of your system.

Ensure that your workstation is connected to a printer, then enter the required information to print the results.

---

3.9 About Pc-Check

This screen includes general information about Pc-Check software, including resident and non-resident components, such as mouse devices.

---

3.10 Exit to DOS

This option exits Pc-Check and returns you to the DOS prompt.

Sun Java Workstation W1100z and W2100z User Guide

817-6585-12

Copyright © 2004, Sun Microsystems, Inc. All Rights Reserved.