Hi Alexus

"Spazio esaurito sul device" means there is no space left on the device, in
this case where /boot is. Free up some space by removing old kernel images:

    apt purge linux-image-<xxx>

Replace <xxx> with the correct ending of an unused kernel package you have
installed, like 5.10.0-16-amd64. Do not remove your running kernel though
(uname -a). Check before that my guess is correct:

    df -h

Regards, Adrian.


In der Nachricht vom Sunday, 7 January 2024 13:06:20 CET schrieb al3xu5 via
Dng:
> Hi all
>
> My sister has a pc desktop and a laptop I installed to her with Chimaera
> some time ago.
>
> Yesterday she asked me to upgrade both these machines, so I did a
> dist-upgrade from chimaera to daedalus on both, following this procedure:
> - # apt-get update && upgrade (on the existing chimaera installation)
> - change /etc/apt/sources.list pointing to the Daedalus repositories
> - # apt-get update
> - # apt-get upgrade
> - # apt-get dist-upgrade
>
> Now on both the machines I have this error (some part of the message is in
> Italian, but I think you can understand the problem):
>
> ~~~
> Elaborazione dei trigger per initramfs-tools (0.142)...
> update-initramfs: Generating /boot/initrd.img-5.10.0-16-amd64
> W: No zstd in /usr/bin:/sbin:/bin, using gzip
> cpio: errore di scrittura: Spazio esaurito sul device
> E: mkinitramfs failure cpio 2
> update-initramfs: failed for /boot/initrd.img-5.10.0-16-amd64 with 1.
> dpkg: errore nell'elaborare il pacchetto initramfs-tools (--configure):
> il sottoprocesso installato pacchetto initramfs-tools script
> post-installation ha restituito lo stato di errore 1
> ~~~
>

> Some clarifications:
> - / and /boot are on the same partition which has several GB of free space
> - it cannot be resolved with (these commands lead to the same error):
>     # apt-get -f install
>     # apt-get dist-upgrade
> - installed kernel is 5.10.0-16, not the 6.x kernel
> - I can't install a kernel other than 5.10.0-16: I always get the same
> error...

>
> I can't figure out what the cause could be. But -- more importantly -- I
> can't find a solution... Please help!
>
> Another observation: searching online I found this:
> https://groups.google.com/g/linux.debian.bugs.dist/c/lc3j09Tdu5M
> The problem seems similar (even if it refers to a live-install) and the
> resulting suspicion is that there may be some connection with the (infamous)
> usr merge... But of course it may have nothing to do with it.
>
> Please, help.
> Thanks in advance
>
> Regards
> alexus