Issue Restoring JetPack 5.1.5 NVMe Image to a New Orin Nano Dev Kit

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

Hello,

I am trying to clone the NVMe content from an existing Orin Nano Super Dev Kit running JetPack 5.1.5 to a new Orin Nano Dev Kit.

Due to test environment limitations, we have only one Orin Nano Dev Kit available. Our test procedure is as follows:

  1. Flash JetPack (A) → Backup → Flash JetPack (B) → Restore the backup of JetPack (A) image.

After the restore process, the log shows the expected messages, indicating that the restore completed successfully.

image
image677×347 12.8 KB

The issue we are encountering is that after the restore, the board fails to boot.

After the restore, the board does not boot from the NVMe. Even when selecting the NVMe as the boot device in BootManager, nothing happens, and the board remains at the final shell prompt.

KakaoTalk_20251017_101308884
KakaoTalk_20251017_1013088841920×1440 204 KB

KakaoTalk_20251017_101730829
KakaoTalk_20251017_1017308291920×1440 213 KB

The commands used are:

  • Backup:
sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b jetson-orin-nano-devkit-super
  • Restore:
sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -r jetson-orin-nano-devkit-super

Could you please advise on how to resolve this NVMe boot issue after restoring the backup image?

Thank you for your support.

3

*** Please note that this reply is generated by LLM automatically ***

To resolve the NVMe boot issue after restoring the backup image on the new Orin Nano Dev Kit, I’ll provide a step-by-step guide and compare the commands used.

Understanding the issue:
The problem occurs after restoring the backup image of JetPack A on the new Orin Nano Dev Kit. The board fails to boot from the NVMe, even when selecting it as the boot device in BootManager.

Comparing the commands:
The commands used for backup and restore are:

Backup: sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -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

Restore: sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -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 --restore

Key differences:

  1. The --restore flag is missing in the original restore command. This flag is crucial for restoring the backup image.
  2. The --external-device option is set to nvme0n1p1 in both commands. Ensure that the NVMe device is correctly identified and configured on the new Orin Nano Dev Kit.

Resolution:

  1. Verify that the NVMe device is correctly identified and configured on the new Orin Nano Dev Kit. You can check the device list using lsblk or nvme list.
  2. Update the restore command to include the --restore flag: sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -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 --restore
  3. Re-run the restore command with the updated flag.
  4. After the restore process, ensure that the NVMe device is selected as the boot device in BootManager.

Additional troubleshooting steps:

  1. Check the boot logs for any errors or warnings using dmesg or journalctl.
  2. Verify that the NVMe device is properly configured in the device tree using dtc or fdt.
  3. If the issue persists, try re-flashing the JetPack image using the flash.sh script.

By following these steps and comparing the commands used, you should be able to resolve the NVMe boot issue after restoring the backup image on the new Orin Nano Dev Kit.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

5

Hello,

The part you mentioned for restoring looks like a flash command, and I’m not clear on what the actual restore command is.
When running l4t_initrd_flash.sh, I don’t see any --restore option available, so it’s unclear how the restore process is supposed to work.

6

Hi Suu,

My apologies for any confusion. Please kindly disregard the LLM suggestion.

JP 5.1.5 does not natively support NVMe backup and restore functionality in its default scripts. If you prefer not to modify the scripts, we recommend using JP 6.2.1, which includes full native support for NVMe backup, restore, and mass flash backup image operations.

If you need NVMe backup and restore support in JP 5.1.5, please refer to the topics below for guidance:

Thanks,

David

7

I followed your advice, and it seems to be working perfectly.
Thank you very much!