Hi, I have a 128GB sd card. Raspberry pi 4b. Running Buster-Lite. Headless. When I use
sudo ./mini_image.sh backup.img mmcblk0
Your documentation doesn't specify, I assume that "device" argument is the device I want to read
I get an infinite loop, tons of rsync log msgs, ever growing, including it's own backup.img file recursively (/root/backup.img, then /root/sdcard/backup.img, etc...)
I had to CTRL-C out of it, which left some things open (might be a great idea to add a CTRL-C signal handler to the script).
If I use sudo ./mini_image.sh backup.img
it generates an image
If I try to restore with Belena Etcher, or using sudo dd if=backup.img of=/dev/disk3
I get an unrecognized disk (in MacOSX),
And it doesn't boot on the rpi - my HDMI doesn't even turn on. Constant green light.
however, when I diskutil list
, I see:
/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *125.0 GB disk3
1: DOS_FAT_16 265.3 MB disk3s1
2: Linux 2.1 GB disk3s2
but it simply doesn't mount in MacOSX like normal rasbian .img files... ( I would expect to see the FAT /boot directory mounted under /Volumes, to edit config.txt and cmdline.txt and such... but MacOSX says unrecognized disk would you like to format)
On my rpi, before backing up with mini_image.sh, I get:
$ sudo blkid
/dev/mmcblk0p1: LABEL_FATBOOT="boot" LABEL="boot" UUID="F661-303B" TYPE="vfat" PARTUUID="88bd9a7d-01"
/dev/mmcblk0p2: LABEL="rootfs" UUID="8d008fde-f12a-47f7-8519-197ea707d3d4" TYPE="ext4" PARTUUID="88bd9a7d-02"
/dev/sda1: LABEL="Samsung USB" UUID="D896-5CB1" TYPE="vfat" PARTUUID="c3072e18-01"
/dev/mmcblk0: PTUUID="88bd9a7d" PTTYPE="dos"