Arch Linux

doblerone

Member

Registered: 2011-12-08

Posts: 215

no space left for regenerating img via mkinitcpio

After recent problem with mesa (same as post here), I decided to fix my system by enabling kms, as suggested by the wiki.
I enabled `MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)` in `/etc/mkinitcpio.conf` but when I try to regenerate the initramfs via `mkinitcpio -P`, I'm getting an error saying that there is no space left on the partition, because an `initramfs-linux.img.tmp` of 78M is created:

david@arch /boot> sudo mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img --microcode /boot/intel-ucode.img
==> Starting build: '6.6.8-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
zstd: error 70 : Write error : cannot write block : No space left on device 
bsdtar: Write error
bsdtar: Write error
==> ERROR: Image generation FAILED: 'bsdtar (step 1) reported an error'
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect --microcode /boot/intel-ucode.img
==> Starting build: '6.6.8-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
zstd: error 70 : Write error : cannot write block : No space left on device 
bsdtar: Write error
bsdtar: Write error
==> ERROR: Image generation FAILED: 'bsdtar (step 1) reported an error'

My /boot partition is 150M:

david@arch /boot> ll
Permissions Size User Group Date Modified Name
drwxr-xr-x     - root root  20 jun  2023   grub
.rw-------   38M root root   1 ene 16:29   initramfs-linux-fallback.img
.rw-------  9,9M root root  29 dic  2023   initramfs-linux.img
.rw-r--r--  7,4M root root  14 nov  2023   intel-ucode.img
drwx------     - root root  14 jun  2023   lost+found
.rw-r--r--   13M root root  29 dic  2023   vmlinuz-linux

Any help would be appreciated.

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,439

Website

Re: no space left for regenerating img via mkinitcpio

My /boot partition is 150M

Why?

Is this an EFI system w/ /boot as the esp?  If so, you could potentially move the esp and save some space (though 300M is the recommended minimum for esp too).  Alternatively, perhaps a different boot manager would help as grub is quite complex for what it does.

Or if you like to live dangerously, you could just go without the fallback image as that's what takes up the most space.

Last edited by Trilby (2024-01-01 15:48:37)

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

doblerone

Member

Registered: 2011-12-08

Posts: 215

Re: no space left for regenerating img via mkinitcpio

My /boot partition is 150M

Why?

Thanks for your reply. I had those numbers from an old installation. I'll keep that in mind for the future.

Or if you like to live dangerously, you could just go without the fallback image as that's what takes up the most space.

Although I had neved had to use the fallback image, I guess that's too risky

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,999

Website

Re: no space left for regenerating img via mkinitcpio

If you're using GRUB then you don't have to use the ESP for /boot/ so just move it to the root partition.

---

Jin, Jîyan, Azadî

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,960

Re: no space left for regenerating img via mkinitcpio

To fix the underlying issue it is sufficient to supply the parameters to the commandline without also enabling early loading by adding the modules to the MODULES= array if you don't want to redo your setup just now.