Backup eMMC to SDCard

[Ali]

Hi every body, I have a Orangepi Plus 2E as you know with 16GB eMMC. Have installed armbian via SDCard before and executed nand-sata-install to copy it to eMMC. But currently need to get an image to install on another one. So there must be an opposite action like install_to_sdcard (in raspbian) but I couldn't find it.

[Moklev]

Uhmm... a full system backup with rsync?

 

i.e.

# rsync -aAXv --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} / /path_to_backup_dir/

(as root)

If you wish to restore, use the same command that was executed but with the source and destination reversed. Make you own --exclude list.

[Ali]

On 2/17/2018 at 5:06 PM, Moklev said:

# rsync -aAXv --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} / /path_to_backup_dir/

 

OK, I've used following scenario to clone file system.:

1. Write a fresh Armbian into an SD Card.
2. Put that sd card into main board that want to get backup from and boot.
3. Use rsync command to get backup into /OPI_Backup directory.
4. Shutdown and put sdcard into target board that want to restore and boot.
5. Use rsync command again to copy files from /OPI_Backup to /media/root/blablabla

After taking out sd card and boot the target board, system doesn't boot. Here you can see the UART result:

Spoiler

Starting kernel ...

[sun8i_fixup]: From boot, get meminfo:
        Start:  0x40000000
        Size:   2048MB
ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1
ion_reserve_select: ion chipid  [0x2c00081!
ion_reserve_common: ion reserve: [0xb0000000, 0xc0000000]!
Loading, please wait...
starting version 229
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  UUID=1c4afecd-7ac7-4bd7-9926-a561a2a61697 does not exist.  Dropping to a shell!
Rebooting automatically due to panic= boot argument

 

I must mention that there is already a files system on target board.

[Igor]

2 hours ago, Ali said:

ALERT!  UUID=1c4afecd-7ac7-4bd7-9926-a561a2a61697 does not exist.  Dropping to a shell!

 

you need to adjust root= parameter to match your new media. use some other computer and determine with blkid, change and boot.