Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #83100 > unrolled thread
| Started by | Diederik de Haas <didi.debian@cknow.org> |
|---|---|
| First post | 2024-07-19 14:50 +0200 |
| Last post | 2024-07-19 18:10 +0200 |
| Articles | 4 — 4 participants |
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.
Bug#1076582: initramfs-tools-core: mkinitramfs failure zstd -q -9 -T0 70 (No space left on device) Diederik de Haas <didi.debian@cknow.org> - 2024-07-19 14:50 +0200
Bug#1076582: initramfs-tools-core: mkinitramfs failure zstd -q -9 -T0 70 (No space left on device) Vincent Lefevre <vincent@vinc17.net> - 2024-07-19 16:00 +0200
Bug#1076582: initramfs-tools-core: mkinitramfs failure zstd -q -9 -T0 70 (No space left on device) Chris Hofstaedtler <zeha@debian.org> - 2024-07-19 18:10 +0200
Processed: Re: Bug#1076582: initramfs-tools-core: mkinitramfs failure zstd -q -9 -T0 70 (No space left on device) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-07-19 18:10 +0200
| From | Diederik de Haas <didi.debian@cknow.org> |
|---|---|
| Date | 2024-07-19 14:50 +0200 |
| Subject | Bug#1076582: initramfs-tools-core: mkinitramfs failure zstd -q -9 -T0 70 (No space left on device) |
| Message-ID | <J1VdD-3cjY-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Control: tag -1 moreinfo On Friday, 19 July 2024 13:08:50 CEST Vincent Lefevre wrote: > 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 If you do not need all that firmware, try removing the ones you don't need. Especially if you don't need nvidia-graphics firmware, remove that because that is BIG (and the reason it got split out from misc-nonfree). It's a RECOMMENDS, so you can remove it (if you don't need it). On Friday, 19 July 2024 13:08:50 CEST Vincent Lefevre wrote: > This is wrong. There's plenty of space: > > Filesystem Size Used Avail Use% Mounted on > ... > 456M 243M 189M 57% /boot While generating the initramfs it needs a LOT more space then what's needed when the generation completes successfully. It's all the uncompressed files + the size of the compressed archived/initramfs. When done, it can remove all the uncompressed files.
[toc] | [next] | [standalone]
| From | Vincent Lefevre <vincent@vinc17.net> |
|---|---|
| Date | 2024-07-19 16:00 +0200 |
| Message-ID | <J1Wjn-3cVO-3@gated-at.bofh.it> |
| In reply to | #83100 |
On 2024-07-19 14:32:28 +0200, Diederik de Haas wrote: > On Friday, 19 July 2024 13:08:50 CEST Vincent Lefevre wrote: > > 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 > > If you do not need all that firmware, try removing the ones you > don't need. Especially if you don't need nvidia-graphics firmware, > remove that because that is BIG (and the reason it got split out > from misc-nonfree). It's a RECOMMENDS, so you can remove it (if you > don't need it). The graphics card is a Nvidia one, so I probably need this firmware. In any case, the upgrade should work for any user, including when all these packages are needed. > On Friday, 19 July 2024 13:08:50 CEST Vincent Lefevre wrote: > > This is wrong. There's plenty of space: > > > > Filesystem Size Used Avail Use% Mounted on > > ... > > 456M 243M 189M 57% /boot > > While generating the initramfs it needs a LOT more space then what's needed > when the generation completes successfully. It's all the uncompressed files + > the size of the compressed archived/initramfs. > When done, it can remove all the uncompressed files. But it would be silly to use the /boot partition (which is typically small) for storing the temporary uncompressed files. Note that https://www.debian.org/releases/stable/amd64/apcs01.en.html does not recommend anything for the /boot partition. https://www.debian.org/releases/stable/amd64/apcs05.en.html says "25–50MB should suffice" (though this is probably not sufficient for most uses). https://linuxhint.com/boot-partition-size-debian/ says 256 MB / 512 MB for Debian 11. Mine has 512 MB (more that 10 times the recommended 25–50MB). -- Vincent Lefèvre <vincent@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)
[toc] | [prev] | [next] | [standalone]
| From | Chris Hofstaedtler <zeha@debian.org> |
|---|---|
| Date | 2024-07-19 18:10 +0200 |
| Message-ID | <J1Ylb-3enm-1@gated-at.bofh.it> |
| In reply to | #83104 |
Control: retitle -1 initramfs-tools: duplicates nvidia firmware files On Fri, Jul 19, 2024 at 04:43:47PM +0200, Diederik de Haas wrote: > > In any case, the upgrade should work for any user, including when > > all these packages are needed. > > The real problem seems to be the size of /boot/ ... Not really. A large part of the problem is that initramfs explodes the size of the nvidia firmware. On the root file system, in /usr/lib/firmware, the nvidia firmware files are 66MB (uncompressed!). However, the initrd.img grows from 64M to 250M (compressed!) when firmware-nvidia-graphics is installed. There is something seriously wrong here. 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. There are probably more cases where the symlinks are not preserved. This needs to be fixed in initramfs (or whatever hook script copies the firmware files). Chris
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2024-07-19 18:10 +0200 |
| Subject | Processed: Re: Bug#1076582: initramfs-tools-core: mkinitramfs failure zstd -q -9 -T0 70 (No space left on device) |
| Message-ID | <J1Ylb-3enm-7@gated-at.bofh.it> |
| In reply to | #83110 |
Processing control commands: > retitle -1 initramfs-tools: duplicates nvidia firmware files Bug #1076582 [initramfs-tools-core] initramfs-tools-core: mkinitramfs failure zstd -q -9 -T0 70 (No space left on device) Changed Bug title to 'initramfs-tools: duplicates nvidia firmware files' from 'initramfs-tools-core: mkinitramfs failure zstd -q -9 -T0 70 (No space left on device)'. -- 1076582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076582 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web