L4t_backup_restore restore backup long boot up times

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

Hi All,

I am currently using the l4t_backup_restore script located in ./tools/backup_restore/ in the Linux_for_Tegra folder derived from SDKManager when attempting to flash a device.

I have several jetson Orin NX devices which I am trying to restore a backup from using Jetpack 6.1. However, after restoring the backup, boot up times for the jetson devices take approximately 4:45 mins compared to ~30 seconds.

I am using a headless system so there is no opportunity to use the GUI to access UEFI settings, etc.

I believe my problem is exactly the same as what is mentioned here: Long Boot Time Issue with Ethernet Cable Inserted - #13 by robert969696

And I am fairly sure the solution mentioned: Long Boot Time Issue with Ethernet Cable Inserted - #14 by lhoang would solve my problem.

However, I was wondering if someone could give me some clarification on this. Am I supposed to install packages etc. (causing several boots potentially), make a backup, flash the original source device with this backup, add the L4TConfiguration.dts file with changed boot order (to indicate to prioritise nvme) and finally make another backup and restore this to my other jetson devices?

From my understanding, this would flash the backup to my other devices which would see the L4TConfiguration file on first boot and be able to parse the correct boot order from it to prioritise nvme. From there we should see quick boot up times with no long timing out sequences looking for other boot sources like network boot, etc.

If someone could clarify my understanding or give me more information if this is no longer valid for Jetpack 6, that would be very useful.

Kind regards,

Tom.

3

First, if you are able to access the boot log via the uart, that would be very useful.
Second, the solution is still valid for Jetpack 6. However, it seems that you need to modify your file system so the solution might be not preferable. I think what you can do is that after restoring the Orin NX devices, you can use efibootmgr to modify the boot order to the correct order. This way you don’t have to create a backup and restore the Orin NX devices again.

4

Hi @lhoang

Thanks for your fast reply. I will have a go with efibootmanager and see if that will solve my problem.

I will try and get you a boot log as well.

Thanks,

Tom.

5

Hi @lhoang

Thanks for your information. I have had a go with efibootmgr and have had good results.

I have checked various boards I have applied a backup to and they are all attempting network boot before attempting to boot from the SSD:

nvidia@nvidia:~$ efibootmgr
BootCurrent: 0008
Timeout: 5 seconds
BootOrder: 000C,000B,000A,0009,0008,0000,0006,0007
Boot0000* Enter Setup
Boot0006* BootManagerMenuApp
Boot0007* UEFI Shell
Boot0008* UEFI TS512GMTE652T2 H236370120
Boot0009* UEFI PXEv4 (MAC:48B02DF8E9DD)
Boot000A* UEFI PXEv6 (MAC:48B02DF8E9DD)
Boot000B* UEFI HTTPv4 (MAC:48B02DF8E9DD)
Boot000C* UEFI HTTPv6 (MAC:48B02DF8E9DD)

Interestingly, of all the boards I tried, it seems quite random as to which ones take a long time to boot with HTTP, PXE, etc. early in the boot order.

However, the board I have which had the correct boot order (SSD first) booted quickly in ~ 40 seconds.

I was able to change the boot order by running this command:

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

And this seems to have solved the problem.

The one board that I currently have which takes ages to boot (and was restored from a backup) now boots in ~40 seconds.

I have repeated this test quite a few times and the boot order remains the same and the boot time remains ~ 40 seconds.

Can you confirm to me that if I set the boot order via efibootmgr that it will remain persistant and cannot be changed by another process from boot to boot?

Can you also tell me if this would be the best way to ensure boot order is correct after restoring a backup (or even if a backup taken with the correct boot order will be reflected when I restore this backup).

I hope this makes sense.

Thanks very much

Kind regards,

Tom.

6

Yes this boot order will remain persistant and cannot be changed by another process from boot to boot. This is the best way to ensure boot order is correct after restoring a backup.

Unfortunately, if you create a backup image with this boot order and use it to restore other devices, it cannot be transferred to other devices because UEFI relies on hardware ID for boot order; and the NVMe SSDs on each devices are different

7

Right, that is no problem. I can apply the correct order using efibootmgr on every new device.

Thanks for the information. I will mark my earlier post as the solution. Thank you for your help.

Thank you!

Tom.

9

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