Without some way to reproduce your problem, I'm at a loss to know what to suggest.
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:
Code:
rsync -aDH --partial --numeric-ids --delete --force --exclude "${MNTPATH}" --exclude '/dev' --exclude '/lost+found' --exclude '/media' --exclude '/mnt' \--exclude '/proc' --exclude '/run' --exclude '/sys' --exclude '/tmp' --exclude '/var/swap' --exclude '/etc/udev/rules.d/70-persistent-net.rules' \--exclude '/var/lib/asterisk/astdb.sqlite3-journal' "${OPTIONS[@]}" / "${MNTPATH}/" if [[ $? -ne 0 && $? -ne 24 ]]; then errexit "Unable to create backup" fiHave 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.
Statistics: Posted by RonR — Sat Mar 09, 2024 7:29 pm