Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#76665 - [mkinitcpio] initramfs fallback image is too large for a dual-boot 100 MiB EFI partition
Attached to Project:
Arch Linux
Opened by Guillaume Delacourt (Feufochmar) - Friday, 25 November 2022, 07:47 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 30 November 2022, 06:52 GMT
Opened by Guillaume Delacourt (Feufochmar) - Friday, 25 November 2022, 07:47 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 30 November 2022, 06:52 GMT
|
DetailsDescription:
After upgrading today (notably updating mkinitcpio), I noticed the messages when initramfs images were built : [...] ==> Creating zstd-compressed initcpio image: /boot/initramfs-linux.img zstd: error 25 : Write error : No space left on device (cannot write compressed block) ==> ERROR: Image generation FAILED: zstd reported an error [...] ==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-fallback.img zstd: error 25 : Write error : No space left on device (cannot write compressed block) ==> ERROR: Image generation FAILED: zstd reported an error My /boot partition is a 100 MiB partition, originally from a pre-installed Windows 10. Since I don't use the Windows installation, I can remove files needed for a Windows boot, but that render a dual boot impossible. After removing files from the /boot partition and trigging another initramfs regeneration, the initramsfs-linux.img is built (it is around 15 MiB), but not the initramfs-linux-fallback.img which is around 64 MiB when zstd reports the write error. This is way too large for a dual-boot EFI partition. When downgrading the mkinitcpio package to version 32-2, the images are built without triggering the write error. The initramfs-linux.img is then around 9 MiB and the initramfs-linux-fallback.img around 36 MiB. Additional info: * version package : mkinitcpio 33-1 |
This task depends upon
Closed by Toolybird (Toolybird)
Wednesday, 30 November 2022, 06:52 GMT
Reason for closing: None
Additional comments about closing: "Increase in size comes from new default values for hooks (notably the kms hook). Recommended size for /boot were at least 200 MiB in 2017, the time I installed ArchLinux on the computer, though the efi partition from the Windows preinstallation was only 100 MiB."
Wednesday, 30 November 2022, 06:52 GMT
Reason for closing: None
Additional comments about closing: "Increase in size comes from new default values for hooks (notably the kms hook). Recommended size for /boot were at least 200 MiB in 2017, the time I installed ArchLinux on the computer, though the efi partition from the Windows preinstallation was only 100 MiB."
For example, the kms hook when using nvidia is going to make things very large.
COMPRESSION="xz"
COMPRESSION_OPTIONS=(-9e)
Was there discussion about image size when setting the new defaults ? The wiki doesn't seems to point size issues with the kms hook. Since preinstalled Windows are likely to come with a 100 MiB partition, I'm unsure setting kms in the default hooks is a right decision.
If you are using a smaller partition than recommended, is reasonable to have to make adjustments. In this case, by editing /etc/mkinitcpio.conf to compress more.