Looks like it is demanding an SD card. However, there are many partitions which are not the root partition, and these must match the release for the root partition. Have both units been flashed with the same L4T release? If not, then the rootfs of one Jetson will be incompatible with the other Jetson.
Second, there are places where Linux can optionally customize certain details. One of my favorite examples is to assign a new network device name or network device setup via the MAC address…and then have other software depend on this new name. This gets cloned, and if the hardware doesn’t have that MAC address, then it fails. A second example is that if passwords or accounts have been changed to something custom in one system, then the passwords and accounts would be changed in the second system as well. Was there any customization, e.g., network setup, but especially was anything done with the SD card? An example would be that if the SD was mounted while it was being cloned, then some temporary files residing on the eMMC might be expecting the SD to still be present.
Also, on the host PC where you store the clone (the specific directory where the clone took place), run “df -H .” (the “.” is important…alternatively instead of using cd to go there and then use “.”, instead use “df -H /where/ever/the/clone/was/originally/created”). There are times when Jetson clone and create operations will silently truncate content if there isn’t enough space on the host.