I'm having a problem: 'image-backup' has failed twice to make a backup of my RPi 5 that is using an NVME card. Here's the scenario:
RPi 5 (RPi OS bookworm) w/ 500 GB NVME card (please let me know if more hardware particulars are needed).
Running 'image-backup' as follows:After this, it just "stalls" - never completes. I left it to run overnight, came back the next morning (10+ hours later), and it has still not completed.
In the "post-mortem":
1. ctrl-C yielded:2. checked ps; nothing found under 'image', but 'rsync' was "still busy"??:3. a "substantial" image file was left behind; this was checked with 'image-check': I am (AFAIK) using the current/latest version of 'image-backup':
'image-backup' runs perfectly on my other systems, but the "other systems" are all 'bullseye' and use an SD card. I'm stumped - any advice?
RPi 5 (RPi OS bookworm) w/ 500 GB NVME card (please let me know if more hardware particulars are needed).
Running 'image-backup' as follows:
Code:
$ sudo image-backupImage file to create? /mnt/NetworkNAS/raspberrypi5/20240307_Pi5_ibu.imgInitial image file ROOT filesystem size (MB) [27041]? 27400Added space for incremental updates after shrinking (MB) [0]? 300Create /mnt/NetworkNAS/raspberrypi5/20240307_Pi5_ibu.img (y/n)? yIn the "post-mortem":
1. ctrl-C yielded:
Code:
^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(518) [generator=3.2.7]Code:
$ ps -aux | grep rsyncroot 3591 0.0 0.2 143600 11584 ? D 05:17 0:04 rsync -aDH --partial --numeric-ids --delete --force --exclude /tmp/img-backup-mnt --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 / /tmp/img-backup-mnt/Code:
$ sudo image-check /mnt/NetworkNAS/raspberrypi5/20240307_Pi5_ibu.imgCheck /mnt/NetworkNAS/raspberrypi5/20240307_Pi5_ibu.img (y/n)? ye2fsck 1.46.2 (28-Feb-2021)rootfs: recovering journalPass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationFree blocks count wrong (6859971, counted=6429521).Fix<y>? yesFree inodes count wrong (1754389, counted=1750599).Fix<y>? yesrootfs: ***** FILE SYSTEM WAS MODIFIED *****rootfs: 3801/1754400 files (0.6% non-contiguous), 584623/7014144 blocksFilesystem appears corruptedCode:
$ ls -l /usr/local/sbin-rwxr-xr-x 1 pi pi 14084 Feb 1 20:49 image-backup-rwxr-xr-x 1 pi pi 1534 Apr 23 2020 image-check-rwxr-xr-x 1 pi pi 3714 Oct 18 21:52 image-chroot-rwxr-xr-x 1 pi pi 3399 Oct 31 20:24 image-compare-rwxr-xr-x 1 pi pi 3107 Oct 18 21:53 image-info-rwxr-xr-x 1 pi pi 1667 Apr 23 2020 image-mount-rwxr-xr-x 1 pi pi 5711 Oct 18 21:53 image-set-partuuid-rwxr-xr-x 1 pi pi 4150 Jul 18 2021 image-shrink'image-backup' runs perfectly on my other systems, but the "other systems" are all 'bullseye' and use an SD card. I'm stumped - any advice?
Statistics: Posted by irishmonk-57 — Fri Mar 08, 2024 6:11 pm