Restore failed-to-back-up-and-restore-a-jetson-device 5.1.1

device: Jeston orin Nano developer kit
number :2
action: clone the total system of device A to device B
Instructions :

command:
sudo ./tools/backup_restore/l4t_backup_restore.sh -r jetson-orin-nano-devkit

Error:
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for device to expose ssh …RTNETLINK answers: File exists
RTNETLINK answers: File exists
Device has booted into initrd. You can ssh to the target by the command:
$ ssh root@fe80::1%ens160u1
Cleaning up…
Log is saved to Linux_for_Tegra/initrdlog/flash_3-2_0_20241021-014950.log
Run command:
ln -s /proc/self/fd /dev/fd && mount -o nolock [fc00:1:1::1]:/home/tom/.local/share/Trash/files/Linux_for_Tegra/tools/backup_restore /mnt && /mnt/nvrestore_partitions.sh -n
on root@fc00:1:1::2
/mnt/images ~
nvrestore_partitions.sh: Use the default nvpartitionmap.txt as the index file.
nvrestore_partitions.sh: You are trying to flash images from a board model that does not
match the current board you’re flashing onto.

i already flash device B to same jetson pack 5.1.1 as device A .because the 5.1.1 had deleted in SDK manager i use this method to flash

  -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" \
  --showlogs --network usb0 jetson-orin-nano-devkit internal`Preformatted text`

my system is load in mvme0 device. both device is the same, i dont know why i can clone from A but cant flash to device B
restore log file

**********************************************
*                                            *
*  Step 1: Build the flashing environment    *
*                                            *
**********************************************
Create flash environment 0
~/.local/share/Trash/files/Linux_for_Tegra/bootloader ~/.local/share/Trash/files/Linux_for_Tegra
~/.local/share/Trash/files/Linux_for_Tegra
Finish creating flash environment 0.
****************************************************
*                                                  *
*  Step 2: Boot the device with flash initrd image *
*                                                  *
****************************************************
~/.local/share/Trash/files/Linux_for_Tegra/temp_initrdflash/bootloader0 ~/.local/share/Trash/files/Linux_for_Tegra
./tegraflash.py --bl uefi_jetson_with_dtb_sigheader.bin.encrypt --bct br_bct_BR.bct --securedev  --bldtb tegra234-p3767-0004-p3768-0000-a0.dtb --applet rcm_2_encrypt.rcm --applet_softfuse rcm_1_encrypt.rcm --cmd "rcmboot"  --cfg secureflash.xml --chip 0x23 --mb1_bct mb1_bct_MB1_sigheader.bct.encrypt --mem_bct mem_rcm_sigheader.bct.encrypt --mb1_cold_boot_bct mb1_cold_boot_bct_MB1_sigheader.bct.encrypt --mb1_bin mb1_t234_prod_aligned_sigheader.bin.encrypt --psc_bl1_bin psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --mem_bct_cold_boot mem_coldboot_sigheader.bct.encrypt  --bins "psc_fw pscfw_t234_prod_sigheader.bin.encrypt; mts_mce mce_flash_o10_cr_prod_sigheader.bin.encrypt; mb2_applet applet_t234_sigheader.bin.encrypt; mb2_bootloader mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt; xusb_fw xusb_t234_prod_sigheader.bin.encrypt; dce_fw display-t234-dce_sigheader.bin.encrypt; nvdec nvdec_t234_prod_sigheader.fw.encrypt; bpmp_fw bpmp_t234-TE950M-A1_prod_sigheader.bin.encrypt; bpmp_fw_dtb tegra234-bpmp-3767-0004-3509-a02_with_odm_sigheader.dtb.encrypt; sce_fw camera-rtcpu-sce_sigheader.img.encrypt; rce_fw camera-rtcpu-t234-rce_sigheader.img.encrypt; ape_fw adsp-fw_sigheader.bin.encrypt; spe_fw spe_t234_sigheader.bin.encrypt; tos tos-optee_t234_sigheader.img.encrypt; eks eks_t234_sigheader.img.encrypt; kernel boot0.img; kernel_dtb tegra234-p3767-0004-p3768-0000-a0.dtb"    --secondary_gpt_backup  --bct_backup  --boot_chain A  --instance 3-2
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
 

 Entering RCM boot

