[SOLVED] modprobe binfmt-0000 cannot be processed

setevoy · 2025-01-13 12:48:54

Hi.
During an upgrade, my terminal was killed (just exited), and `pacman` process was killed too.
After re-launching Konsole, I've restarted upgrade process, and it was finished kind of successfully.
But then, after rebooting OS, I've got the error:

request_module: modprobe binfmt-0000 cannot be processed, kmod busy with 50 threads for more than 5 seconds now

Run /init as init process
failed to execute /init (error -8)
Run /sbin/init as init process
Starting init: /sbin/init exists but couldn't execute it (error -8)

Found a similar topic here , but running `mkinitcpio -p linux` didn't help, still getting the same eror.
Although files in `/boot/` (`initramfs` and `vmlinuz`) were updated (actually, I just moved the old ones, and new were created).

The root partition has enough space, tmpfs too, the SSD disk is working, because I'm able to mount my LMV partitions to an Arch Linux "LiveUSB", can see my data.

Any help?

Last edited by setevoy (Yesterday 11:53:15)

astralc · 2025-01-13 13:27:32

check what you installed when the terminal closed (in pacman.log) and install it again (overwrite files only if needed)

Last edited by astralc (2025-01-13 13:27:55)

setevoy · Yesterday 10:23:53

Hi, @astralc
Thanks for reminding me about logs, forgot about that :facepalm:
Didn't had problems with pacman for years.

So, indeed, during my upgrade there was an issue with available disc space in the /tmp:

[2025-01-13T12:09:47+0200] [ALPM] running '90-mkinitcpio-install.hook'...
[2025-01-13T12:09:48+0200] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2025-01-13T12:09:48+0200] [ALPM-SCRIPTLET] ==> Using configuration file: '/etc/mkinitcpio.conf'
[2025-01-13T12:09:48+0200] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2025-01-13T12:09:48+0200] [ALPM-SCRIPTLET] /usr/lib/initcpio/functions: line 1160: echo: write error: No space left on device
[2025-01-13T12:09:48+0200] [ALPM-SCRIPTLET] /usr/lib/initcpio/functions: line 1181: printf: write error: No space left on device
[2025-01-13T12:09:48+0200] [ALPM-SCRIPTLET] install: error writing '/tmp/mkinitcpio.XWdMSD/root/usr/lib/os-release': No space left on device
[2025-01-13T12:09:48+0200] [ALPM-SCRIPTLET] ==> Starting build: '6.12.9-arch1-1'
[2025-01-13T12:09:48+0200] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2025-01-13T12:09:48+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.XWdMSD/root/bin/busybox': No space left on device
...
[2025-01-13T12:09:50+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.XWdMSD/root/lib/modules/6.12.9-arch1-1/modules.order': No space left on device
[2025-01-13T12:09:50+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.XWdMSD/root/lib/modules/6.12.9-arch1-1/kernel/drivers/hid/hid-generic.ko.zst: Invalid argument

But after that, when I booted from Arch USB, and ran mkinitcpio everything went good with no errors:

[2025-01-13T11:55:25+0000] [PACMAN] Running 'pacman -r /mnt/root/ -Sy --config=/tmp/pacman.conf.9CfG --disable-sandbox --cachedir=/mnt/root//var/cache/pacman/pkg --noconfirm base linux linux-firmware'
[2025-01-13T11:55:25+0000] [PACMAN] synchronizing package lists
[2025-01-13T11:55:28+0000] [ALPM] transaction started
[2025-01-13T11:55:28+0000] [ALPM] reinstalled base (3-2)
[2025-01-13T11:55:29+0000] [ALPM] reinstalled linux (6.12.9.arch1-1)
[2025-01-13T11:55:29+0000] [ALPM] reinstalled linux-firmware (20241210.b00a7f7e-1)
[2025-01-13T11:55:29+0000] [ALPM] transaction completed
[2025-01-13T11:55:30+0000] [ALPM] running '30-systemd-update.hook'...
[2025-01-13T11:55:30+0000] [ALPM] running '60-depmod.hook'...
[2025-01-13T11:55:31+0000] [ALPM] running '90-mkinitcpio-install.hook'...
[2025-01-13T11:55:32+0000] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2025-01-13T11:55:32+0000] [ALPM-SCRIPTLET] ==> Using configuration file: '/etc/mkinitcpio.conf'
[2025-01-13T11:55:32+0000] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2025-01-13T11:55:32+0000] [ALPM-SCRIPTLET] ==> Starting build: '6.12.9-arch1-1'
[2025-01-13T11:55:32+0000] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2025-01-13T11:55:32+0000] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2025-01-13T11:55:33+0000] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2025-01-13T11:55:33+0000] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2025-01-13T11:55:33+0000] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2025-01-13T11:55:33+0000] [ALPM-SCRIPTLET]   -> Running build hook: [lvm2]
[2025-01-13T11:55:34+0000] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2025-01-13T11:55:34+0000] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2025-01-13T11:55:34+0000] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2025-01-13T11:55:35+0000] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2025-01-13T11:55:35+0000] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
[2025-01-13T11:55:35+0000] [ALPM-SCRIPTLET]   -> Early uncompressed CPIO image generation successful
[2025-01-13T11:55:35+0000] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2025-01-13T11:55:35+0000] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2025-01-13T11:55:35+0000] [ALPM-SCRIPTLET] ==> Using configuration file: '/etc/mkinitcpio.conf'
[2025-01-13T11:55:35+0000] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2025-01-13T11:55:35+0000] [ALPM-SCRIPTLET] ==> Starting build: '6.12.9-arch1-1'
[2025-01-13T11:55:35+0000] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2025-01-13T11:55:36+0000] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2025-01-13T11:55:36+0000] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2025-01-13T11:55:36+0000] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2025-01-13T11:55:37+0000] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qed'
[2025-01-13T11:55:37+0000] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'wd719x'
[2025-01-13T11:55:37+0000] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla1280'
[2025-01-13T11:55:37+0000] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla2xxx'
[2025-01-13T11:55:37+0000] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'bfa'
[2025-01-13T11:55:37+0000] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'aic94xx'
[2025-01-13T11:55:39+0000] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'xhci_pci_renesas'
[2025-01-13T11:55:41+0000] [ALPM-SCRIPTLET]   -> Running build hook: [lvm2]
[2025-01-13T11:55:42+0000] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2025-01-13T11:55:43+0000] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2025-01-13T11:55:45+0000] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2025-01-13T11:55:48+0000] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2025-01-13T11:55:48+0000] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
[2025-01-13T11:55:49+0000] [ALPM-SCRIPTLET]   -> Early uncompressed CPIO image generation successful
[2025-01-13T11:55:49+0000] [ALPM-SCRIPTLET] ==> Initcpio image generation successful

