Your message dated Wed, 24 Jul 2024 19:19:20 +0200
with message-id <35875175.SxXBtFtcgi@bagend>
and subject line Re: Bug#1076582: initramfs-tools-core: mkinitramfs failure
zstd -q -9 -T0 70 (No space left on device)
has caused the Debian Bug report #1076582,
regarding initramfs-tools: duplicates nvidia firmware files
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1076582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools-core
Version: 0.142
Severity: grave
Justification: renders package unusable
When upgrading the firmware:
[...]
Setting up firmware-intel-graphics (20240610-1) ...
Setting up firmware-iwlwifi (20240610-1) ...
Setting up firmware-misc-nonfree (20240610-1) ...
Setting up firmware-nvidia-graphics (20240610-1) ...
Setting up firmware-intel-misc (20240610-1) ...
Setting up firmware-mediatek (20240610-1) ...
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.9.9-amd64
zstd: error 70 : Write error : cannot write block : No space left on device
E: mkinitramfs failure zstd -q -9 -T0 70
update-initramfs: failed for /boot/initrd.img-6.9.9-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
initramfs-tools
====== How can you help? (doc: https://wiki.debian.org/how-can-i-help ) ======
----- Show old opportunities as well as new ones: how-can-i-help --old -----
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up initramfs-tools (0.142) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.9.9-amd64
zstd: error 70 : Write error : cannot write block : No space left on device
E: mkinitramfs failure zstd -q -9 -T0 70
update-initramfs: failed for /boot/initrd.img-6.9.9-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
initramfs-tools
This is wrong. There's plenty of space:
Filesystem Size Used Avail Use% Mounted on
udev 16G 0 16G 0% /dev
tmpfs 3.2G 5.1M 3.1G 1% /run
/dev/mapper/qaa--vg-root 915G 307G 562G 36% /
tmpfs 16G 0 16G 0% /dev/shm
efivarfs 438K 308K 126K 72% /sys/firmware/efi/efivars
tmpfs 5.0M 12K 5.0M 1% /run/lock
tmpfs 1.0M 0 1.0M 0%
/run/credentials/systemd-journald.service
tmpfs 1.0M 0 1.0M 0%
/run/credentials/systemd-udev-load-credentials.service
tmpfs 1.0M 0 1.0M 0%
/run/credentials/systemd-sysctl.service
tmpfs 1.0M 0 1.0M 0%
/run/credentials/systemd-tmpfiles-setup-dev-early.service
tmpfs 1.0M 0 1.0M 0%
/run/credentials/systemd-tmpfiles-setup-dev.service
tmpfs 1.0M 0 1.0M 0%
/run/credentials/systemd-cryptsetup@nvme0n1p3_crypt.service
/dev/nvme0n1p2 456M 243M 189M 57% /boot
tmpfs 16G 24K 16G 1% /tmp
/dev/nvme0n1p1 511M 42M 470M 9% /boot/efi
tmpfs 1.0M 0 1.0M 0%
/run/credentials/systemd-tmpfiles-setup.service
tmpfs 1.0M 0 1.0M 0%
/run/credentials/getty@tty1.service
tmpfs 3.2G 60K 3.2G 1% /run/user/1000
There was no such issue with the latest upgrades.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'),
(500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages initramfs-tools-core depends on:
ii coreutils 9.4-3.1
ii cpio 2.15+dfsg-1
ii e2fsprogs 1.47.1-1
ii klibc-utils 2.0.13-4
ii kmod 32+20240611-1
ii logsave 1.47.1-1
ii udev 256.2-1
Versions of packages initramfs-tools-core recommends:
ii busybox 1:1.36.1-9
ii zstd 1.5.6+dfsg-1
Versions of packages initramfs-tools-core suggests:
ii bash-completion 1:2.14.0-1
-- no debconf information
--
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Version: 0.143
On Wednesday, 24 July 2024 19:05:45 CEST Goffredo Baroncelli wrote:
> On 24/07/2024 10.58, Diederik de Haas wrote:
> > What IS a general solution is upgrading initramfs-tools to version 0.143
> > currently available in Experimental as that can handle symlinks to
> > *directories*, whereas 0.142 could only deal with symlinks to files.
>
> I can confirm that 0.143 solve this issue
>
> case 1) initramfs-tools 0.142, no firmware-nvidia-graphics
> ...
> case 2) initramfs-tools 0.142, firmware-nvidia-graphics 20240610-1 installed
> ...
> case 3) initramfs-tools-* 0.143, firmware-nvidia-graphics 20240610-1
> installed
>
> 0.143 0.142 nvidia blob initrd size
> ====== ===== =========== ===========
> case 1) X 74M
> case 2) X X 244M
> case 3) X X 114M
>
> size of initrd of case 3) is bigger that the size of initrd of case 1), but
> it is expected because in case 1) I don't have the nvidia binary at all.
> However case 3) is half of the case 2), and this is right because I have
> the nvidia binary but I don't have the multiple copy in the initrd.
>
> > I already mentioned this in message #44, so it's rather disappointing that
> > people insist on ranting about the problem, but not willing to try the
> > suggested solution. Or they did and just didn't care to report the results
> > back, which normally means it did fix the problem.
>
> To be fair you wrote:
>
> ) There was a relatively recent upload of initramfs-tools 0.143 to
> ) *Experimental* and I'm curious if that would help in this case.
>
> So it was not really clear that it was a solution; it seemed that it *could*
> be a possible solution; this to explain why nobody care it too much.
Yes, at that time it could be the solution and so far I had 1 indication/
confirmation on IRC that it indeed seemed to solve the issue.
But to know whether it is the solution, people who are actually affected
by it should confirm it.
Which you just did. So thanks for that :-)
> Anyhow, 0.143 solve this issue.
Thanks for testing and reporting back!
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