[   0.2509 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from --mb1_bin
[   0.2509 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from --psc_bl1_bin
[   0.2509 ] rcm boot with presigned binaries
[   0.2531 ] tegrarcm_v2 --instance 3-2 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[   0.3715 ] BR_CID: 0x80012344705DD8213C00000018FE80C0
[   0.4803 ] Sending bct_br
[   0.4804 ] Sending mb1
[   0.5573 ] Sending psc_bl1
[   0.7766 ] Sending bct_mb1
[   0.9411 ] Generating blob for T23x
[   0.9455 ] tegrahost_v2 --chip 0x23 0 --generateblob blob.xml blob.bin
[   0.9468 ] The number of images in blob is 18
[   0.9476 ] blobsize is 65788654
[   0.9477 ] Added binary blob_uefi_jetson_with_dtb_sigheader.bin.encrypt of size 3182656
[   1.0398 ] Added binary blob_pscfw_t234_prod_sigheader.bin.encrypt of size 375168
[   1.0403 ] Added binary blob_mce_flash_o10_cr_prod_sigheader.bin.encrypt of size 190592
[   1.0409 ] Added binary blob_applet_t234_sigheader.bin.encrypt of size 277312
[   1.0413 ] Not supported type: mb2_applet
[   1.0415 ] Added binary blob_mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt of size 437984
[   1.0420 ] Added binary blob_xusb_t234_prod_sigheader.bin.encrypt of size 164352
[   1.0425 ] Added binary blob_display-t234-dce_sigheader.bin.encrypt of size 9097216
[   1.0484 ] Added binary blob_nvdec_t234_prod_sigheader.fw.encrypt of size 294912
[   1.0515 ] Added binary blob_bpmp_t234-TE950M-A1_prod_sigheader.bin.encrypt of size 1047936
[   1.0528 ] Added binary blob_tegra234-bpmp-3767-0004-3509-a02_with_odm_sigheader.dtb.encrypt of size 199872
[   1.0531 ] Added binary blob_camera-rtcpu-sce_sigheader.img.encrypt of size 166304
[   1.0534 ] Added binary blob_camera-rtcpu-t234-rce_sigheader.img.encrypt of size 537952
[   1.0537 ] Added binary blob_adsp-fw_sigheader.bin.encrypt of size 400960
[   1.0539 ] Added binary blob_spe_t234_sigheader.bin.encrypt of size 270336
[   1.0541 ] Added binary blob_tos-optee_t234_sigheader.img.encrypt of size 1064752
[   1.0550 ] Added binary blob_eks_t234_sigheader.img.encrypt of size 9232
[   1.0553 ] Added binary blob_boot0.img of size 47724544
[   1.0965 ] Added binary blob_tegra234-p3767-0004-p3768-0000-a0.dtb of size 345470
[   1.7321 ] tegrarcm_v2 --instance 3-2 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
[   1.8723 ] BL: version 0.32.0.0-t234-54845784-57325615 last_boot_error: 0
[   1.9560 ] Sending bct_mem
[   1.9840 ] Sending blob
[   6.8201 ] RCM-boot started

~/.local/share/Trash/files/Linux_for_Tegra
***************************************
*                                     *
*  Step 3: Start the flashing process *
*                                     *
***************************************
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for device to expose ssh ......RTNETLINK answers: File exists
RTNETLINK answers: File exists
Device has booted into initrd. You can ssh to the target by the command:
$ ssh root@fe80::1%ens160u1
Cleaning up...

Hi lyysupertom,

Have you confirmed that you are using the devkit board rather than custom carrier board?

Please verify with the latest JP5.1.4(R35.6.0).

Do you mean the nvme0n1(NVMe SSD) here?
If so, you have to specify -e nvme0n1 during backup for NVMe SSD.

Do you also connect SD on the devkit or only NVMe SSD?

I bought a two the devkit board that is Jeston orin Nano 4GB named this .sorry i could not reflash device A to JP5.1.4(R35.6.0) because some enviroment i am not sure can run. i am only conneting NVMe SSD. is use this commond to backup?

sudo ./tools/backup_restore/l4t_backup_restore.sh -r jetson-orin-nano-devkit -e nvme0n1

For the devkit, you should be able to update to the latest JP5.1.4(R35.6.0) through SDK manager.

The following command is used for backup:

$ sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b jetson-orin-nano-devkit

The following command is used for restore:

$ sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -r jetson-orin-nano-devkit

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.