I have tried with different dev kit units and also backed up from different systems (raw + system with our own software) and they are all the same. Idk what’s the reason. Here are the steps I do backup and restore.
Worth to note, that if I use the same method to flash a raw image (BSP + rootfs downloaded from the official website), it can work. But even if I didn’t change anything, just back up that newly installed system. Then I reflash the system, I’ll get stuck too.
It will get stuck forever unless i force exit. after force exit, if i reboot the orin again, the system will be gone and it won’t boot up. then i have to reflash the original raw system again.
The size is valid. Either raw (the “.raw” file) or sparse (the one without “.raw”) works for flash if copied to system.img. The raw file is ignored if its name is not “system.img”, and it won’t matter which one you use. The sparse file is smaller and thus faster to flash. I just wanted to find out if the partition size was valid, and it is. Being stuck is for some other reason.
In case it is a sparse-to-raw conversion issue you could try copying the “.raw” file to “system.img” and try with that, but I doubt it will help. If it does help, then you found a bug in sparse-to-raw conversion (which I’ve not seen stop a flash before…flash should not care if what it flashes is valid versus garbage).
Is this a VM, or is it an actual Ubuntu 18.04 or 20.04 PC? Ubuntu 18.04 is recommended, but I think 20.04 works with JetPack/SDK Manager 5.x.
Is the clone from the same release which is being used to flash it? They should match, but I would think if this fails, then it would still flash and simply not boot correctly, so I doubt this is the problem (worth checking though).