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

Groups > linux.debian.bugs.dist > #1204700 > unrolled thread

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

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Bastian Venthur <venthur@debian.org> - 2024-07-18 09:50 +0200
    Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Laurent Bigonville <bigon@debian.org> - 2024-07-18 10:30 +0200
    Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Laurent Bigonville <bigon@debian.org> - 2024-07-18 11:20 +0200
      Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Diederik de Haas <didi.debian@cknow.org> - 2024-07-18 11:50 +0200
    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
      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
    Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Max Görner <max+reportbug@familie-goerner.eu> - 2024-07-23 15:50 +0200

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

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/ip_discovery.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_3_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_2_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vcn_5_0_0.bin for module amdgpu
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

# du -h /boot
12K	./lost+found
4,0K	./efi/EFI/debian/fw
4,5M	./efi/EFI/debian
4,5M	./efi/EFI
4,5M	./efi
5,1M	./grub/locale
2,4M	./grub/fonts
3,2M	./grub/x86_64-efi
13M	./grub
279M	.


# ls -lh /boot
total 262M
-rw-r--r-- 1 root root 270K 13. Jul 17:45 config-6.9.9-amd64
drwx------ 3 root root 4,0K  1. Jan 1970  efi
drwxr-xr-x 5 root root 1,0K 16. Jul 08:37 grub
-rw-r--r-- 1 root root 251M 16. Jul 12:47 initrd.img-6.9.9-amd64
drwx------ 2 root root  12K 26. Jan 2021  lost+found
-rw-r--r-- 1 root root   83 13. Jul 17:45 System.map-6.9.9-amd64
-rw-r--r-- 1 root root 9,2M 13. Jul 17:45 vmlinuz-6.9.9-amd64


Cheers,

Bastian


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.9.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 plymouth depends on:
ii  init-system-helpers  1.66
ih  initramfs-tools      0.142
ii  libc6                2.39-4
ii  libdrm2              2.4.121-2
ii  libplymouth5         24.004.60-2
ii  systemd              256.2-1
ii  udev                 256.2-1

plymouth recommends no packages.

Versions of packages plymouth suggests:
ii  desktop-base     12.0.6+nmu1
pn  plymouth-themes  <none>

-- no debconf information

[toc] | [next] | [standalone]

#1204704

reassign 1076539 firmware-misc-nonfree 20240610-1
severity 1076539 serious
affects 1076539 + plymouth
thanks

Le 18/07/24 à 09:43, Bastian Venthur a écrit :
> Dear Maintainer,
>
> trying to update plymouth fails with "No space left on device":

Hello, I also had the problem this morning, but it's not related to 
plymouth.

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.

I'm reassigning this to firmware-misc-nonfree

Kind regards,

Laurent Bigonville

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

#1204706

Le 18/07/24 à 10:54, Diederik de Haas a écrit :
> Control: severity -1 minor
>
> [...]
> 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.
>
> Solution: make your boot partition larger. Or remove older/other
> kernels, but IMO this will only delay the inevitable.
>
> Reducing severity to minor, but I actually think it should just be closed.
>
> 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.

Well you change expectation from users that have firmware-misc-nonfree 
installed by pulling that huge package

IMVHO, a lot of people with firmware-misc-nonfree installed will 
experience an issue when updating.

The /boot partition size I've here is the default one from the 
debian-installer

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

#1204710

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

On Thursday, 18 July 2024 11:11:23 CEST Laurent Bigonville wrote:
> Well you change expectation from users that have firmware-misc-nonfree
> installed by pulling that huge package

I fail to see how. If those files weren't split into their own packages, the 
updated/new firmware-misc-nonfree would've contained the firmware of
the 'old' misc-nonfree + nvidia-graphics + intel-graphics + mediatek/ralink + 
new files that would otherwise have been added for misc-nonfree.

See also https://bugs.debian.org/1057786

> IMVHO, a lot of people with firmware-misc-nonfree installed will
> experience an issue when updating.

You should've seen a NEWS entry informing you of the changes.
If that didn't happen, that's a problem/bug.

On donderdag 18 juli 2024 11:14:35 CEST you wrote:
> On 18.07.24 11:11, Laurent Bigonville wrote:
> > The /boot partition size I've here is the default one from the
> > debian-installer
> 
> This seems to be the core of the problem. In my case it is 500MB, and
> was the default from the install. So many users will be affected by default.

I do agree with that. And the kernel size growing bigger contributed to that 
becoming a (bigger) problem. (There are bug reports about that)

When I set up my system, I made /boot 2G because I foresaw this problem
(and I intended to do a bit more with kernels then the average user).

I think a very valid argument can be made to change the default in d-i,
but to be blunt: you *accepted* the *defaults*.

But most people are probably not as experienced with Debian as the two of you 
which in turn would make me point out the same problem, but be more subtle/
gentle about it.

Still, "No space left on device" is not a packaging problem.

Cheers,
  Diederik

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

#1204860

[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] | [prev] | [next] | [standalone]

#1204871

[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]

#1205260

[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] | [next] | [standalone]

#1205255

Package: firmware-linux-nonfree
Version: 20240610-1
Followup-For: Bug #1076539

Dear Maintainer,

today I was hit by the reported bug on Testing. I find this extremely
unfortunate, as now I am unable to do anything that would trigger
updating the initramfs. This includes purging `plymouth` and
`firmware-nvidia-graphics` using `apt purge`.

I understand the desire for more space available on `/boot`. However, I
am very sceptical that breaking systems which are functional for a very
long time is the correct migration strategy. If not addressed, this bug
will break systems of users who want to upgrade from Bookworm to Trixie
after it is released. Again, this seems to be highly undesirable.

Are there any recommendations how this situation can be fixed? Right now
I am unable to update Kernels. Additionally, I am afraid to reboot. I'd
like to avoid having to change partition sizes, though.

Thank you very much for your attention.

Best
Max Görner



-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.9.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firmware-linux-nonfree depends on:
ii  firmware-amd-graphics  20240610-1
ii  firmware-misc-nonfree  20240610-1

Versions of packages firmware-linux-nonfree recommends:
ii  amd64-microcode  3.20240116.2+nmu1
pn  intel-microcode  <none>

firmware-linux-nonfree suggests no packages.

-- no debconf information

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web