Jetson Cloning & Backup and restore not working correctly

I have cloned the APP partition on one Jetson and then used sudo ./flash.sh -r -k APP <board> mmcblk0p1 to flash it to the second Jetson. The idea is that I would get the same OS and user files as the one I copied from. However, the second Jetson retains its OS and files and it seems the reflash had no affect.

I had then also used the backup and restore tool in tools/ of L4T tools and it also had no affect on the second Jetson when the ./toos/backup_and_restore/l4t_backup_restore.sh -r <board>. I had previously done a backup wit -b.

Am I doing something wrong? my board is jetson-xavier-nx-devkit-emmc. My lsusb that represents my type of board is 7e19 which falls onto either jetson-xavier-nx-devkit-emmc or jetson-xavier-nx-devkit

I’m using L4T Jetson Linux 35.1

Hi,

Are you sure restoring was performed successfully?
What did you get from flashing log and serial console log under these two circumstances?

I realised now it has to do with the fact that I was backing up the wrong partition. It was backing up/clonning the onboard emmc while I want the nvme

1 Like

That’s fine.
Then for NVMe drives, you need to use the second method which utilizes initrd flash, and flash.sh does not support NVMe drives. Also remember to replace every mmcblk0 with nvme0n1 in both nvbackup_partitions.sh and nvrestore_partitions.sh.

1 Like

Thanks for that, when I run nvbackup_partitions.sh -n I get an error cat: /etc/board_spec.txt:No such file or directory

I’ve copied the tools to a network drive that is mounted on the Jetson and then ran it. Am I required to do anything prior?

I have no idea what you are doing here.
I mean l4t_backup_restore.sh will internally call nvbackup_partitions.sh and nvrestore_partitions, and you have to patch these two scripts to have them work with NVMe drives, but you are not going to run them directly.

You should directly run l4t_backup_restore.sh on your host PC, but not anything else.

1 Like

Thank you again. I’ve now correctly modified both scripts I also made a modification in l4t_backup_restore.sh (nvme0n1 instead of mmcblk0) I’ve now put the Xavier in recovery mode and ran l4t_backup_restore.sh once more and it seems to be performing the backup.

1 Like

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