On Mon, Jan 12, 2026 at 5:20 AM Chris Green <[email protected]> wrote: > > While running 'apt updata' followed by 'apt upgrade' this morning I > got the following error from dpkg:- > > ... > ... > Processing triggers for initramfs-tools (0.148.3) ... > update-initramfs: Generating /boot/initrd.img-6.12.63+deb13-amd64 > zstd: error 70 : Write error : cannot write block : No space left on > device > E: mkinitramfs failure cpio 141 > E: mkinitramfs failure zstd -q -9 -T0 70 > update-initramfs: failed for /boot/initrd.img-6.12.63+deb13-amd64 with 1. > dpkg: error processing package initramfs-tools (--configure): > installed initramfs-tools package post-installation script subprocess > returned error exit status 1 > Processing triggers for hicolor-icon-theme (0.18-2) ... > Processing triggers for cups (2.4.10-3+deb13u2) ... > Errors were encountered while processing: > initramfs-tools > Error: Sub-process /usr/bin/dpkg returned an error code (1) > ... > ... > > I can't see any obvious lack of space on any of the 'real' disk drives:- > > Filesystem Type 1M-blocks Used Avail Use% Mounted on > /dev/mapper/t470--vg-root ext4 936644 201503 687490 23% / > efivarfs efivarfs 1 1 1 56% > /sys/firmware/efi/efivars > /dev/sda1 ext4 960331 18776 892702 3% /bak > /dev/nvme0n1p2 ext2 456 264 168 62% /boot > /dev/nvme0n1p1 vfat 511 5 507 1% /boot/efi > > Even if I include tmpfs I can't see much wrong:- > Filesystem 1M-blocks Used Available Use% Mounted on > udev 3797 0 3797 0% /dev > tmpfs 772 2 770 1% /run > /dev/mapper/t470--vg-root 936644 201503 687490 23% / > tmpfs 3856 57 3800 2% /dev/shm > efivarfs 1 1 1 56% > /sys/firmware/efi/efivars > tmpfs 5 1 5 1% /run/lock > /dev/sda1 960331 18776 892702 3% /bak > /dev/nvme0n1p2 456 264 168 62% /boot > tmpfs 3856 74 3782 2% /tmp > /dev/nvme0n1p1 511 5 507 1% /boot/efi > tmpfs 1 0 1 0% > /run/credentials/[email protected] > tmpfs 772 1 772 1% /run/user/1000 > tmpfs 1 0 1 0% > /run/credentials/systemd-journald.service > > The upgrade appeared to complete OK but it would still be good to know > what the 'No space' error was about. > > Any ideas anyone?
My guess is, /boot is full. Also see <https://www.debian.org/releases/trixie/release-notes/issues.html#ensure-boot-has-enough-free-space>. Jeff
