LOOP paths can not be set // umounting of /boot/firmware

[sneumeister]

Hello,

What I did: Downloaded latest version (1.1) of shrink-backup. The shring-backup-folder is located on my NAS mounted unter /mnt/netbackup/.

-rw-r--r-- 1 1024 users 9377861120 Jun  4 22:31 backup_george_bookworm.img
-rw-r--r-- 1 1024 users         83 Aug  1  2023 exclude.txt
-rw-r--r-- 1 1024 users       1539 Jun 25 17:20 LICENSE
-rw-r--r-- 1 1024 users      18192 Jun 25 17:00 README.md
-rwxr-xr-x 1 1024 users      99071 Jun 25 16:58 shrink-backup
-rw-r--r-- 1 1024 users      91117 Jul 20 23:06 shrink-backup.log

Ok, so I started upadte -U the above visible *.img file sudo /mnt/netbackup/shrink-backup/shrink-backup -Uz /mnt/netbackup/shrink-backup/backup_george_bookworm.img So far so good, output of program:

## Zoom speed requested...
## Scanning filesystem and calculating...
## Looping img file...
#####################################################################################
# Updating /mnt/netbackup/shrink-backup/backup_george_bookworm.img                  #
# f2fs filesystem detected on root                                                  #
# Autoexpand filesystem at boot not available for f2fs                               #
# Resize operations not available for f2fs                                          #
# --------------------------------------------------------------------------------- #
# Write to logfile: false                                                           #
# Zoom speed requested: true                                                        #
# Autocalculate img root partition size: false                                      #
# Autoexpand filesystem at boot: false                                              #
# Use exclude.txt: false                                                            #
# Bootsector size: 515MiB                                                           #
# Estemated root usage: 10661MiB                                                    #
# Total img size: 8943MiB                                                           #
#####################################################################################
## Do you want to continue? [y/n] n
!! Aborting...
## Exiting and cleaning up...
## Please stand by...
## Done.
## Elapsed time: 00.20

Since I discovered logfile was disables I stopped script by entering n. So I restarted backup with additional l option: sudo /mnt/netbackup/shrink-backup/shrink-backup -Ulz /mnt/netbackup/shrink-backup/backup_george_bookworm.img But since than the script shows errors....

## Debugging requested, writing to log file: /mnt/netbackup/shrink-backup/shrink-backup.log
## Zoom speed requested...
## Scanning filesystem and calculating...
lsblk: : not a block device
## Looping img file...
!! LOOP paths can not be set, retrying in 5 seconds...
!! LOOP paths can not be set, retrying in 5 seconds...
!! LOOP paths can not be set, retrying in 5 seconds...
^C
!! Script stopped by user...
## Exiting and cleaning up...
## Please stand by...
## Done.
## Elapsed time: 00.21

And this repeat everytime I restart the script. Logfile: shring-backup.log

losetup --list Gives no output.

Output of lsblk:

 $ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
mmcblk0     179:0    0 119.1G  0 disk
├─mmcblk0p1 179:1    0   512M  0 part
└─mmcblk0p2 179:2    0 118.6G  0 part /

This is the effect we have seen in some older issues: The mmcblk0p1 was un-mount for what ever reason. Re-mounting it again to /boot/firmware makes the script run as it should.

Since you search in /proc/mounts on your script I was wondering if this unmount-behaviour may be influenced by the order of mounts.

So I rebooted, started shrink-backup again and stopped with no (not continue). The first time nothing happened (checked with lsblk). Starting shrink-backup again and stopping with no (not continue) then brought the result with the unmounting of the /boot/firmware partition!

Remounting /boot/firmware and starting / stopping the script several times then never umounts /boot/firmware.

Repeating with reboot, mount /mnt/netbackup starting backup uns stopping ist with entering no this time immediately leads to an unmounted /boot/firmware .... Re-mount /boot/firmware manually and starting / stopping the script several times then never umounts anything.

Strange behavior... not able to grab the root cause.