Boot Issue After Image Recovery on NVMe SSD Orin Nano Custom Board Jetpack6.1

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
1

Dear NVIDIA Supporter,

I used a backup tool to back up an image and then recovered it to a custom board with an NVMe SSD.
However, I encountered a boot problem with the following messages:
`>>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-E16: No valid offer received.`
I followed other responses suggesting to check that the SSD is set as the first boot option in the UEFI settings.
Is there any method to skip or disable the Ethernet boot in UEFI?

Best regards,
Yen

2

Refer this link for changing boot order via efibootmgr method:

3

Hi yen_chou,

Please also check if NVMe SSD is still the first boot device in boot order of UEFI menu.
You can press ESC during boot to enter into UEFI menu

4

Hi Nagesh_accord,

Thank you for you reply, but the issue still persists.
Here are the steps I followed:
1.Set the boot order on machine A using efibootmgr:

ubuntu@tegra-ubuntu:~$ sudo efibootmgr -o 0001,0004,0003,0002,0005,0000,0006,0007
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0004,0003,0002,0005,0000,0006,0007
Boot0000* Enter Setup
Boot0001* UEFI Phison ESMP256GKB5C2-E19T 25032M25600414 1
Boot0002* UEFI PXEv4 (MAC:3C6D66222928)
Boot0003* UEFI PXEv6 (MAC:3C6D66222928)
Boot0004* UEFI HTTPv4 (MAC:3C6D66222928)
Boot0005* UEFI HTTPv6 (MAC:3C6D66222928)
Boot0006* BootManagerMenuApp
Boot0007* UEFI Shell

2.Backed up the image:

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

3.Restored the image on another device:

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

4.Powered on machine B and checked the boot order:

ubuntu@tegra-ubuntu:~$ efibootmgr
BootCurrent: 0008
Timeout: 0 seconds
BootOrder: 000C,000B,000A,0009,0008,0000,0006,0007
Boot0000* Enter Setup
Boot0006* BootManagerMenuApp
Boot0007* UEFI Shell
Boot0008* UEFI Phison ESMP512GKB5C2-E19T 24454M51210725 1
Boot0009* UEFI PXEv4 (MAC:48B02DF90434)
Boot000A* UEFI PXEv6 (MAC:48B02DF90434)
Boot000B* UEFI HTTPv4 (MAC:48B02DF90434)
Boot000C* UEFI HTTPv6 (MAC:48B02DF90434)

As you can see, the boot order on machine B is different from machine A.

5

Hi KevinFFF,
Thank you for your reply.
Yes, I’ve confirmed that the NVMe SSD is still set as the first boot device.

The issue occurs after performing the backup and restore process between the two machines. The detailed steps are provided in my previous reply to Nagesh_accord.

Is there any method to lock or preserve the boot order settings in the boot menu?

6

Try changing the boot order on the same machine and restart that machine and check the boot order.
It will be persistent and settings are restored across the boot.

7

Boot-order should be predefined in L4TConfiguration.dtsbefore flash.

What’s the boot order on machine B before you perform restore process?
Have you tried to configure the boot-order to set NVMe as first boot device manually on machine B?

8

Hi Nagesh_accord,

Changing the boot order on the same machine works fine, but after restoring the image to another machine, the boot order gets changed.
I would like to resolve the issue where a backup from machine A and restore to machine B results in a different boot order.

1 Like
9

1.Boot order should be predefined in L4TConfiguration.dts before flashing.
In L4TConfiguration.dts, the boot order is defined as follows:

gNVIDIATokenSpaceGuid {
    DefaultBootPriority {
        data = "usb,nvme,emmc,sd,ufs";
        locked;
    };
};

However, it still boots from HTTP instead of NVMe by default.
How can I set NVMe as the default boot device, instead of HTTP?

2.What was the boot order on machine B before performing the restore process?
The boot order on machine B was the same as on machine A before the restore.

3.Have you tried setting the boot order manually on machine B to prioritize NVMe?
No, I haven’t set it manually because I expected the boot order to remain the same after restoring the backup from machine A.
Is it possible that the backup process does not include UEFI settings such as the boot order?

12

We can reproduce the similar behavior as yours.
I’ve checked this with internal and we think the current result is expected.
Please refer to L4t_backup_restore restore backup long boot up times - #6 by lhoang for details.