But it did not work out. Below is the end of output:
Device has booted into initrd. You can ssh to the target by the command:
$ ssh root@fe80::1%eth0
Cleaning up...
Log is saved to Linux_for_Tegra/initrdlog/flash_1-9_0_20250731-152406.log
Run command:
ln -s /proc/self/fd /dev/fd && mount -o nolock [fc00:1:1::1]:/home/ls4t/vc_mipi_nvidia/build/Xavier_35.4.1/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.
partx: specified range <1:0> does not make sense
The backup image is created from same board but it was flash normally first.
So is not possible to flash a backup image with newly SOM & nvme ?
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, I’ll try to help you troubleshoot the issue.
Firstly, it’s essential to understand that the Backup and Restore Tool is designed to create a backup image of a Jetson device and restore the Jetson from a backup image. However, the tool might not work seamlessly when dealing with new hardware components, such as a new SOM (System On Module) and NVMe storage.
The error message you provided doesn’t give much information about the issue. However, I can offer some general guidance and potential solutions.
Compatibility: Ensure that the backup image was created from the same Jetson Orin Nano DevKit model and that the new SOM and NVMe storage are compatible with the device. Check the NVIDIA documentation for any specific requirements or restrictions.
Backup image creation: Verify that the backup image was created correctly using the Backup and Restore Tool. Make sure that the image was created from a working system and that all necessary partitions were included in the backup.
Flashing process: When flashing the backup image, use the correct flashing command and options. For the Jetson Orin Nano DevKit with NVMe storage, you need to specify the correct PCIe controller and NVMe device. Refer to the example commands provided in the context:
SOM and NVMe initialization: After flashing the backup image, ensure that the new SOM and NVMe storage are properly initialized. You might need to run additional commands or scripts to configure the hardware.
Bootloader and kernel: Verify that the bootloader and kernel are correctly configured to support the new SOM and NVMe storage. You might need to update the bootloader or kernel to ensure compatibility.
Debugging: If none of the above steps resolve the issue, try debugging the flashing process using the flash.sh command with the --debug option. This will provide more detailed output and might help you identify the problem.
In summary, while it is technically possible to flash a backup image with a newly installed SOM and NVMe storage, there are potential compatibility and configuration issues that need to be addressed. Carefully review the NVIDIA documentation, verify the backup image creation, and ensure proper flashing and initialization of the new hardware components. If issues persist, try debugging the flashing process to identify the root cause.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
The new NVMe drive does not have any partitions. So it only works if I do a normal flash first, then re-flash the backup image. Later, I found another way to set a custom petition, but I was in a hurry, so I didn’t try it.