Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #83108 > unrolled thread

Bug#1076539: plymouth: Updating plymouth fails with "No space left on device"

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Diederik de Haas <didi.debian@cknow.org> - 2024-07-19 17:40 +0200
    Processed: Re: Bug#1076539: plymouth: Updating plymouth fails  with "No space left on device" "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-07-19 17:40 +0200
    Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Diederik de Haas <didi.debian@cknow.org> - 2024-07-19 20:10 +0200
      Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Diederik de Haas <didi.debian@cknow.org> - 2024-07-23 16:20 +0200

#83108 — Bug#1076539: plymouth: Updating plymouth fails with "No space left on device"

[Multipart message — attachments visible in raw view] — view raw

Control: severity -1 important

On Thursday, 18 July 2024 10:54:48 CEST Diederik de Haas wrote:
> Control: severity -1 minor
> 
> On 18 Jul 2024 09:43:38 +0200 Bastian Venthur <venthur@debian.org> wrote:
> > Package: plymouth
> > Version: 24.004.60-2
> > Severity: important
> > X-Debbugs-Cc: venthur@debian.org
> > 
> > Dear Maintainer,
> > 
> > trying to update plymouth fails with "No space left on device":
> > 
> > sudo aptitude -u
> > Performing actions...
> > Setting up initramfs-tools (0.142) ...
> > update-initramfs: deferring update (trigger activated)
> > Setting up plymouth (24.004.60-2) ...
> > update-initramfs: Generating /boot/initrd.img-6.9.9-amd64
> > ...
> > W: Possible missing firmware /lib/firmware/amdgpu/smu_14_0_2.bin for
> > module amdgpu 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 plymouth (--configure):
> >  installed plymouth package post-installation script subprocess returned
> >  error exit status 1> 
> > dpkg: dependency problems prevent configuration of plymouth-label:
> >  plymouth-label depends on plymouth (= 24.004.60-2); however:
> >   Package plymouth is not configured yet.
> > 
> > /boot still has 170MB free:
> > 
> > # df -h /boot
> > Filesystem      Size  Used Avail Use% Mounted on
> > /dev/nvme0n1p2  471M  275M  172M  62% /boot
> 
> I fail to see how this is any package's problem.
> Your boot partition is too small to perform the requested operation.
> 
> During compression it needs the space for the uncompressed files and
> the space needed for the compressed archive, so it generally needs
> (much) more space then it finally needs as the uncompressed files will
> be removed again once the compressed archive is complete.

Looks like I was incorrect on that one; from 929424#10 :
"initramfs-tools doesn't store temporary files on /boot"

Apologies for that.

Today I learned something new and that is that plymouth includes
GPU modules AND their firmware in the initramfs.
And with the now much larger firmware packages/files, that made
the actual problem much more urgent.

> Solution: make your boot partition larger. Or remove older/other
> kernels, but IMO this will only delay the inevitable.

And that is IMO still the actual issue.

Due to a VERY similar bug report, I was made aware of some rather
horrific advise ... in the official Debian documentation:
https://bugs.debian.org/1076582#27

On the d-i size (in code) things were apparently already evolved into
this century, but I still think 512MB for /boot partition is problematic.
And even more so when plymouth is in the mix, where (too many?) firmware
files get included in initramfs.

> Reducing severity to minor, but I actually think it should just be closed.

So I bumped up the severity, but not reassigned it as I think it's useful
if all these reports came in on the same Mailing List, which in this case
is the debian-kernel ML ...

> On 18 Jul 2024 10:17:20 +0200 Laurent Bigonville <bigon@debian.org> wrote:
> > It's related to firmware-misc-nonfree that is now pulling
> > firmware-nvidia-graphics that contains a lot of (non-free) firmwares.
> > 
> > With firmware-nvidia-graphics installed, my initramfs grows to something
> > like 200M compared to 64M without it.
> 
> The firmware-nvidia-graphics package was created exactly because its size
> got big(ger) and (partially therefor) deserved its own package instead of
> making the firmware-misc-nonfree extremely large. That package is meant
> for 'the other' firmware which don't deserve their own package.
> The firmware-nvidia-graphics is recommended by firmware-misc-nonfree as
> the nvidia graphics firmware files were moved from the latter to the former.
> 
> Solution: If you don't need firmware-nvidia-graphics, don't install it.
> If you do need it, but don't have the space for it, then increase your
> storage size.

That's still correct (though).
But it may be useful to extend the NEWS to be more explicit and verbose
about the potential consequences.

Cheers,
  Diederik

[toc] | [next] | [standalone]

#83109 — Processed: Re: Bug#1076539: plymouth: Updating plymouth fails with "No space left on device"

Processing control commands:

> severity -1 important
Bug #1076539 [firmware-misc-nonfree] plymouth: Updating plymouth fails with "No space left on device"
Severity set to 'important' from 'minor'

-- 
1076539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076539
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#83119

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 moreinfo

On Friday, 19 July 2024 17:27:39 CEST Diederik de Haas wrote:
> Today I learned something new and that is that plymouth includes
> GPU modules AND their firmware in the initramfs.

And learned something else via https://bugs.debian.org/1076582#37 :

On vrijdag 19 juli 2024 17:56:30 CEST Chris Hofstaedtler wrote:
> One of the things I've noticed:
> 
> /usr/lib/firmware/nvidia/tu104/gsp is supposed to be a symlink to
> /usr/lib/firmware/nvidia/tu102/gsp. However, in initrd.img, this is
> a copy of the directory; accounting for 25M on its own.
> 
> No wonder the initrd is way too large.

They are symlinks in the firmware-nvidia-graphics package, which leads
to initramfs-tools being the problem.

In *Experimental* there's version 0.143 and there's at least 1 report
that that keeps the symlinks (IOW: fixes the problem most likely)

Can you test whether the problem is indeed fixed with initramfs-tools
version 0.143?

[toc] | [prev] | [next] | [standalone]

#83147

[Multipart message — attachments visible in raw view] — view raw

Control: reassign -1 src:initramfs-tools 0.142
Control: fixed -1 0.143

On Friday, 19 July 2024 20:05:52 CEST Diederik de Haas wrote:
> Control: tag -1 moreinfo
> 
> On Friday, 19 July 2024 17:27:39 CEST Diederik de Haas wrote:
> They are symlinks in the firmware-nvidia-graphics package, which leads
> to initramfs-tools being the problem.
> 
> In *Experimental* there's version 0.143 and there's at least 1 report
> that that keeps the symlinks (IOW: fixes the problem most likely)
> 
> Can you test whether the problem is indeed fixed with initramfs-tools
> version 0.143?

No response, so I guess that means the problem is fixed with initramfs-tools 
version 0.143, so closing the bug with that version.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web