It's upgrade from bulseye. What is strange is that the image-utilities work if I try to do a backup without mounting. It creates 20 gb img file then shrinks it to 18 gb. In the same path. This takes about 30 min and I can see the verbose parm output. When I delete the file, mount the share and start the same command again it only creates the 20gb image file and hangs, no verbose output, no errors no nothing, I even waited for 2-3 hours just to be sure that isn't taking longer because of the network share
Upgrading Bullseye to Bookworm is often problematic and is not recommended. I've not tested Image File Utilities on such a system.
I can't reproduce the problem here:
Code:
root@raspberrypi:~# mount -t cifs -o username=xxxxxxxx,password=xxxxxxxx //192.168.1.100/work /mediaroot@raspberrypi:~# ./image-backup -i /media/test.imgStarting full backup (for incremental backups, run: ./image-backup /media/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: 81658/170016 files (0.1% non-contiguous), 553845/679672 blocksresize2fs 1.47.0 (5-Feb-2023)The filesystem is already 679672 (4k) blocks long. Nothing to do!resize2fs 1.47.0 (5-Feb-2023)The filesystem is already 679672 (4k) blocks long. Nothing to do!resize2fs 1.47.0 (5-Feb-2023)The filesystem is already 679672 (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: 81658/170016 files (0.1% non-contiguous), 553845/679672 blocksroot@raspberrypi:~# ./image-backup /media/test.imgroot@raspberrypi:~# ./image-info /media/test.img-rwxr-xr-x 1 root root 3321872896 Apr 27 02:03 /media/test.imgFilesystem Type 1K-blocks Used Available Use%boot vfat 522230 64726 457504 13%root ext4 2602488 2099180 350992 86%disk: PTUUID="8211cb8a-3034-4ddd-bb28-d0128ad5d957" PTTYPE="gpt"boot: LABEL_FATBOOT="bootfs" LABEL="bootfs" UUID="30A9-B6A1" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="2175cdf3-bd6d-4a16-8f21-13ba8e59e75b"root: LABEL="rootfs" UUID="a20b09d0-b086-49cb-9313-6148ba9d902c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="33111616-7218-aa4f-9a1a-3fec2828d594"root@raspberrypi:~#I would recommend writing a fresh Raspberry Pi OS Bookworm image to another storage device and testing the same scenario on it.
Statistics: Posted by RonR — Sat Apr 27, 2024 7:08 am