[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Out of space error from dpkg, but I can't see where

On Mon, 12 Jan 2026, Chris Green 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
/var (/) or /boot are the two usual culprits. /var looks ample to hold the uncompressed initrd so I'd guess /boot. Look at how big your existing initrd is, you'll need at least that much space.
Setting modules=dep in initrd.conf (writing from memory so that might not be correct) will likely get you past this (I'm guessing you have modules=most) 

Tim.
Reply to: