Jetpack 7.2 installation crash

Hi,

I’m trying to upgrade from JetPack 6.2 to 7.2 on my Jetson Orin Nano Super. However, the installation keeps crashing while installing packages, forcing me to open a shell. It opens the shell at root@ubuntu-server:/var/snap/subiquity/6808. Perhaps this indicates something? How can I fix this?
I have been following this guide;

Best regards,

Hello @otte.christian!

Based on the title and content of your topic, it looks like it may receive better visibility and feedback in a different category. We took the liberty of moving it for you.

If this was an incorrect assessment, please send me a direct message.

Disclaimer: this moderation suggestion and message were generated with AI assistance.

Same issue for me. Shows exit code 100 after the 15 mins wait message.

Same for me. I was targeting nvme

Here is where it crashes for me

finish:  subiquity/Late/run/command_29: logger -p info "[β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘] 67% Step 9/13 Updating boot firmware"
start:  subiquity/Late/run/command_30: rm -f /target/opt/nvidia/l4t-packages/.nv-l4t-disable-boot-fw-update-in-preinstall
finish:  subiquity/Late/run/command_30: rm -f /target/opt/nvidia/l4t-packages/.nv-l4t-disable-boot-fw-update-in-preinstall
start:  subiquity/Late/run/command_31: curtin in-target -- /bin/bash -c "mkdir -p /target/boot/efi; mount --bind /boot/efi /target/boot/efi"
finish:  subiquity/Late/run/command_31: curtin in-target -- /bin/bash -c "mkdir -p /target/boot/efi; mount --bind /boot/efi /target/boot/efi"
start:  subiquity/Late/run/command_32: mount --bind /dev /target/dev
finish:  subiquity/Late/run/command_32: mount --bind /dev /target/dev
start:  subiquity/Late/run/command_33: mount --bind /dev/pts /target/dev/pts
finish:  subiquity/Late/run/command_33: mount --bind /dev/pts /target/dev/pts
start:  subiquity/Late/run/command_34: curtin in-target -- /bin/bash -c "unset SNAP; DEBIAN_FRONTEND=noninteractive apt-get install --reinstall -y --no-install-recommends nvidia-l4t-bootloader"
finish:  subiquity/Late/run/command_34: Command '['systemd-cat', '--level-prefix=false', '--identifier=subiquity_log.2521', 'sh', '-c', 'curtin in-target -- /bin/bash -c "unset SNAP; DEBIAN_FRONTEND=noninteractive apt-get install --reinstall -y --no-install-recommends nvidia-l4t-bootloader"']' returned non-zero exit status 100.
finish: subiquity/Late/run: Command '['systemd-cat', '--level-prefix=false', '--identifier=subiquity_log.2521', 'sh', '-c', 'curtin in-target -- /bin/bash -c "unset SNAP; DEBIAN_FRONTEND=noninteractive apt-get install --reinstall -y --no-install-recommends nvidia-l4t-bootloader"']' returned non-zero exit status 100.
finish: subiquity/Install/install: Command '['systemd-cat', '--level-prefix=false', '--identifier=subiquity_log.2521', 'sh', '-c', 'curtin in-target -- /bin/bash -c "unset SNAP; DEBIAN_FRONTEND=noninteractive apt-get install --reinstall -y --no-install-recommends nvidia-l4t-bootloader"']' returned non-zero exit status 100.
start:  subiquity/ErrorReporter/1751466501.953714371.install_fail/add_info:
finish:  subiquity/ErrorReporter/1751466501.953714371.install_fail/add_info: written to /var/crash/1751466501.953714371.install_fail.crash
An error occurred. Press enter to start a shell

Hi,
Please check if you can re-trigger ISO installation. If not, we would suggest download the packages from release page and run the l4t_initrd_flash.sh command to upgrade to Jetpack 7.2 r39.2:
Quick Start β€” NVIDIA Jetson Linux Developer Guide

Tried from iso install multiple times, ending in same error.

Tried sdkmanager approach also using docker that failed in resolving host urm.nvidia.com. and directly from sdkmanager it got stuck.

Will try the alternate you suggested. But any idea why these other options not working?

Hi,
Could you please provide the crash log (ie /var/crash/*.install_fail.crash)?

hi,

I attached the log

crash.log (5.0 MB)

and here are some of the additional details the other thread mentioned would be helpful

Current UEFI firmware version: 39.2.0-gcid-45755727

Previous UEFI firmware version: 36.4.4-gcid-41062509

Target storage used: NVMe initially, but I also tried microSD with no luck

I used headless setup

Host OS used to create the USB installer: Windows

Thank you for the help

after looking closer it like the nano is misreporting its P3767-0005 compatible-spec as jetson-orin-nx-devkit-16gb (crash.log:12665), so nvidia-l4t-bootloader fails board matching (β€œdoes not match any known boards”, crash.log:45683) since that’s not actually a real configuration

so the 39.2.0 update regressed this board’s TegraPlatformCompatSpec value from 3767--0005--1--jetson-orin-nano-devkit-super- to the invalid 3767--0005--1--jetson-orin-nx-devkit-16gb-

so what’s the fix for this?

I checked crash log and have same error as charles mentioned. I have targeted SD card and SSD. any recommendations are appreciated.

Having the same issue, trying to install Jetpack 7.2 to NVMe on Orin Nano Super (previously at 6.2). Thanks for any insight you can offer! Here’s a screenshot of the error from the crash log.

I got it work by:

  1. using the direct flash method with the SDK manager, but stopping after Jetson Linux was fully flashed and not letting it install the runtimes/SDK components (that part wouldn’t work for me)
  2. going back and trying the ISO USB install method again

but at that point to be honest, why bother with the ISO USB

I tried that as well. Used sdk manager to flash 7.2 without runtime components, got a completely bootable Jetson Orin Nano on 7.2. Then used the 7.2 USB stick and tried to flash that exact same orin, and got the old exit status 127 error. So, had the same idea as you, but even that did not work for me. Yes, you can make it work with the sdk manager, but there are many reasons many people want a clean install from a USB.

I don’t know if this will help anyone or not, but I was struggling mightily with the exit status 127 error. What I found for me it was a strong function of the specific USB thumb drive used. I had a random stack of thumb drives and went through them. Half of them would consistently give the error when trying to flash the SD card, and half would not.