I have 2 orin agx devices. I set up the first device, made a clone with the sudo command./flash.sh -r -k APP -G my_backup.img jetson-agx-orin-devkit mmcblk0p1. I do the recovery with the sudo command./flash.sh -r -k APP jetson-agx-orin-devkit mmcblk0p1. When trying to restore the second device, I get the error [ 28.466796] ERROR: mounting PARTUUID=000d8c60-ec48-4b0d-a2f2-457ba287c010 as /mnt fail…
I understood the reason for the error. You can point to detailed instructions for restoring different jetson orin agx devices from the same clone.
I can’t give you the exact answer. Probably some useful things to know though.
The partition UID is also cloned by that method. However, the boot content which is not part of the clone probably has an initrd or other software which has generated a different UID, and would have used that UID if the image had been freshly created during the flash. The nice thing is that if you have the raw clone still, then you can loopback mount this and examine it with standard tools, including finding the UID. You could even edit and change the UID with loopback. If it turns out the ID is other than the listed “PARTUUID=000d8c60-ec48-4b0d-a2f2-457ba287c010”, then changing this on the raw image would do the trick (you could then use mksparse with a NULL filler byte to make a system.img sparse clone for faster flash).
If the two are in fact the expected ID, then it is possible that an initrd needs to be updated as this will try to mount the partition. So it is likely a case of either (A) changing the partition UID, or (B) changing the requested UID from the initrd.
If you have the raw clone, and if it is named “clone.img.raw” then you could mount it on the host PC like this:
sudo mount -o loop clone.img.raw /mnt
You can then use “losetup --list” to find your loop device. I will pretend it is “/dev/loop10”. Disk utilities such as this will work:
sudo gdisk -l /dev/loop10lsblk -f /dev/loop10sudo blkid list /dev/loop10
You can then “sudo umount /mnt” or “sudo umount /dev/loop10” (you have to cd out of /mnt first).
Try to identify if a log or boot message (serial console is highly recommended) can identify what the requested ID is, and then use the above to see if the cloned ID matches.
Thank you for your reply; I’ll try to do it as you described.
I managed to resolve the issue of flashing two Jetson Orin AGX devices with the same clone. I first flashed one device and configured it. Then, following the instructions in /Linux_for_Tegra/tools/backup_restore/README_backup_restore.txt, I initially tried steps 1 and 2, but they didn’t work. However, using step 3 succeeded.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.