KB 118007 - NVIDIA Field Diagnostics Test (FDIAG) Tool for Validating H100/H200

KB 118007 - NVIDIA Field Diagnostics Test (FDIAG) Tool for Validating H100/H200


FDIAG
NVIDIA’s Field Diagnostics Test Tool (FDIAG)is an offline hardware test tool for GPU health test. Mainly used in RMA workflow and tool is not provided to public for download. They are distributed through OEMs or directly from NVIDIA support as part of service. It covers log generation, FDIAG execution, and log collection for RMA or system verification.

Prerequisites

  • Portable bootable USB (Service OS)
  • USB hub
  • USB data stick for log collection
  • Keyboard and monitor (can be removed after FDIAG starts)

Step 1: Boot into Service OS

  1. Connect the following:

        Bootable Ubuntu USB stick
        USB hub
        USB data stick for Collecting Log
  2. Power on or restart the system.
  3. Press F11 to access the Boot Menu.
  4. Select the portable USB stick and boot into Service OS (Ubuntu). If USB Stick is not visible, go to BIOS and change the boot settings UEFI to dual mode. After Complete the test change back to UEFI mode.
  5. Log in using the following credentials:
    Username: service
    Password: 1234

 

Step 2: Initial GPU & System Verification

Perform the following checks before starting FDIAG.

1. Verify GPU Detection

nvidia-smi

2. Create GPU Serial Number List

nvidia-smi -q | grep -i serial >> nvidiaserials.txt

3. View GPU Serial Numbers

vi nvidiaserials.txt

 

4. Verify GPU VBIOS Firmware

nvidia-smi -q | grep -i Vbios

5. Verify BIOS and BMC Versions

sudo ./IPMICFG-Linux.x86_64 -summary

Step 3: Running NVIDIA Field Diagnostics (FDIAG)

  1. Change directory to the H100 folder:

Type - cd H100 to change into H100 folder. You can run ls to confirm that the Python script is available.

  1. Start FDIAG:

Type - python3 run.py

  1. Select the system type:

Option 1 – Intel system

Option 2 – AMD system

  1. Select the test mode:

Option 4 – RMA

Option 5 – System Validation

  1. Wait until the DGX FIELD DIAGNOSTIC messages appear

 

  1. Once FDIAG has started we can safely remove Keyboard and monitor

Important Notes

  • H100 / H200 FDIAG runtime: Approximately 75–90 minutes
  • A100 FDIAG runtime: Approximately 5 hours
  • Always start the sequence as: 
              For Intel Systems start 1 to 4/.5
              For AMD Systems start 2 to 4/5

Once FDIAG begins, you cannot return to generate logs. PASS or FAIL Screen will appear once test finished.
FAIL Screen Image is Attached

 

Step 4: Log Collection After FDIAG Completion

1. Verify All Drives
           Type - lsblk

2. Identify Data USB
             Typically identified as sdb/sdd

3. Mount the USB Partition
         Type -sudo mount /dev/sdb1 /media/usb/

4. Copy or Move Logs
Copy or move the System Serial Number folder to the USB:
       Type - sudo cp -r <System_Serial_Number_Folder> /media/usb OR Type - sudo mv <System_Serial_Number_Folder> /media/usb

5. Synchronize Data
     Type - sync

6. Verify USB Contents
        Type - cd /media/usb
         ls (or) dir -i

Step 5: USB Removal and Upload

  1. Unmount the USB safely: 
    Type - sudo umount /media/usb/

  1. Remove the USB data stick.
  2. Connect it to your laptop.
  3. Upload the collected folder to the shared drive / Box folder.
  4. Shut down Ubuntu OS and remove all USB devices.

 

 


    • Recent Articles

    • KB-630208 | How to use Find and Locate to search for files in Linux

      Purpose To provide Linux administrators and Field Engineers with guidance on using the find and locate utilities to efficiently search for files and directories within a Linux filesystem based on criteria such as name, type, size, timestamps, ...

    • KB-630164 | How to use rsync to Synchronize Files

      Purpose To provide a clear and practical procedure for using the rsync utility to synchronize files and directories between local systems and remote hosts, including push and pull operations, while preserving file attributes and optimizing data ...

    • KB-630107 | How to create a Linux swap file

      Purpose To provide Field Engineers and Linux administrators with a standardized procedure for creating, configuring, and validating a Linux swap file. This procedure helps ensure sufficient virtual memory is available when physical RAM is exhausted ...

    • MSI All-in-One (AIO) PC – Physical Damage Policy for Warranty Claims

      MSI All-in-One (AIO) PC – Physical Damage Policy for Warranty Claims MSI's standard warranty does not cover physical or accidental damage to an All-in-One (AIO) PC. If the damage is determined to be caused by external factors rather than a ...

    • KB 134833 - Troubleshooting NVSM Alert NV-CPU-XX – Unrecoverable CPU Internal Error

      Purpose This document provides a general troubleshooting procedure for the NVIDIA System Management (NVSM) alert NV-CPU-XX, which indicates that a CPU has reported an internal error. The article outlines how to verify whether the alert represents an ...

    • Popular Articles

    • CP Plus Camera and NVR Configuration

      NVR Configuration The CP Plus Pro Series of NVRs have been meticulously designed for providing you with upgraded performance and higher recording quality in your IP video surveillance solution. The robust processor that has been inculcated in this ...

    • KB 775235 - Kerberos Authentication – Overview

      What is Kerberos? Kerberos is a secure authentication method used in our Active Directory (AD) environment (mbuzztech.com). It allows users to: Access multiple systems without re-entering passwords (Single Sign-On – SSO) Log in once Where We Use It ...

    • How to Remove and Reinstall NVIDIA Drivers on Ubuntu

      This article provides step by step guide to completely remove existing NVIDIA drivers and reinstall specific version of the NVIDIA driver on the Ubuntu system Prerequisites Administrative (sudo) access to the Ubuntu system. Internet access to ...

    • KB 692001 - Personal Computers and Servers - Classification and Point of Contact

      We can classify the computers that MBUZZ handles based on their form-factor as below: Tower Workstations, Desktops, Gaming PCs and SFF (Small form factor) PCs fall under this category. These are computers people would use on a desk and rarely move. ...

    • KB 298031 - M.2 SSD Tier List

      The sequential read and write speeds, which are usually the most advertised number, are not a proper benchmark of real-world performance or the quality of an SSD. This article categorizes and tiers SSDs based on factors like the type of NAND flash, ...