Jetpack 6.2 / L4T 36.4.3 - Orin Nano and NX won't boot after flashing NVME

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
,
1

We are having trouble flashing both the Nano and NX devkits with the latest Jetpack/L4T. Everything worked just fine on 36.4.0 and now the same commands result in errors during bootup after flashing the NVME. We get

mount /mnt: can't find PARTUUID=7231cb5e...

and then the device reboots.

Things we tried that did not work

  • Flash without ROOTFS_AB (the ‘default’ case in the instructions)
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p "-c ./bootloader/generic/cfg/flash_t234_qspi.xml" -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit external
  • Flash with ROOTFS_AB enabled
# Generate images for QSPI
$ sudo ROOTFS_AB=1 ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" --no-flash --network usb0 jetson-orin-nano-devkit internal

# Generate images for external storage device
$ sudo ROOTFS_AB=1 ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --no-flash --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_t234_nvme_rootfs_ab.xml --external-only --append --network usb0 jetson-orin-nano-devkit external

# Flash images into the both storage devices
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --network usb0 --flash-only
  • Swap the SSD
  • Try on an NX instead of a NANO

The flash log is here:
36.4.3-flash_5-2_0_20250219-132536.log (48.0 KB)

1 Like
3

Hi,

Please record the serial console log during the bootup.
To record the serial console log, please refer below link.

Thanks

4

Thanks, I’m waiting for an FTDI to arrive. In the meantime I managed to flash the SDCard on a Nano Devkit and use it to try and see what’s wrong with booting from the NVMe.

I re-flashed both the NVMe and the SD Card with a minimal rootfs per Root File System — NVIDIA Jetson Linux Developer Guide 1 documentation

SD Card

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device mmcblk0p1 \
  -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
  --showlogs --network usb0 jetson-orin-nano-devkit internal

NVME

sudo ROOTFS_AB=1 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_t234_nvme_rootfs_ab.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" --showlogs --network usb0 jetson-orin-nano-devkit internal

After running lsblk -o NAME,PARTUUID when booting from the SD Card I can see that all of the 16 required partitions (nvme0n1p1-16) are around and have the correct UUIDs - but booting from the NVME still fails to find and mount the existing partition.

5

Hi,

Got it.
Please execute below commands and share result with us

 cat /boot/extlinux/extlinux.conf

Thanks

6

Hey David,

I found the issue - it was related to the minimal flavor rootfs. It looks like there is a failure that bobbles up when running ./apply_binaries.shand later causes a broken boot. It invokes nv_tegra/nv-apply-debs.sh which fails because the following two debs are not around in the minimal flavor

  • nvidia-l4t-jetsonpower-gui-tools
  • nvidia-l4t-nvpmodel-gui-tools

Steps to reproduce are:

For us this reproducably caused a broken Orin. I had to patch nv_tegra/nv-apply-debs.sh to get it to work.

7

Hi,

Thank you for your finding.
It seems like a bug.
We need to reproduce it to confirm and file the patch to fix in next release.

Could you provide the patch for us to try?

Thanks

8

Sure, I inserted this bit at line 227 of nv_tegra/nv-apply-debs.sh:

deb_skiplist+=("nvidia-l4t-jetsonpower-gui-tools")
deb_skiplist+=("nvidia-l4t-nvpmodel-gui-tools")

Not sure if this would break the existing sample_fs build or if you’d need to add another flag.