@marcel.tx The partition in which u-boot resides should be cloned as well. Then one needs to run u-boot from ram using the recovery mode, right?
I made the eMMC accessible to the host as usb mass storage device running
Apalis TK1 # ums 0 mmc 0 in the u-boot prompt. Then
rootfs have been mounted in
/media/kromer/rootfs. But no directory content was visible. I had to unmount and mount
rootfs again. Like expected
rootfs contains all the file system files.
But how can I clone/restore the whole system image information (including mbr, u-boot, etc.) in one “atomic” step? If I boot into linux on the target I should be able to use
ssh to transfer the whole eMMC content (including /dev/mmcblk0/mmcblk0boot1 and …/mmcblk0boot1) to the host over ethernet using something like
ubuntu@tegra-ubuntu:~$ dd if=/dev/mmcblk0 | ssh firstname.lastname@example.org "dd of=/home/kromer/full_backup.img" http://stackoverflow.com/questions/11681079/do-i-have-to-unmount-dev-mmcblk0-when-doing-dd-over-ssh. But my rootfs is not readonly and this could be a problem I guess… Would it make any difference to clone the eMMC by accessing it from the host side (something like
kromer@rc-019:~$ dd ssh email@example.com "dd if=/dev/mmcblk0" | dd of=home/kromer/full_backup.img)?