About This Documentation (PDF and HTML)
Introduction to Diagnostic Tools
Diagnostic Tools for Oracle Servers
Using the Diagnostic Tools to Troubleshoot a Server
U-Boot Diagnostic Startup Tests
U-Boot Diagnostic Startup Tests Overview
Running the U-Boot Diagnostic Tests
Sample SP Environmental Variables Showing U-Boot Test Status
Accessing Pc-Check Diagnostics Utility
Create Diagnostic Partition Menu Option
How to Remove Existing Partitions From a Hard Disk
How to Add a Diagnostic Partition to the First Bootable Disk
How to Access the Diagnostic Partition on a Red Hat Linux System
How to Access the Diagnostic Partition on the Oracle Solaris 10 Operating System
How to Access the Diagnostic Partition on the Windows Server 2003 Operating System
Accessing the Pc-Check Diagnostics Utility on the Tools and Drivers CD/DVD
How to Access and Run Pc-Check From the Tools and Drivers CD/DVD
How to Access and Run Pc-Check From a USB Device
How to Set Up the Tools and Drivers CD/DVD Image on the PXE Server
How to Access the Tools and Drivers CD/DVD From the Target Server
All the scripts that are loadable with the hardware diagnostics utility are predefined, with logging to the diagnostic partition enabled. The names of log files correspond to the name of the script. For example, a script named noinput.tst creates a log file named noinput.jrl.
The following procedure shows an example of how to create and access a log file on the diagnostic partition for the noinput.tst script.
If you are using a test you have created yourself, enter d:\testname.tst into the Load Burn-in Script field, where testname is the name of the test you created.
C:> d:
D:> dir
The noinput.jrl log appears.