hi,
Could you provide a recovery image file for recovery if the OS is erased. Or, I would like to ask if it is possible to extract the OS image from ORIN.
hi,
Could you provide a recovery image file for recovery if the OS is erased. Or, I would like to ask if it is possible to extract the OS image from ORIN.
If you’ve installed the flash software, it produces a directory at:
~/nvidia/nvidia_sdk/JetPack_...version.../Linux_for_Tegra/
This contains the flash and clone tools. Note that JetPack/SDK Manager is a GUI front end to the actual flash software, and that the “Linux_for_Tegra/
” directory is the actual flash software.
Flashing with JetPack is the factory restore. It will erase what is on there now. Orin is fairly new, and it is advisable to flash with the most recent release which has significant bug fixes in it.
FYI, there are a lot of partitions on an AGX Orin. Jetsons don’t have a BIOS, and so that content is performed in software, and the boot and (equivalent) of the BIOS are in those partitions or QSPI memory (which is on the module). The clone only clones the rootfs (which is the Ubuntu operating system). One would normally clone, and perhaps restore, using the same flash software release that originally created the content. You can see your L4T release version (Ubuntu plus NVIDIA drivers) via:
head -n 1 /etc/nv_tegra_release
It is possible that a given rootfs will not be compatible with earlier or later boot content, but a clone can be used to copy and install content, e.g., you could restore the home directory via a clone and rsync
. I know there are some restore bugs in the older R35.x releases, but I think the most recent R35.x is improved. L4T (which is what actually gets flashed) has its release version tied to the GUI JetPack installer, so picking one picks the other. You can get the release you are interested in via either of:
You’ll want an Ubuntu 20.04 host PC and a lot of disk space. The clone produces both a “raw” image (a bit-for-bit exact copy of the rootfs partition, and so if the partition is 128 GB, then so will the file produced on the host PC), and it also produces a “sparse” image (which is more or less the size of the content in the partition; as the partition fills the sparse image approaches the size of the raw image…that’s a lot of disk space).
Documentation exists for specific releases of L4T, just go to that URL for your release. Note that you can pretty much clone from any L4T flash software release (I assume R34.x+ for Orin), and the time when the release version matters is during flash, which also installs the non-rootfs content (this content is standard, you don’t need to clone it).
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.