And files in the /boot looks good:

[root@archiso ~]# ls -l /mnt/boot/
total 135748
drwxr-xr-x 2 root root     4096 Dec  7  2020 EFI
-rw------- 1 root root 41469096 Jan 13 11:56 initramfs-linux-fallback.img
-rw------- 1 root root 41469096 Jan 13 11:38 initramfs-linux-fallback.img-bkp
-rw------- 1 root root 14205680 Jan 13 11:56 initramfs-linux.img
-rw------- 1 root root 14205680 Jan 13 11:38 initramfs-linux.img-bkp
-rw-r--r-- 1 root root 13812224 Jan 13 11:55 vmlinuz-linux
-rw-r--r-- 1 root root 13812224 Jan 13 11:37 vmlinuz-linux-bkp

The `-bkp` postfixed there are ones I moved before running mkinitcpio to make sure that files are created from scratch.

So, after re-build the initramfs, everything must be fixed, but no :-(

The re-building initramfs was:

# pacstrap /mnt base linux linux-firmware
# arch-chroot /mnt/
# mkinitcpio -p linux

Last edited by setevoy (Yesterday 10:26:17)

setevoy · Yesterday 11:46:28

Okay, solved.
That's wierd :-)

I completely forgot that I have a dedicated partinon for my /boot.

So, what I did before was hjust mounting my /dev/vg_arch/root to the /mtt, and then running mkinitcpio there.
Instead, I have to mount /dev/vg_arch/root && mount /dev/nvme0n1p2 /mnt/boot/.

So, the partitions are:

[root@archiso ~]# lsblk 
NAME             MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0              7:0    0 820.6M  1 loop /run/archiso/airootfs
sda                8:0    1  28.9G  0 disk 
└─sda1             8:1    1  28.9G  0 part 
nvme0n1          259:0    0 465.8G  0 disk 
├─nvme0n1p1      259:1    0   512M  0 part 
├─nvme0n1p2      259:2    0     1G  0 part 
├─nvme0n1p3      259:3    0    32G  0 part 
└─nvme0n1p4      259:4    0 432.3G  0 part 
  ├─vg_arch-root 254:0    0   100G  0 lvm  /mnt
  └─vg_arch-home 254:1    0 332.3G  0 lvm  /mnt/home

And when I checked my fstab, I saw that there is dedicated /boot:

13:35:36 [root@archiso /]  # cat /etc/fstab 
# /dev/mapper/vg_arch-root
UUID=8569a65c-d848-427d-bcd0-5046d0e07f2b       /               ext4            rw,relatime     0 1

# /dev/mapper/vg_arch-home
UUID=0ae5ba43-3bb3-4826-8570-8918a82bf27f       /home           ext4            rw,relatime     0 2

# /dev/nvme0n1p1
UUID=54C4-1990          /boot/EFI       vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro       0 2

# /dev/nvme0n1p2
UUID=6a42ffb4-6811-4176-b26e-873f49aea3b0       /boot           ext2            rw,relatime     0 2

# /dev/nvme0n1p3
UUID=08d2ae9d-28fa-4d20-9d06-72d1b7fdc21d       none            swap            defaults        0 0

Everything is working now.

Arch Linux

#1 2025-01-13 12:48:54

[SOLVED] modprobe binfmt-0000 cannot be processed

#2 2025-01-13 13:27:32

Re: [SOLVED] modprobe binfmt-0000 cannot be processed

#3 Yesterday 10:23:53

Re: [SOLVED] modprobe binfmt-0000 cannot be processed

#4 Yesterday 11:46:28

Re: [SOLVED] modprobe binfmt-0000 cannot be processed

Board footer