----------------------------------------------------------------------------------@kwatty1,
I don't believe you mentioned the model of Raspberry Pi or the Raspberry Pi OS image file you are using. I just used the following:
Raspberry Pi 4B 4GB
2024-11-19-raspios-bookworm-armhf-lite.img
After writing the image file to a USB SSD, I created an empty 'ssh' file in the BOOT partition. I then created a 'userconf' file in the BOOT partition containing:I booted the SSD on the Raspberry Pi 4B, logged in via SSH as pi:raspberry, became root, and ran image-backup without encountering any errors:Code:
pi:$6$GJ61x8I4L2xjODVZ$gyCxF/aw/wOZQCE8dKnaj8q6s0Ma1HPmn51AJEaETGz19CQfKMZ71MTW/zBylgE9LNJLnWMBcofDBP2vd0zvK0I'm not seeing a problem with image-backup.Code:
Linux raspberrypi 6.6.51+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt3 (2024-10-08) aarch64The programs included with the Debian GNU/Linux system are free software;the exact distribution terms for each program are described in theindividual files in /usr/share/doc/*/copyright.Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extentpermitted by applicable law.Last login: Tue Dec 10 20:49:35 2024 from 192.168.1.100SSH is enabled and the default password for the 'pi' user has not been changed.This is a security risk - please login as the 'pi' user and type 'passwd' to set a new password.Wi-Fi is currently blocked by rfkill.Use raspi-config to set the country before use.pi@raspberrypi:~ $ sudo -iSSH is enabled and the default password for the 'pi' user has not been changed.This is a security risk - please login as the 'pi' user and type 'passwd' to set a new password.Wi-Fi is currently blocked by rfkill.Use raspi-config to set the country before use.root@raspberrypi:~# nano image-backuproot@raspberrypi:~# chmod +x image-backuproot@raspberrypi:~# ./image-backupImage file to create? /mnt/test.imgInitial image file ROOT filesystem size (MB) [2381]?Added space for incremental updates after shrinking (MB) [0]?Create /mnt/test.img (y/n)? yStarting full backup (for incremental backups, run: ./image-backup /mnt/test.img)e2fsck 1.47.0 (5-Feb-2023)Pass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationrootfs: 69253/152608 files (0.1% non-contiguous), 404680/609280 blocksresize2fs 1.47.0 (5-Feb-2023)Resizing the filesystem on /dev/loop0p2 to 507706 (4k) blocks.The filesystem on /dev/loop0p2 is now 507706 (4k) blocks long.resize2fs 1.47.0 (5-Feb-2023)Resizing the filesystem on /dev/loop0p2 to 507503 (4k) blocks.The filesystem on /dev/loop0p2 is now 507503 (4k) blocks long.resize2fs 1.47.0 (5-Feb-2023)The filesystem is already 507503 (4k) blocks long. Nothing to do!e2fsck 1.47.0 (5-Feb-2023)Pass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationrootfs: 69253/128512 files (0.1% non-contiguous), 403168/507503 blocksroot@raspberrypi:~#
Hi Ron
Under System details in my previous reply, see:
Pi 3 Model B Rev 1.2 (I ommitted Pi 3. My bad)
OS:
VERSION_ID="12"
VERSION="12 (bookworm)"
In my first post, booting off a usb drive, I included the following reported errors:
rsync: [generator] symlink "/tmp/img-backup-mnt/boot/issue.txt" -> "firmware/issue.txt" failed: Operation not permitted (1)
rsync: [generator] symlink "/tmp/img-backup-mnt/boot/overlays" -> "firmware/overlays" failed: Operation not permitted (1)
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(713) [sender=3.2.7]
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(518) [generator=3.2.7]
rsync: [generator] write error: Broken pipe (32)
Aborted
Booting off an sd card, as per your recent instructions, the errors reported were:
rsync: [generator] symlink "/tmp/img-backup-mnt/boot/issue.txt" -> "firmware/issue.txt" failed: Operation not permitted (1)
rsync: [generator] symlink "/tmp/img-backup-mnt/boot/overlays" -> "firmware/overlays" failed: Operation not permitted (1)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.2.7]
Unable to create backup
The confusion for me is that, despite the above errors (specifically Aborted and Unable to create backup), the backup appears to complete and the image-check utility suggests image integrity is sound. I have not attempted to make a boot image from the test.img backup. I will do so now and reply back with the results.
Statistics: Posted by kwatty1 — Wed Dec 11, 2024 11:55 am
