You are not logged in.

#1 2024-09-04 12:44:08

originCVII
Member
Registered: 2024-09-04
Posts: 18

mkinitcpio error on kernel install

i reinstalled the kernel through pacman, and i got the following error

   
    ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
    ==> WARNING: errors were encountered during the build. The image may not be complete.
    error: command failed to execute correctly
   

so i checked

    mkinitcpio --verbose -P

and it shows;


    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
    ==> Using default configuration file: '/etc/mkinitcpio.conf'
      -> -v -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
    ==> ERROR: Invalid option -g -- '/boot/initramfs-linux.img' must be writable
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
    ==> Using default configuration file: '/etc/mkinitcpio.conf'
      -> -v -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
    ==> ERROR: Invalid option -g -- '/boot/initramfs-linux-fallback.img' must be writable
 
 

and i couldn't find any info on this "not writable" error,
so any help would be appreciated.

Offline

#2 2024-09-04 12:57:02

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 24,960

Re: mkinitcpio error on kernel install

Do you have enough diskspace on /boot, do you have a /boot partition? What output do you get from

lsblk -f
df -h /boot
ls -l /boot

(and post outputs wrapped in code and not i tags)

Last edited by V1del (2024-09-04 12:57:27)

Offline

#3 2024-09-04 12:57:12

cryptearth
Member
Registered: 2024-02-03
Posts: 1,858

Re: mkinitcpio error on kernel install

please use bbcode code tags

Offline

#4 2024-09-04 13:23:56

originCVII
Member
Registered: 2024-09-04
Posts: 18

Re: mkinitcpio error on kernel install

V1del wrote:

Do you have enough diskspace on /boot, do you have a /boot partition? What output do you get from

lsblk -f
df -h /boot
ls -l /boot

(and post outputs wrapped in code and not i tags)

1)yes, i have a 2gb /boot partition, and i have quite a bit disk space left on my root partition as well.
2)lsblk -f:

NAME   FSTYPE   FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0  squashfs 4.0                                                    0   100% /var/lib/snapd/snap/bare/5
loop1                                                                  0   100% /var/lib/snapd/snap/core20/2318
loop2                                                                  0   100% /var/lib/snapd/snap/core20/2182
loop3                                                                  0   100% /var/lib/snapd/snap/core22/1564
loop4                                                                  0   100% /var/lib/snapd/snap/core22/1586
loop5                                                                  0   100% /var/lib/snapd/snap/gnome-3-38-2004/143
loop6                                                                  0   100% /var/lib/snapd/snap/gnome-42-2204/176
loop7                                                                  0   100% /var/lib/snapd/snap/gtk-common-themes/1535
loop8                                                                  0   100% /var/lib/snapd/snap/pokemmo/275
loop9                                                                  0   100% /var/lib/snapd/snap/pokemmo/278
loop10                                                                 0   100% /var/lib/snapd/snap/snapd/21184
loop11                                                                 0   100% /var/lib/snapd/snap/snapd/21759
sda                                                                             
├─sda1 vfat     FAT32 BOOT  6828-076F                                 2G     0% /boot/efi
├─sda2 swap     1     swap  be233bb9-7e98-464f-812b-78fa7e7debe7                [SWAP]
└─sda3 ext4     1.0   root  4fd1e0b9-fc6a-4340-8fdb-6b940a987f7a  112.5G    70% /

3)df -h /boot:

Filesystem      Size  Used Avail Use% Mounted on
/dev/sda3       457G  321G  113G  75% /

4)ls -l /boot:

drwxr-xr-x    - root  1 Jan  1970  efi
drwxr-xr-x    - root  4 Sep 17:25  grub
.rw------- 125M root  4 Sep 17:41  initramfs-linux-fallback.img
.rw-------  15M root  4 Sep 17:40  initramfs-linux.img
.rw-r--r--  13M root  4 Sep 17:40  vmlinuz-linux

Offline

#5 2024-09-04 14:06:57

originCVII
Member
Registered: 2024-09-04
Posts: 18

Re: mkinitcpio error on kernel install

cryptearth wrote:

please use bbcode code tags

ohk thanks for letting me know.

Offline

#6 2024-09-04 14:37:57

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 71,612

Re: mkinitcpio error on kernel install

so i checked

   

mkinitcpio --verbose -P

As root?
What if you re-install the kernel "--verbose --debug"? Do you get lots of output you could share for the context?

Offline

#7 2024-09-04 15:41:30

originCVII
Member
Registered: 2024-09-04
Posts: 18

Re: mkinitcpio error on kernel install

seth wrote:

so i checked

   

mkinitcpio --verbose -P

As root?
What if you re-install the kernel "--verbose --debug"? Do you get lots of output you could share for the context?

i ran the previous command as root, and then i reinstalled the kernel with the --verbose and --debug parameters;

-- the latter shows

==> 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
==> Starting build: '6.10.7-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> 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'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> 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
==> Starting build: '6.10.7-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> 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: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [filesystems]
==> ERROR: binary dependency 'libboost_chrono.so.1.83.0' not found for 'mount.dwarfs'
==> ERROR: binary dependency 'libboost_iostreams.so.1.83.0' not found for 'mount.dwarfs'
==> ERROR: binary dependency 'libboost_filesystem.so.1.83.0' not found for 'mount.dwarfs'
==> ERROR: binary dependency 'libboost_program_options.so.1.83.0' not found for 'mount.dwarfs'
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
debug: call to waitpid succeeded
error: command failed to execute correctly
debug: unregistering database 'local'
debug: freeing package cache for repository 'local'
debug: unregistering database 'core'
debug: freeing package cache for repository 'core'
debug: unregistering database 'extra'
debug: unregistering database 'multilib'
debug: unregistering database 'rumpowered'
debug: unregistering database 'chaotic-aur'

--the former shows the errors highlighted below, which are present in the above as well;

==> ERROR: binary dependency 'libboost_chrono.so.1.83.0' not found for 'mount.dwarfs'
==> ERROR: binary dependency 'libboost_iostreams.so.1.83.0' not found for 'mount.dwarfs'
==> ERROR: binary dependency 'libboost_filesystem.so.1.83.0' not found for 'mount.dwarfs'
==> ERROR: binary dependency 'libboost_program_options.so.1.83.0' not found for 'mount.dwarfs'

Offline

#8 2024-09-04 15:48:37

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 71,612

Re: mkinitcpio error on kernel install

So "must be writable" was just down to the unprivileged mkinitcpio execution?
Boost is a 1.86 - rebuild https://aur.archlinux.org/packages/dwarfs

Offline

#9 2024-09-04 16:09:26

originCVII
Member
Registered: 2024-09-04
Posts: 18

Re: mkinitcpio error on kernel install

seth wrote:

So "must be writable" was just down to the unprivileged mkinitcpio execution?

yes it seems, and thankfully so.

seth wrote:

i rebuilt dwarfs, and then reinstalled the kernel, and it works fine now.

thank you for your assistance.

Offline

#10 2024-09-04 16:10:36

originCVII
Member
Registered: 2024-09-04
Posts: 18

Re: mkinitcpio error on kernel install

btw, can you please tell me how i can close the topic, or do moderators have to do it ?

Offline

#11 2024-09-04 16:16:21

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 71,612

Re: mkinitcpio error on kernel install

Mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Offline

Board footer

Powered by FluxBB