# Looking out for nvidia-diagnostic-local-repo-ubuntu

**URL:** <https://forums.developer.nvidia.com/t/looking-out-for-nvidia-diagnostic-local-repo-ubuntu/269133>\
**Category:** DGX Systems (DATA CENTER)\
**Created:** [October 11, 2023, 10:17am UTC](https://forums.developer.nvidia.com/t/looking-out-for-nvidia-diagnostic-local-repo-ubuntu/269133 "2023-10-11T10:17:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![shan\_8992](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shan\_8992](https://forums.developer.nvidia.com/u/shan_8992)\
**Post date:** [October 11, 2023, 10:17am UTC](https://forums.developer.nvidia.com/t/looking-out-for-nvidia-diagnostic-local-repo-ubuntu/269133/1 "2023-10-11T10:17:44Z")

</div>

I would like to perform EUD testing [Extended Utility Diagnostics (EUD) — NVIDIA DCGM Documentation latest documentation](https://docs.nvidia.com/datacenter/dcgm/latest/user-guide/dcgm-eud.html)

However, I couldn’t find the package to install nvidia-diagnostic [DCGM Diagnostics — NVIDIA DCGM Documentation latest documentation](https://docs.nvidia.com/datacenter/dcgm/latest/user-guide/dcgm-diagnostics.html#installing-the-eud-packages)

Requesting to share link to download nvidia-diagnostic for ubuntu 22.04, current environment has `nvidia-driver-535`

---

<div class="post-metadata">

**Author:** ![acesse780829](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@acesse780829](https://forums.developer.nvidia.com/u/acesse780829)\
**Post date:** [June 28, 2026, 1:54pm UTC](https://forums.developer.nvidia.com/t/looking-out-for-nvidia-diagnostic-local-repo-ubuntu/269133/2 "2026-06-28T13:54:51Z")

</div>

Sharing our actual workflow for obtaining and deploying EUD packages in an air-gapped environment

We ran into the exact same issue during GB300 platform validation — the `nvidia-diagnostic` packages aren’t reachable through standard channels in an air-gapped setup, and `/usr/share/nvidia/diagnostic/` doesn’t get created automatically either.

Here’s the three-step workflow that worked for us:

**1. Extract the nested package**  
The EUD package itself is wrapped inside a local-tegra-repo .deb structure, so you need to extract the inner repo first, then extract the actual binaries from there:

```auto
mkdir -p ./eud_temp && dpkg-deb -x nvidia-diagnostic-local-tegra-repo-ubuntu2404-580.126.12-mode1_1.0-1_arm64.deb ./eud_temp
cd ./eud_temp/var/nvidia-diagnostic-local-tegra-repo-ubuntu2404-580.126.12-mode1/
mkdir -p ./binary && dpkg-deb -x nvidia-diagnostic-580_580.126.12-1_arm64.deb ./binary

```

**2. Manually create the target directory and inject the files**  
This directory doesn’t exist by default, so you have to create it yourself:

```auto
sudo mkdir -p /usr/share/nvidia/diagnostic
cd ./binary/usr/share/nvidia/diagnostic && sudo cp -r ./* /usr/share/nvidia/diagnostic/

```

**3. Confirm MIG mode is disabled before running the deep diagnostic**  
The EUD deep stress test (`dcgmi diag -r eud`) needs full, unpartitioned GPU access:

```auto
sudo nvidia-smi -mig 0
sudo dcgmi diag -r eud -p "eud.passthrough_args='gpu_diag'"

```

This completely bypassed the installation issue in our environment, and the EUD deep test itself runs for over 10 hours — it’s what we use as the formal basis for hardware RMA determination.

Hope this helps anyone running into the same situation.