Error when updating to FreedomBox 23.15: No free space on boot partition

vrillo · August 19, 2023, 3:06pm

After upgrading to Bookworm there were no updates anymore. So there was the advice of the maintainers to do:

sudo apt install -t bookworm-backports freedombox

which worked fine up to FreedomBox Version 23.14. FreedomBox 23.15 has now been released and uploaded to Debian unstable. When I try to update to this version via ssh (Putty) by doing

sudo apt install -t bookworm-backports freedombox

the result is:

Log started: 2023-08-19 16:45:38
quota not working (qgroup not set)
quota not working (qgroup not set)
(Reading database …
(Reading database … 5%
(Reading database … 10%
(Reading database … 15%
(Reading database … 20%
(Reading database … 25%
(Reading database … 30%
(Reading database … 35%
(Reading database … 40%
(Reading database … 45%
(Reading database … 50%
(Reading database … 55%
(Reading database … 60%
(Reading database … 65%
(Reading database … 70%
(Reading database … 75%
(Reading database … 80%
(Reading database … 85%
(Reading database … 90%
(Reading database … 95%
(Reading database … 100%
(Reading database … 69139 files and directories currently installed.)
Removing linux-image-6.1.0-9-arm64 (6.1.27-1) …
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-6.1.0-9-arm64
/etc/kernel/postrm.d/z50-raspi-firmware:
cp: error writing ‘/boot/firmware/initrd.img-6.1.0-11-arm64’: No space left on device
run-parts: /etc/kernel/postrm.d/z50-raspi-firmware exited with return code 1
dpkg: error processing package linux-image-6.1.0-9-arm64 (–remove):
installed linux-image-6.1.0-9-arm64 package post-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
linux-image-6.1.0-9-arm64
Processing was halted because there were too many errors.
Config is in use.
Illegal snapshot.
Config is in use.
E:Sub-process /usr/bin/dpkg returned an error code (1)
Log ended: 2023-08-19 16:46:03

It’s the same when I try to update manually by using GUI.

jvalleroy · August 19, 2023, 3:38pm

The error is here, there is no free space on your boot partition. Is this a Raspberry Pi 4, or 3?

vrillo · August 19, 2023, 3:45pm

This is a Raspberry Pi 4 Model B.

vrillo · August 19, 2023, 3:53pm

What do you think about this?

sudo apt autoremove
[sudo] password for pi:
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following packages will be REMOVED:
linux-image-6.1.0-9-arm64
0 upgraded, 0 newly installed, 1 to remove and 14 not upgraded.
3 not fully installed or removed.
After this operation, 355 MB disk space will be freed.
Do you want to continue? [Y/n]

jvalleroy · August 19, 2023, 6:35pm

Yes, that looks ok to remove the old kernel.

vrillo · August 19, 2023, 6:48pm

No, this doesn’t work:

sudo apt autoremove
[sudo] password for pi:
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following packages will be REMOVED:
linux-image-6.1.0-9-arm64
0 upgraded, 0 newly installed, 1 to remove and 14 not upgraded.
3 not fully installed or removed.
After this operation, 355 MB disk space will be freed.
Do you want to continue? [Y/n] y
quota not working (qgroup not set)
(Reading database … 69139 files and directories currently installed.)
Removing linux-image-6.1.0-9-arm64 (6.1.27-1) …
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-6.1.0-9-arm64
/etc/kernel/postrm.d/z50-raspi-firmware:
cp: error writing ‘/boot/firmware/initrd.img-6.1.0-11-arm64’: No space left on device
run-parts: /etc/kernel/postrm.d/z50-raspi-firmware exited with return code 1
dpkg: error processing package linux-image-6.1.0-9-arm64 (–remove):
installed linux-image-6.1.0-9-arm64 package post-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
linux-image-6.1.0-9-arm64
Processing was halted because there were too many errors.
Config is in use.
E: Sub-process /usr/bin/dpkg returned an error code (1)

vrillo · August 20, 2023, 4:52am

I tried to remove all wasted kernels.

The currently used one:
uname -r
6.1.0-10-arm64

uname -a
Linux freedombox 6.1.0-10-arm64 #1 SMP Debian 6.1.38-2 (2023-07-27) aarch64 GNU/Linux

All kernels:
sudo dpkg -l | grep linux-image

sudo dpkg -l | grep linux-image
[sudo] password for pi:
ii linux-image-5.10.0-10-arm64 5.10.84-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-12-arm64 5.10.103-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-13-arm64 5.10.106-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-14-arm64 5.10.113-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-15-arm64 5.10.120-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-16-arm64 5.10.127-2 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-17-arm64 5.10.136-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-18-arm64 5.10.140-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-19-arm64 5.10.149-2 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-20-arm64 5.10.158-2 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-21-arm64 5.10.162-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-22-arm64 5.10.178-3 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-23-arm64 5.10.179-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
ii linux-image-6.1.0-10-arm64 6.1.38-2 arm64 Linux 6.1 for 64-bit ARMv8 machines (signed)
iF linux-image-6.1.0-11-arm64 6.1.38-4 arm64 Linux 6.1 for 64-bit ARMv8 machines (signed)
rH linux-image-6.1.0-9-arm64 6.1.27-1 arm64 Linux 6.1 for 64-bit ARMv8 machines (signed)
iU linux-image-arm64 6.1.38-4 arm64 Linux for 64-bit ARMv8 machines (meta-package)

So I actually should be able to remove the old kernels:
ii linux-image-5.10.0-10-arm64
every kernel deleted but still configured (rc)
the half-installed one
rH linux-image-6.1.0-9-arm64

The rest would be
ii linux-image-6.1.0-10-arm64
iF linux-image-6.1.0-11-arm64 (half-configured)
iU linux-image-arm64 6.1.38-4 arm64 Linux for 64-bit ARMv8 machines (meta-package) (unpacked)

So first of all I tried to remove linux-image-5.10.0-10-arm64. But it also failed. Strange that the system automatically also tried to remove the linux-image-6.1.0-9-arm64:

sudo apt-get remove --purge linux-image-5.10.0-10-arm64
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following packages will be REMOVED:
linux-image-5.10.0-10-arm64* linux-image-6.1.0-9-arm64
0 upgraded, 0 newly installed, 2 to remove and 14 not upgraded.
3 not fully installed or removed.
After this operation, 611 MB disk space will be freed.
Do you want to continue? [Y/n] y
quota not working (qgroup not set)
(Reading database … 69139 files and directories currently installed.)
Removing linux-image-6.1.0-9-arm64 (6.1.27-1) …
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-6.1.0-9-arm64
/etc/kernel/postrm.d/z50-raspi-firmware:
cp: error writing ‘/boot/firmware/initrd.img-6.1.0-11-arm64’: No space left on device
run-parts: /etc/kernel/postrm.d/z50-raspi-firmware exited with return code 1
dpkg: error processing package linux-image-6.1.0-9-arm64 (–remove):
installed linux-image-6.1.0-9-arm64 package post-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
linux-image-6.1.0-9-arm64
Processing was halted because there were too many errors.
Config is in use.
E: Sub-process /usr/bin/dpkg returned an error code (1)

vrillo · August 20, 2023, 6:06am

Then I tried another way. I looked for old kernels which can be deleted:

dpkg -l ‘linux-[ihs]’ | sed ‘/^ii/!d;/’"$(uname -r | sed "s/([-0-9])-([^0-9]+)/\1/“)”’/d;s/^[^ ]* [^ ]* ([^ ])./\1/;/[0-9]/!d’
linux-image-5.10.0-10-arm64
linux-image-6.1.0-10-arm64

But as you can see there is linux-image-6.1.0-10-arm64. This is the one which is used currently! So I can’t go on doing:
dpkg -l ‘linux-[ihs]’ | sed ‘/^ii/!d;/’"$(uname -r | sed "s/([-0-9])-([^0-9]+)/\1/“)”’/d;s/^[^ ]* [^ ]* ([^ ])./\1/;/[0-9]/!d’ | xargs sudo dpkg -P

vrillo · August 20, 2023, 9:44am

Success!

Next attempt of deleting kernels, beginning this time with linux-image-6.1.0-11-arm64

sudo apt-get remove --purge linux-image-6.1.0-11-arm64

[sudo] password for pi:
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following packages will be REMOVED:
linux-image-6.1.0-11-arm64* linux-image-6.1.0-9-arm64 linux-image-arm64*
0 upgraded, 0 newly installed, 3 to remove and 14 not upgraded.
3 not fully installed or removed.
After this operation, 711 MB disk space will be freed.
Do you want to continue? [Y/n] y
quota not working (qgroup not set)
(Reading database … 69139 files and directories currently installed.)
Removing linux-image-arm64 (6.1.38-4) …
Removing linux-image-6.1.0-11-arm64 (6.1.38-4) …
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.10.0-10-arm64
I: /initrd.img.old is now a symlink to boot/initrd.img-5.10.0-10-arm64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-10-arm64
I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-10-arm64
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-6.1.0-11-arm64
/etc/kernel/postrm.d/z50-raspi-firmware:
raspi-firmware: deleting obsolete /boot/firmware/vmlinuz-6.1.0-11-arm64 (no longer in /boot)
raspi-firmware: deleting obsolete /boot/firmware/vmlinuz-6.1.0-9-arm64 (no longer in /boot)
raspi-firmware: deleting obsolete /boot/firmware/initrd.img-6.1.0-11-arm64 (no longer in /boot)
raspi-firmware: deleting obsolete /boot/firmware/initrd.img-6.1.0-9-arm64 (no longer in /boot)
Removing linux-image-6.1.0-9-arm64 (6.1.27-1) …
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-6.1.0-9-arm64
(Reading database … 63959 files and directories currently installed.)
Purging configuration files for linux-image-arm64 (6.1.38-4) …
Purging configuration files for linux-image-6.1.0-11-arm64 (6.1.38-4) …
Config is in use.
Scanning processes…
Scanning processor microcode…
Scanning linux images…

Running kernel seems to be up-to-date.

Failed to check for processor microcode upgrades.

sudo apt-get remove --purge linux-image-5.10.0-10-arm64

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.

Afterwards:

sudo apt-get remove --purge linux-image-5.10.0-10-arm64
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following packages will be REMOVED:
linux-image-5.10.0-10-arm64*
0 upgraded, 0 newly installed, 1 to remove and 14 not upgraded.
After this operation, 256 MB disk space will be freed.
Do you want to continue? [Y/n] y
quota not working (qgroup not set)
(Reading database … 63958 files and directories currently installed.)
Removing linux-image-5.10.0-10-arm64 (5.10.84-1) …
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.1.0-10-arm64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.1.0-10-arm64
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-5.10.0-10-arm64
/etc/kernel/postrm.d/z50-raspi-firmware:
raspi-firmware: deleting obsolete /boot/firmware/vmlinuz-5.10.0-10-arm64 (no longer in /boot)
raspi-firmware: deleting obsolete /boot/firmware/initrd.img-5.10.0-10-arm64 (no longer in /boot)
(Reading database … 59384 files and directories currently installed.)
Purging configuration files for linux-image-5.10.0-10-arm64 (5.10.84-1) …
quota not working (qgroup not set)

Afterwards:

sudo dpkg -l | grep linux-image
ic linux-image-5.10.0-12-arm64 5.10.103-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-13-arm64 5.10.106-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-14-arm64 5.10.113-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-15-arm64 5.10.120-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-16-arm64 5.10.127-2 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-17-arm64 5.10.136-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-18-arm64 5.10.140-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-19-arm64 5.10.149-2 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-20-arm64 5.10.158-2 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-21-arm64 5.10.162-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-22-arm64 5.10.178-3 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
rc linux-image-5.10.0-23-arm64 5.10.179-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed)
ii linux-image-6.1.0-10-arm64 6.1.38-2 arm64 Linux 6.1 for 64-bit ARMv8 machines (signed)
rc linux-image-6.1.0-9-arm64 6.1.27-1 arm64 Linux 6.1 for 64-bit ARMv8 machines (signed)

Afterwards:

sudo apt-get remove --purge linux-image-5.10.0-12-arm64 linux-image-5.10.0-13-arm64 linux-image-5.10.0-14-arm64 linux-image-5.10.0-15-arm64 linux-image-5.10.0-16-arm64 linux-image-5.10.0-17-arm64 linux-image-5.10.0-18-arm64 linux-image-5.10.0-19-arm64 linux-image-5.10.0-20-arm64 linux-image-5.10.0-21-arm64 linux-image-5.10.0-22-arm64 linux-image-5.10.0-23-arm64 linux-image-6.1.0-9-arm64
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following packages will be REMOVED:
linux-image-5.10.0-12-arm64* linux-image-5.10.0-13-arm64* linux-image-5.10.0-14-arm64* linux-image-5.10.0-15-arm64* linux-image-5.10.0-16-arm64* linux-image-5.10.0-17-arm64* linux-image-5.10.0-18-arm64* linux-image-5.10.0-19-arm64*
linux-image-5.10.0-20-arm64* linux-image-5.10.0-21-arm64* linux-image-5.10.0-22-arm64* linux-image-5.10.0-23-arm64* linux-image-6.1.0-9-arm64*
0 upgraded, 0 newly installed, 13 to remove and 14 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
quota not working (qgroup not set)
(Reading database … 59383 files and directories currently installed.)
Purging configuration files for linux-image-6.1.0-9-arm64 (6.1.27-1) …
Purging configuration files for linux-image-5.10.0-16-arm64 (5.10.127-2) …
Purging configuration files for linux-image-5.10.0-23-arm64 (5.10.179-1) …
Purging configuration files for linux-image-5.10.0-15-arm64 (5.10.120-1) …
Purging configuration files for linux-image-5.10.0-20-arm64 (5.10.158-2) …
Purging configuration files for linux-image-5.10.0-12-arm64 (5.10.103-1) …
Purging configuration files for linux-image-5.10.0-18-arm64 (5.10.140-1) …
Purging configuration files for linux-image-5.10.0-14-arm64 (5.10.113-1) …
Purging configuration files for linux-image-5.10.0-19-arm64 (5.10.149-2) …
Purging configuration files for linux-image-5.10.0-13-arm64 (5.10.106-1) …
Purging configuration files for linux-image-5.10.0-22-arm64 (5.10.178-3) …
Purging configuration files for linux-image-5.10.0-17-arm64 (5.10.136-1) …
Purging configuration files for linux-image-5.10.0-21-arm64 (5.10.162-1) …
quota not working (qgroup not set)

Afterwards:

sudo dpkg -l | grep linux-image
ii linux-image-6.1.0-10-arm64 6.1.38-2 arm64 Linux 6.1 for 64-bit ARMv8 machines (signed)

Afterwards:

sudo apt install -t bookworm-backports freedombox
[sudo] password for pi:
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following additional packages will be installed:
freedombox-doc-en freedombox-doc-es
The following packages will be upgraded:
freedombox freedombox-doc-en freedombox-doc-es
3 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
Need to get 0 B/92.3 MB of archives.
After this operation, 17.4 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
quota not working (qgroup not set)
Preconfiguring packages …
(Reading database … 59370 files and directories currently installed.)
Preparing to unpack …/freedombox_23.15~bpo12+1_all.deb …
Unpacking freedombox (23.15~bpo12+1) over (23.14~bpo12+1) …
Preparing to unpack …/freedombox-doc-en_23.15~bpo12+1_all.deb …
Unpacking freedombox-doc-en (23.15~bpo12+1) over (23.14~bpo12+1) …
Preparing to unpack …/freedombox-doc-es_23.15~bpo12+1_all.deb …
Unpacking freedombox-doc-es (23.15~bpo12+1) over (23.14~bpo12+1) …
Setting up freedombox-doc-en (23.15~bpo12+1) …
Setting up freedombox-doc-es (23.15~bpo12+1) …
Setting up freedombox (23.15~bpo12+1) …
Processing triggers for dbus (1.14.8-2~deb12u1) …
Config is in use.
Scanning processes…
Scanning processor microcode…
Scanning linux images…

Running kernel seems to be up-to-date.

Failed to check for processor microcode upgrades.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.

Afterwards:

sudo dpkg -l | grep linux-image
ii linux-image-6.1.0-10-arm64 6.1.38-2 arm64 Linux 6.1 for 64-bit ARMv8 machines (signed)

Avron · August 20, 2023, 11:16am

Do you still have 19 packages not upgraded?

With respect to “auto-update to the next stable version”: by having that, you will be among the first people to try the upgrade and it will happen regardless whether you are away or busy with something else and forgot about this. I tend to find that risky.

vrillo · August 20, 2023, 1:24pm

You’re right: “auto-update to the next stable version” is risky indeed. So I deactivated it. Now there are no packages to be upgraded anymore. Thanks for your advices!

sudo apt update
[sudo] password for pi:
Hit:1 Index of /debian bookworm InRelease
Hit:2 Index of /debian bookworm-updates InRelease
Hit:3 Index of /debian bookworm-backports InRelease
Get:4 Index of /debian-security bookworm-security InRelease [48.0 kB]
Fetched 48.0 kB in 2s (22.8 kB/s)
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
11 packages can be upgraded. Run ‘apt list --upgradable’ to see them.
N: Repository ‘Debian bookworm’ changed its ‘non-free component’ value from ‘non-free’ to ‘non-free non-free-firmware’
N: More information about this can be found online in the Release notes at: Chapter 5. Issues to be aware of for bookworm
pi@freedombox:~$ sudo apt list --upgradable
Listing… Done
libldb2/stable-security 2:2.6.2+samba4.17.10+dfsg-0+deb12u1 arm64 [upgradable from: 2:2.6.2+samba4.17.9+dfsg-0+deb12u3]
libwbclient0/stable-security 2:4.17.10+dfsg-0+deb12u1 arm64 [upgradable from: 2:4.17.9+dfsg-0+deb12u3]
python3-ldb/stable-security 2:2.6.2+samba4.17.10+dfsg-0+deb12u1 arm64 [upgradable from: 2:2.6.2+samba4.17.9+dfsg-0+deb12u3]
python3-samba/stable-security 2:4.17.10+dfsg-0+deb12u1 arm64 [upgradable from: 2:4.17.9+dfsg-0+deb12u3]
samba-ad-provision/stable-security 2:4.17.10+dfsg-0+deb12u1 all [upgradable from: 2:4.17.9+dfsg-0+deb12u3]
samba-common-bin/stable-security 2:4.17.10+dfsg-0+deb12u1 arm64 [upgradable from: 2:4.17.9+dfsg-0+deb12u3]
samba-common/stable-security 2:4.17.10+dfsg-0+deb12u1 all [upgradable from: 2:4.17.9+dfsg-0+deb12u3]
samba-dsdb-modules/stable-security 2:4.17.10+dfsg-0+deb12u1 arm64 [upgradable from: 2:4.17.9+dfsg-0+deb12u3]
samba-libs/stable-security 2:4.17.10+dfsg-0+deb12u1 arm64 [upgradable from: 2:4.17.9+dfsg-0+deb12u3]
samba-vfs-modules/stable-security 2:4.17.10+dfsg-0+deb12u1 arm64 [upgradable from: 2:4.17.9+dfsg-0+deb12u3]
samba/stable-security 2:4.17.10+dfsg-0+deb12u1 arm64 [upgradable from: 2:4.17.9+dfsg-0+deb12u3]
pi@freedombox:~$ sudo apt upgrade
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Calculating upgrade… Done
The following packages will be upgraded:
libldb2 libwbclient0 python3-ldb python3-samba samba samba-ad-provision
samba-common samba-common-bin samba-dsdb-modules samba-libs
samba-vfs-modules
11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 11.3 MB of archives.
After this operation, 63.5 kB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 Index of /debian-security bookworm-security/main arm64 samba-vfs-modules arm64 2:4.17.10+dfsg-0+deb12u1 [404 kB]
Get:2 Index of /debian-security bookworm-security/main arm64 python3-ldb arm64 2:2.6.2+samba4.17.10+dfsg-0+deb12u1 [59.0 kB]
Get:3 Index of /debian-security bookworm-security/main arm64 libldb2 arm64 2:2.6.2+samba4.17.10+dfsg-0+deb12u1 [153 kB]
Get:4 Index of /debian-security bookworm-security/main arm64 samba-dsdb-modules arm64 2:4.17.10+dfsg-0+deb12u1 [297 kB]
Get:5 Index of /debian-security bookworm-security/main arm64 samba-common-bin arm64 2:4.17.10+dfsg-0+deb12u1 [1098 kB]
Get:6 Index of /debian-security bookworm-security/main arm64 python3-samba arm64 2:4.17.10+dfsg-0+deb12u1 [2621 kB]
Get:7 Index of /debian-security bookworm-security/main arm64 libwbclient0 arm64 2:4.17.10+dfsg-0+deb12u1 [51.6 kB]
Get:8 Index of /debian-security bookworm-security/main arm64 samba-libs arm64 2:4.17.10+dfsg-0+deb12u1 [5260 kB]
Get:9 Index of /debian-security bookworm-security/main arm64 samba-ad-provision all 2:4.17.10+dfsg-0+deb12u1 [414 kB]
Get:10 Index of /debian-security bookworm-security/main arm64 samba arm64 2:4.17.10+dfsg-0+deb12u1 [889 kB]
Get:11 Index of /debian-security bookworm-security/main arm64 samba-common all 2:4.17.10+dfsg-0+deb12u1 [85.4 kB]
Fetched 11.3 MB in 1s (11.3 MB/s)
quota not working (qgroup not set)
Preconfiguring packages …
(Reading database … 59370 files and directories currently installed.)
Preparing to unpack …/00-samba-vfs-modules_2%3a4.17.10+dfsg-0+deb12u1_arm64.deb …
Unpacking samba-vfs-modules:arm64 (2:4.17.10+dfsg-0+deb12u1) over (2:4.17.9+dfsg-0+deb12u3) …
Preparing to unpack …/01-python3-ldb_2%3a2.6.2+samba4.17.10+dfsg-0+deb12u1_arm64.deb …
Unpacking python3-ldb (2:2.6.2+samba4.17.10+dfsg-0+deb12u1) over (2:2.6.2+samba4.17.9+dfsg-0+deb12u3) …
Preparing to unpack …/02-libldb2_2%3a2.6.2+samba4.17.10+dfsg-0+deb12u1_arm64.deb …
Unpacking libldb2:arm64 (2:2.6.2+samba4.17.10+dfsg-0+deb12u1) over (2:2.6.2+samba4.17.9+dfsg-0+deb12u3) …
Preparing to unpack …/03-samba-dsdb-modules_2%3a4.17.10+dfsg-0+deb12u1_arm64.deb …
Unpacking samba-dsdb-modules:arm64 (2:4.17.10+dfsg-0+deb12u1) over (2:4.17.9+dfsg-0+deb12u3) …
Preparing to unpack …/04-samba-common-bin_2%3a4.17.10+dfsg-0+deb12u1_arm64.deb …
Unpacking samba-common-bin (2:4.17.10+dfsg-0+deb12u1) over (2:4.17.9+dfsg-0+deb12u3) …
Preparing to unpack …/05-python3-samba_2%3a4.17.10+dfsg-0+deb12u1_arm64.deb …
Unpacking python3-samba (2:4.17.10+dfsg-0+deb12u1) over (2:4.17.9+dfsg-0+deb12u3) …
Preparing to unpack …/06-libwbclient0_2%3a4.17.10+dfsg-0+deb12u1_arm64.deb …
Unpacking libwbclient0:arm64 (2:4.17.10+dfsg-0+deb12u1) over (2:4.17.9+dfsg-0+deb12u3) …
Preparing to unpack …/07-samba-libs_2%3a4.17.10+dfsg-0+deb12u1_arm64.deb …
Unpacking samba-libs:arm64 (2:4.17.10+dfsg-0+deb12u1) over (2:4.17.9+dfsg-0+deb12u3) …
Preparing to unpack …/08-samba-ad-provision_2%3a4.17.10+dfsg-0+deb12u1_all.deb …
Unpacking samba-ad-provision (2:4.17.10+dfsg-0+deb12u1) over (2:4.17.9+dfsg-0+deb12u3) …
Preparing to unpack …/09-samba_2%3a4.17.10+dfsg-0+deb12u1_arm64.deb …
Unpacking samba (2:4.17.10+dfsg-0+deb12u1) over (2:4.17.9+dfsg-0+deb12u3) …
Preparing to unpack …/10-samba-common_2%3a4.17.10+dfsg-0+deb12u1_all.deb …
Unpacking samba-common (2:4.17.10+dfsg-0+deb12u1) over (2:4.17.9+dfsg-0+deb12u3) …
Setting up samba-common (2:4.17.10+dfsg-0+deb12u1) …
Setting up libwbclient0:arm64 (2:4.17.10+dfsg-0+deb12u1) …
Setting up samba-ad-provision (2:4.17.10+dfsg-0+deb12u1) …
Setting up libldb2:arm64 (2:2.6.2+samba4.17.10+dfsg-0+deb12u1) …
Setting up samba-libs:arm64 (2:4.17.10+dfsg-0+deb12u1) …
Setting up python3-ldb (2:2.6.2+samba4.17.10+dfsg-0+deb12u1) …
Setting up samba-dsdb-modules:arm64 (2:4.17.10+dfsg-0+deb12u1) …
Setting up python3-samba (2:4.17.10+dfsg-0+deb12u1) …
Setting up samba-vfs-modules:arm64 (2:4.17.10+dfsg-0+deb12u1) …
Setting up samba-common-bin (2:4.17.10+dfsg-0+deb12u1) …
Setting up samba (2:4.17.10+dfsg-0+deb12u1) …
Processing triggers for libc-bin (2.36-9+deb12u1) …
quota not working (qgroup not set)
Scanning processes…
Scanning processor microcode…
Scanning linux images…

Running kernel seems to be up-to-date.

Failed to check for processor microcode upgrades.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.
pi@freedombox:~$ sudo apt update
Hit:1 Index of /debian-security bookworm-security InRelease
Hit:2 Index of /debian bookworm InRelease
Hit:3 Index of /debian bookworm-updates InRelease
Hit:4 Index of /debian bookworm-backports InRelease
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
All packages are up to date.
N: Repository ‘Debian bookworm’ changed its ‘non-free component’ value from ‘non-free’ to ‘non-free non-free-firmware’
N: More information about this can be found online in the Release notes at: Chapter 5. Issues to be aware of for bookworm
pi@freedombox:~$ sudo reboot

Broadcast message from root@freedombox on pts/1 (Sun 2023-08-20 15:16:31 CEST):

The system will reboot now!