Does anyone know if the flash.sh used to create and image backup works for SSD/nvme too? It hasn’t been working for me.
NO.
flash.sh does not support anything involving NVMe/USB.
Please use the backup/restore tool located in Linux_for_Tegra/tools/backup_restore, and read the README file in that folder.
So when i run this command it boots into the board via ssh but nothing else happens. Am i missing something to use this script?
sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b jetson-orin-nano-devkit
Blockquote
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
Waiting for device to expose ssh …Device has booted into initrd. You can ssh to the target by the command:
$ ssh root@fc00:1:1:0::2
Cleaning up…
Log is saved to Linux_for_Tegra/initrdlog/flash_1-4_0_20240117-095412.log
Run command:
ln -s /proc/self/fd /dev/fd && mount -o nolock [fc00:1:1::1]:/home/ubuntu/nvidia/nvidia_sdk/JetPack_6.0_DP_Linux_DP_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/backup_restore /mnt && /mnt/nvbackup_partitions.sh -e nvme0n1 -n && echo Backup image is stored in /home/ubuntu/nvidia/nvidia_sdk/JetPack_6.0_DP_Linux_DP_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/backup_restore/images
on root@fc00:1:1::2
nvbackup_partitions.sh: The detected partitions in nvme0n1 are:
/dev/nvme0n1p1
/dev/nvme0n1p2
/dev/nvme0n1p3
/dev/nvme0n1p4
/dev/nvme0n1p5
/dev/nvme0n1p6
/dev/nvme0n1p7
/dev/nvme0n1p8
/dev/nvme0n1p9
/dev/nvme0n1p10
/dev/nvme0n1p11
/dev/nvme0n1p12
/dev/nvme0n1p13
/dev/nvme0n1p14
/dev/nvme0n1p15
nvbackup_partitions.sh: Backing up QSPI0…
flash_to_file: read, size 0x4000000, n 0x4000000
read(): Input/output error
Can you please also verify with 35.4.1?
Looks like it works for 35.4.1.
Why doesnt it work for Jetpack 6?
Also for the backup I just need the .tar.gz file right? all the *_bak.img file are just extra?
Is there anyway I can turn the nvme0n1p1.tar.gz file into the system.img file so it can be used in flashing?
Looks like a bug.
We will check it.
NO. They are all required.
You use -b for backup, then you use -r for restore.
Whats the best way for me to create a custom system.img file?
And does the l4t_initrd_flash.shflashing from system.img to NVMe instead of building the whole file system from scratch? Is --flash-only what i’m looking for? or --reuse?
If you just want to get a backup image, please use the tool I mentioned. You can also restore it.
I don’t know why you insist on working with system.img.
For our use case, it seems like system.img is the better solution since l4t_initrd_flash.sh can flash the qspi and nvme all at once. It is one file that our HVM group has to deal with. And with the problem we have discovered earlier with the backup image script, I can not move forward with using JetPack6 until this script issue is fixed.
But if you insist, we will stick with 35.4.1 until the issue with Jetpack 6 is resolved, or if anyone else would like to chime in to help with possibility system.img with the flashing script, that would be much appreciated.
The backup/restore tool does the same thing.
We are currently looking into it.
I think you can just run the same flashing command, but with —no-flash to generate the image along with all other boot loader stuff, without really flashing the device. Then swap out system.img with your own one, and flash with —flash-only.
I need to order more orin nano. I need to make sure restore works on a blank SoM. Give me a few days to confirm.
Can you also help me figure out why i can’t connect to the internet? I assuming its the jetson nano that has an issue connected.
You don’t need SDK Manager for installing JetPack components.
You can just run this on the device:
sudo apt update
sudo apt install nvidia-jetpack
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.