Fail to restore nvme with Jetson Orin nx,B1 backup, B2 restore fail, JetPack_5.1.2

JetPack_5.1.2

B1 B2 same batch orin module
nvme1 nvme2 all N930ES M.2 nvme 128G

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

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

two sets: B1+nvme1, B2+nvme2

step:
B1+nvme1-> Installing system through the SDK Manager, and then backup
B2+nvme2-> Restore using the command above, and fail

what is the reason for this?

B1+nvme1 self restore log → cmd_B1_nvme1_log.txt & uart_B1_nvme1_log.txt
B2+nvme2 restore fail log → cmd_B2_nvme2_log.txt & uart_B2_nvme2_log.txt

cmd_B1_nvme1_log.txt (125.6 KB)
cmd_B2_nvme2_log.txt (96.2 KB)
uart_B1_nvme1_log.txt (212.6 KB)
uart_B2_nvme2_log.txt (121.2 KB)

PS: before b1+nvme1 installed the system through the SDK Manager, already tried to restore with the backup of A+nvmeA, which failed too, so I tried the SDK Manager and installed it successfully

Hi 1adamward1,

Are you using the devkit or custom board for Orin NX?

nvrestore_partitions.sh: Use the default nvpartitionmap.txt as the index file.
partx: specified range <1:0> does not make sense

Could you try to use another USB cable and NVMe drive to restore on B2?

custom board for Orin NX

using another USB cable->done

backup->B1+nvme1+boardB1

restore->B2+nvmeA+boardB2

after restore:

B2+nvmeA+boardB2 → can not get into the system, black screen. → see log cmd_B2_nvmeA_log.txt & uart_B2_nvmeA_log.txt

A+nvmeA+boardA->can get into the system. → see log uart_A_nvmeA_log.txt

B2+nvme1+boardB2->can get into the system. → see log uart_B2_nvme1_log.txt

cmd_B2_nvmeA_log.txt (105.1 KB)
uart_A_nvmeA_log.txt (91.0 KB)
uart_B2_nvmeA_log.txt (274.3 KB)
uart_B2_nvme1_log.txt (90.8 KB)

using the same Samsung SSD, B2 still fails to get into the system, reset/ power off/on, only black screen

Test order:

B1+sumsung_SSD_980+boardB1, Installing the system through the SDK Manager, can get into the system

B1+sumsung_SSD_980+boardB1, backup && self-restore, can get into the system

B2+sumsung_SSD_980+boardB2, restore and shows successfully, can not get into the system, reset/ power off/on, only black screen

Extra test:

B1+sumsung_SSD_980+boardB1, power on, can get into the system

B1+sumsung_SSD_980+boardB2, power on, can get into the system

Result:

issue not related to SSD or board

B1 has been Installing the system through the SDK Manager, but not B2

the issue relates to B2 orin module

before being built through the SDK Manager, B1 had the same issue, after that issue was gone.

Question:

why B2 can not get into the system when it is blank(not being built through the SDK Manager)?

B1_B2_sumsung_ssd_flash_uart_cmd_log_sets.zip (132.4 KB)

From this log, it seems trying to boot from HTTP and then trigger reset.
Could you enter UEFI menu and select it to boot from NVMe drive?

Jetson UEFI firmware (version 4.1-33958178 built on 2023-08-01T19:34:02+00:00)
ESC   to enter Setup.
F11   to enter Boot Manager Menu.
Enter to continue boot.
**  WARNING: Test Key is used.  **
......
>>Start HTTP Boot over IPv6.▒▒
[0000.061] I> MB1 (version: 1.2.0.0-t234-54845784-562369e5)
[0000.067] I> t234-A01-0-Silicon (0x12347) Prod
[0000.071] I> Boot-mode : Coldboot

In addition, do you have the the same partition layout for both module/board?

nvmeA is 256G
nvme1 and 2 are 128G
B1 B2 same batch orin module
boradB1 and boradB2 have the same layout

Recent test:

B1+nvme1+boardB1->Installing the system through the SDK Manager, can get into the system
B1+nvme1+boardB1->backup && self-restore and can get into the system
B2+nvme2+boardB2->restore fail

fail case just the same as the original post topic

How about if you backup and restore with this combination?

no need to backup and restore with B2+nvme2+boardB2. B1+nvme1+boardB1 had the same condition at the very beginning. also have the same issue, which is mentioned in the original post topic’s PS part.

currently, B2 never installs the system through the SDK Manager, which I intend to save the issue’s env.

test update:

B1+nvme2+boardB2->Installing the system through the SDK Manager, can get into the system
B1+nvme2+boardB2->restore using the backup of B1+nvme1+boardB1
B2+nvme2+boardB2->power on, can get into the system

the test result shows that:

  1. there is nothing wrong of B1, B2, nvme1, nvme2, boardB1 or boardB2
  2. only SSD had been installed by the SDK Manager then the restore process can be processed successfully

Question:
why does SSD have to be installed by the SDK Manager first? Is there a firewall between orin module and empty SSD?

Actually, you shouldn’t use SDK Manage to flash the board since you are using the custom carrier board.
If you don’t use SDKM to flash the SSD, how did you flash?

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