Jetson Xavier NX massflash /dev/sd* no medium found


We have 2 laptops each with with Ubuntu 18 and and Ubuntu 22. We hook up from the laptop USB port to a target PCBA that has a “Jetson Xavier NX SOM 16 GB eMMC” and a “Samsung SSD 500 GB V-NAND 970 EVO PCLE 3.0X4 NVME M1.3” both attached to the PCBA. Using any of the 2 computers we get an error that stops us from flashing successfully.

In the terminal (and we think always the log file too), we get the error:

“Error: Error opening /dev/sde: No medium found.”

We think it’s related to this line in “” or something adjacent:

if ls /dev/sd* 1> /dev/null 2>&1; then

It occurs shortly after the “Waiting for target to boot-up…” message. We could send a log if it will help.

When this occurs (it’s there one day, gone the next, back again, repeat…), the flash time goes from 20 minutes down to 3 to 5 minutes, and we get the FAILURES message from this block in “”:

if [ ${failure} -ne 0 ]; then
    echo "Flash complete (WITH FAILURES)";
    exit 1

Our basic flash command is the following (when it’s working we prepend with bash “time” and “ionice”):

sudo ./tools/kernel_flash/ --external-device nvme0n1 \ -c
-S 458GiB --showlogs --flash-only --massflash 5
–keep --showlogs \ jetson-xavier-nx-MASKED-emmc nvme0n1p1

Might you know the source of the error and how to permanently fix it?


Please have a Ubuntu 20.04 OS on laptop/PC to try for JetPack 5.x release. Thanks

Hi kayccc,

We have an Ubuntu 20 computer. Where do we go for JetPack 5.x? What are the steps to configure it? What are the steps to automate flashing of devices in production?


JetPack/SDK Manager are front ends to the actual flash software. The software being flashed is L4T. The two have their versions tied together, so you can consult either of these URLs to find the software and the docs which go with them:

Note that on the host PC you will install the sdkmanager package. Then you will run “sdkmanager” as a regular user (not sudo). It will ask for a login to the developer program. The Jetson is then attacked to the correct port in recovery mode, and you’ll pick what you want to do. Note that you can ignore installing components to the host PC if you want. Also, you can separate flash from package install (you can choose to only flash, and then at a later date choose to only install optional packages; these are separate steps and after flash the Jetson will automatically reboot and ask for first boot account setup prior to install over the network), just check or uncheck the parts you want. It will ask for your host PC password at some point when using host PC features which require sudo.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.