Thank you but in case of encrypted disk, we can’t reuse this backup because flash command use rootfs to create another encrypted img file. If each device have an unique key for disk encryption we can only backup with rsync ? This work fine in JetPack 4 but in Jetpack5 doesn’t.
Sorry, I’m not clear about what do you mean here. Have you tried if it would work with your encrypted disk on JP5?
The minimal root file system is the basic root file system that is used for NVIDIA Jetson develop kits.
Are you using the devkit or custom board for Xavier NX?
Thanks for your help.
My issue was with a package I removed in my rootfs. The consequence is that the nvidia luks package is not in /usr/sbin and causes a boot failure caused by not being able to decrypt the disk
Minor thought: This is good, but you might consider “--numeric-owner”, which is possibly better. Numeric ID is quite robust compared to a lot of other methods (in combination with the option to preserve permissions).
Don’t forget that if your sample rootfs does not contain the NVIDIA content, that you’ll also need to run: sudo ./apply_binaries.sh
I’ve not run flash naming an alternate sample rootfs location, but consider that on a normal command line flash some “rootfs/boot/” content is copied in before image generation based on what target is specified, including an extlinux.conf. You could run a log of a normal flash, and try to manually copy that content into your alternate location before flashing (just example parameters for an SD card model, adjust for your case…this is to show logging): sudo ./flash.sh jetson-xavier-nx-devkit mmcblk1p1 2>&1 | tee log_flash.txt
Look what gets copied in. Then run whatever flash you were using with the same logging. Append this: sudo .... 2>&1 | tee log_alt_flash.txt
Compare what is or is not copied ahead of time for kernel/extlinux so on.