JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle x86 Server Diagnostics Guide
search filter icon
search icon

Document Information

Preface

Related Documentation

About This Documentation (PDF and HTML)

Typographic Conventions

Documentation Comments

Change History

Diagnostics Guide

Introduction to Diagnostic Tools

About 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

System Diagnostic Test Options at Startup

U-Boot Diagnostic Test Modes-Normal, Quick, and Extended

Reporting Diagnostic Failures at System Startup

Running the U-Boot Diagnostic Tests

Sample U-Boot Test Output

Sample SP Environmental Variables Showing U-Boot Test Status

Pc-Check Diagnostics Utility

Pc-Check Diagnostics Overview

Accessing Pc-Check Diagnostics Utility

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

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

Index

Reporting Diagnostic Failures at System Startup

After U-Boot completes the diagnostic test, the test output and a final status of the U-Boot test appears on your screen. If a hardware failure is detected by U-Boot, the failure is reported in the test output. To view samples of the U-Boot test outputs, see Sample U-Boot Test Output.


Note - For troubleshooting purposes, a -Failed or -Passed status of the last U-Boot test performed on the server is also stored in the SP environmental variables. To view a sample output of the environmental variables showing the status of the U-Boot test, see Example 4.


When troubleshooting your system, note that the symptoms of a diagnostic failure can vary depending on whether the diagnostics at startup have failed on the server SP or host. For additional details about how to determine where the diagnostics failed at startup and possibly locate additional information about the failure, see the following table.

Component
Failure Status and Symptoms
Server SP

(U-Boot)

  • When the component failure is detected on the server SP, the failure is typically reported in the following locations:

    – U-Boot test results

    For sample output of U-Boot test results, see Sample U-Boot Test Output .

    – ILOM event log.

    For details about how to access this log, refer to the information about the ILOM event log in the Oracle Integrated Lights Out Manager 3.0 User’s Guide.

    – Fault Management tab in the ILOM web interface

    For more details about access and use of fault management, refer to the information about ILOM fault management in the Oracle Integrated Lights Out Manager 3.0 User’s Guide. To determine which faults you must manually clear on your server, refer to the platform ILOM Supplement Guide for your server.

  • If a component failed to start, the Service Action Required LED on the front panel of the server illuminates.

  • If the U-Boot diagnostic test failed, the server SP will not start.

Server Host (BIOS POST)
  • When the component failure is detected on the server host, the failure is typically reported in the following locations:

    – Fault Management tab in the ILOM web interface

    For more details about access and use of fault management, refer to the information about ILOM fault management in the Oracle Integrated Lights Out Manager 3.0 User’s Guide. To determine which faults you must manually clear on your server, refer to the platform ILOM Supplement Guide for your server.

    – ILOM event log.

    For details about how to access this log, refer to the information about the ILOM event log in the Oracle Integrated Lights Out Manager 3.0 User’s Guide.

  • If a component failed at startup, the Service Action Required LED on the front panel of the server illuminates.

  • If the BIOS POST detected a fatal error, the host operating system will not start.