OK - it seemed odd to me, and I thought it worth a question. I do appreciate the tremendous effort you've put into this - all of it: creation of the scripts, and the support.What about the 'rsync' process I mentioned?
...
I wonder why this 'rsync' process continued to run after the 'image-backup' process was terminated?
That would be a question for the author of rsync. image-backup simply creates an empty image file that appears as a storage device with a BOOT partition formatted FAT32 and a ROOT partition formatted EXT4. That empty image file is then mounted as a loop device and rsync is executed to copy files to it:
image-backup is out of the loop while rsync is running. This code hasn't changed in literally years. The changes for Bookworm (using /boot/firmware instead of /boot) and NVMe (allowing /dev/nvme0n1 in addition to /dev/mmcblk0) were tiny changes. They appear to work properly for Raspberry Pi 5/Bookworm installations other than yours.
Have you considered copying your SD card to an NVMe device using usb-boot instead of rpi-clone? I believe you've said the problem only occurs when running from an NVMe device, which begs the question of it being the source of the problem. With no other reports of problems and not seeing any problems here, I'm limited as to what I can do for you.
And your suggestion to use `usb-boot` is a good one I'm sure, but a bit out-of-sync for me... I've invested more time/effort in this system since "starting from scratch" 3-4 weeks ago. I'd need to copy the NVME to the SD to have anything worth copying from the SD to the NVME - if you get my meaning :) In the meantime, I've made another successful "full backup", and updated it using the script I've written for that small task. And so - fingers crossed - I'm going to stand pat for the present. I'll post here if I've anything worth reporting.
Statistics: Posted by irishmonk-57 — Sat Mar 09, 2024 8:42 pm