Hi all,
I’ve been trying to flash Jetson AGX Orin 64 GB devkit on a 1TB NVMe using JetPack 5.1.2 on Ubuntu 20.04.6 LTS (focal), and I keep running into the following issue during the flashing process:
ERROR: Flash Jetson Linux - flash: Error: Invalid argument during seek for read on /dev/mmcblk0
ERROR: Flash Jetson Linux - flash: [ 9]: l4t_flash_from_kernel: Error: partprobe failed. This indicates that:
- the xml indicates the gpt is larger than the device storage
- the xml might be invalid
- the device might have a problem.
System Setup:
-
Host Machine: Alienware Aurora R16
-
OS: Ubuntu 20.04.6 LTS
-
CPU: Intel i9-14900KF (32 cores, 24 threads)
-
RAM: 32GB
-
JetPack Version: 5.1.2
-
SDK Manager Version: 2.2.0 12028 x86_64
-
Target Device: Jetson AGX Orin 64GB DevKit
-
Flashing Command Used:
sudo ./flash.sh jetson-agx-orin-devkit nvme0n1
-
Connected via: USB-C (Recovery Mode confirmed via
lsusb
showing NVIDIA APX)
What I’ve Tried:
-
Confirmed device is in recovery mode (Checked with
lsusb
- ID 0955:7023 NVIDIA APX is detected). -
Reinstalled JetPack 5.1.2 and SDK Manager from scratch.
-
Tried different USB cables and ports.
-
Ensured
nvme0n1
is the correct storage target and Jetson is booting from NVMe. -
Checked available storage (NVMe has 714GB free, so it’s not a space issue).
-
Rebooted host machine and Jetson multiple times between attempts.
-
Attempted to manually flash using:
sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1
and still encountered issues.
-
Tried flashing using SDK Manager GUI, same error.
-
Disabled secure boot, as recommended in some forum posts.
Error Snippets:
ERROR: Flash Jetson Linux - flash: [ 0.0091 ] ERROR: failed to read rcm_state
ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
ERROR: /misc/tsc_controls/tsc_locking_config is not supported
and later:
ERROR: Flash Jetson Linux - flash: Error: Invalid argument during seek for read on /dev/mmcblk0
ERROR: Flash Jetson Linux - flash: [ 9]: l4t_flash_from_kernel: Error: partprobe failed.
Request for Help:
At this point, I’ve exhausted most troubleshooting steps and am looking for advice. Is this an issue with the XML partitions, or is something wrong with my device?
Any suggestions or insight would be greatly appreciated!
Thanks,
Ricardo