Go to main content

Oracle® x86 Servers Diagnostics and Troubleshooting Guide

Exit Print View

Updated: January 2020
 
 

Run UEFI Diagnostics Manually (CLI)

This task provides instructions for running UEFI diagnostics manually from the CLI through the host console.

  1. Power off the server:
    1. Type stop -f /SYS.
    2. To stop the system, type y.

      The System OK LED on the front panel is blinking.

  2. Start a serial console redirection:
    1. Log in to the Oracle ILOM command-line interface (CLI) as root.
    2. Type start /HOST/console.
    3. To start the host console, type y.
  3. To change the directory to /HOST/diag, type cd /HOST/diag.
  4. To set manual mode, type set mode=manual.
  5. Start the UEFI diagnostics.
    1. Type start /HOST/diag.
    2. To start the UEFI diagnostic, type y.

    The server automatically boots the UEFI shell. No more action is necessary.


    Note -  As UEFI diagnostics boot, you might see messages stating that you can use function keys to interrupt the boot process. These messages do not apply to UEFI diagnostics. Do not press any function keys when starting the UEFI diagnostics.

    The system displays boot messages, and displays the following startup messages.

    FS0:\> echo -off
    
    Oracle Enterprise UEFI Diagnostics
    
    Diagnostics tool found at drive FS0:
    UEFI Diagnostics x8_8A v1.2.1332
    Production Rel.
    
    Last Changed Rev: 1332
    Last Changed Date: 2018-04-26 11:40:28 -0700 (Tue, 26 February 2019)
    
    02/26/2019
    05:24:36 (LOCAL)
    
  6. To view the progress of the diagnostic tests in Manual mode, type show /HOST/diag status.

    The Diagnostics Status field indicates the progress of the diagnostic tests.

  7. To display the available commands, type udiag -hv.
  8. Stop the diagnostic tests.
    1. Type stop /HOST/diag.
    2. To stop the UEFI diagnostics, type y.

    Caution

    Caution  -  If there is an unexpected AC power cycle and a test is in progress, configure Diagnostics mode again starting from Step 1. Internal variables could be corrupted and setting a new mode or resetting the same mode fixes any potential issue.


  9. To resume running the diagnostic tests, type start /HOST/diag.

    Note -  To check the history of the test using Oracle ILOM Event logs, type: show /SP/logs/event/list/ type==diags.
  10. To finish the Diagnostics activities, type set /HOST/diag/ mode=disabled.