How to Back Up and Restore the System Using Jetson Orin Nano

HI
When using the Jetson Orin Nano, I needed to migrate my entire current environment system to another system. I used the following commands:
cd ~/Jetson_Linux_R36.4.4_aarch64/Linux_for_Tegra/ sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b jetson-orin-nano-devkit-super

cd ~/Jetson_Linux_R36.4.4_aarch64/Linux_for_Tegra/ sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -r jetson-orin-nano-devkit-super

When performing the burn-in operation onto the new system, it prompted that it couldn’t attach to /dev/nvme0n1. However, this device is functioning normally and it was originally capable of booting up normally. Here is my complete error output. Please help analyze it.
Log is saved to Linux_for_Tegra/initrdlog/flash_3-2_0_20260202-173016.log
Run command:
ln -s /proc/self/fd /dev/fd && mount -o nolock [fc00:1:1::1]:/home/yahboom/test1/Linux_for_Tegra/tools/backup_restore /mnt && /mnt/nvrestore_partitions.sh -e nvme0n1 -n
on root@fc00:1:1::2
/mnt/images ~
nvrestore_partitions.sh: Use the default nvpartitionmap.txt as the index file.
40+0 records in
40+0 records out
20480 bytes (20 kB, 20 KiB) were copied, taking 0.000557632 seconds and achieving a transfer speed of 36.7 MB/s. Error: Unable to partprobe /dev/nvme0n1

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

Based on the provided context, it appears that you are attempting to migrate your current environment system to another system using the Jetson Orin Nano. You have used the l4t_backup_restore.sh script to create a backup of your system and are now trying to restore it to the new system.

However, you are encountering an error when trying to attach to the device /dev/nvme0n1. This device is functioning normally and was originally capable of booting up normally.

To analyze this error, let’s break down the log output:

  1. The script is trying to create a symbolic link to /proc/self/fd as /dev/fd.
  2. It then tries to mount the /home/username/test1/Linux_for_Tegra/tools/backup_restore directory to /mnt.
  3. The script then tries to restore the partitions using the nvrestore_partitions.sh script.
  4. The script uses the default nvpartitionmap.txt file as the index file.
  5. The script then tries to copy 400 records from the backup to the new system, but encounters an error when trying to attach to /dev/nvme0n1.

The error message “Error: Unable to partprobe /dev/nvme0n1” suggests that the script is unable to probe the partitions on the /dev/nvme0n1 device. This could be due to a variety of reasons, such as:

  • The device is not properly connected or configured.
  • The device is not recognized by the system.
  • There is a conflict with another device or partition.

To troubleshoot this issue, you can try the following:

  1. Verify that the /dev/nvme0n1 device is properly connected and configured.
  2. Check the system logs to see if there are any error messages related to the device.
  3. Try running the partprobe command manually to see if it returns any errors.
  4. Check the nvpartitionmap.txt file to ensure that it is correctly configured for the new system.

It’s also worth noting that the l4t_backup_restore.sh script is a complex script that performs a variety of tasks, including creating a backup of the system, restoring the partitions, and configuring the system. If you are experiencing issues with this script, it may be helpful to try breaking it down into smaller tasks to see where the error is occurring.

In comparison to other Jetson modules, the Jetson Orin Nano has a similar architecture and uses the same l4t_backup_restore.sh script for backup and restore operations. However, the specific error message and log output may vary depending on the module and system configuration.

In terms of HDMI support, the Jetson Orin NX and Nano modules support HDMI in addition to DP. To customize the carrier baseboard to HDMI, you can use the p3509-a02-p3767-0000.conf config file to flash the board.

Overall, the error message and log output suggest that there is an issue with the /dev/nvme0n1 device that is preventing the script from completing the restore operation. Further troubleshooting and debugging may be necessary to resolve this issue.

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

Hi,

Did you restore the image to another Orin Nano, or did you restore it to the original one?
Please provide the full logs, including the flashing log and the serial console logs.

Thanks