Can not restore the image on onrinnx

JP5.1.3
Here is my cmd to flash
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" --showlogs --network usb0 p3768-0000+p3767-0000-maxn internal
The machine can work well, and then I backup the image
sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b p3768-0000+p3767-0000-maxn
It work well too and then I want to restore to a new machine the nvme and the som are new. It crashes.
flash_1-12_0_20240316-182019.log (6.4 KB)

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%enxf6d6f3de8b61
Cleaning up...
Log is saved to Linux_for_Tegra/initrdlog/flash_1-12_0_20240316-182019.log 
Run command: 
ln -s /proc/self/fd /dev/fd && mount -o nolock [fc00:1:1::1]:/home/alfred/nvidia_docker/nvidia/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/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) copied, 0.000108992 s, 188 MB/s
partition: none, disk: /dev/nvme0n1, lower: 0, upper: 0
partx: /dev/nvme0n1: failed to find unused loop device: No such device

It use the serial to do that

bash-5.0# ls /dev/nvme0n1
/dev/nvme0n1

Hi AlfredNG
Please upload your restore log ,thanks

flash_1-12_0_20240316-182019.log (6.4 KB)

Hi AlfredNG,
please paste your restore command

sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -r p3768-0000+p3767-0000-maxn

Here is restore command

Hi AlfredNG,
please upload your uart log during restore as well. thanks

uart_log.txt (78.0 KB)
restore_tool_log.txt (98.4 KB)

Hi AlfredNG,
from restore_tool_log :
partx: /dev/nvme0n1: failed to find unused loop device: No such device

SSD not found during restore, what brand of this SSD?
could you try a new Samsung SSD?

I can find that

bash-5.0# ls /dev/nvme0n1
/dev/nvme0n1

There are two brands, one is Netac 128G and the other is WD 500G
Netac is log as above
WD can restore but stay at UEFI for about 5 minutes when I reboot the machine. The log is the following

Jetson UEFI firmware (version 5.0-35550185 built on 2024-02-20T04:21:22+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.
  Error: Could not retrieve NBP file size from HTTP server.

  Error: Unexpected network error.

>>Start HTTP Boot over IPv4.
  Error: Could not retrieve NBP file size from HTTP server.

  Error: Server response timeout.

>>Start PXE over IPv6.
  PXE-E16: No valid offer received.

>>Start PXE over IPv4.
  PXE-E18: Server response timeout.

L4TLauncher: Attempting Direct Boot
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services and installing virtual address map...
��I/TC: Secondary CPU 1 initializing
I/TC: Secondary CPU 1 switching to normal world boot
I/TC: Secondary CPU 2 initializing
I/TC: Secondary CPU 2 switching to normal world boot
I/TC: Secondary CPU 3 initializing
I/TC: Secondary CPU 3 switching to normal world boot
I/TC: Secondary CPU 6 initializing
I/TC: Secondary CPU 6 switching to normal world boot
I/TC: Secondary CPU 7 initializing
I/TC: Secondary CPU 7 switching to normal world boot

It seems that the uefi could not auto select the hard disk

Customizing the Default Boot Order in the UEFI Menu

When prompted to Press ESCAPE for boot options from the landing page of UEFI menu, navigate to Boot Maintenance manager and click Boot Options → Change Boot Order. The boot order can be changed at this time.

Or change it using

$ sudo efibootmgr
$ sudo efibootmgr -o 0008,000C,000B,000A,0009,0000,0006,0007

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