[SOLVED] Arch won't start after reboot, can't execute init (error -8)

kitchen_ace · 2023-03-13 11:44:43

I was getting an error about tmpfs being full, so I thought a reboot would fix the problem. Instead Arch will no longer boot at all.
Here's a photo of the output with loglevel=7: https://i.imgur.com/OaIam3v.jpg

some key messages:

request_module: kmod_concurrent_max (0) close to 0 (max_modprobes: 50), for module binfmt-0000, throttling...
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)

I use the LTS kernel but trying the regular one doesn't work either, nor do fallback initramfs entries.

Computer is an Intel i7-11800H with Nvidia 3060 card, full specs at https://www.gigabyte.com/Laptop/AORUS-1 … -Gen/sp#sp (KD model) in case it matters.

I keep it up to date regularly, I had just done an update which is what gave me one of the tmpfs full errors. Can't remember the message exactly, sorry.

The only thing I can remember doing differently lately was running xboxdrv -d --mimic-xpad --force-feedback to play a Windows game.

fstab:

# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=4E32-E726                            /boot/efi      vfat    defaults,noatime 0 2
UUID=85234389-d715-4d5a-ad4d-3d24978f8c18 /              ext4    defaults,noatime 0 1

typical grub entry:

        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_gpt
        insmod ext2
        search --no-floppy --fs-uuid --set=root 85234389-d715-4d5a-ad4d-3d24978f8c18
        echo    'Loading Linux linux-lts ...'
        linux   /boot/vmlinuz-linux-lts root=UUID=85234389-d715-4d5a-ad4d-3d24978f8c18 rw  loglevel=3 nowatchdog nvme_load=YES nvidia-drm.modeset=1 ibt=off
        echo    'Loading initial ramdisk ...'
        initrd  /boot/intel-ucode.img /boot/initramfs-linux-lts.img

Last edited by kitchen_ace (2023-03-13 14:11:16)

seth · 2023-03-13 13:16:56

Rebuild the initramfs, pay close attention to errors.
The init binary in the initramfs isn't executable/is corrupted what could indicate that your boot partition is out of space.
Also "df -h" itr.

kitchen_ace · 2023-03-13 14:10:09

Well, rebuilding initramfs worked and now the system boots again, and tmpfs is back to normal. I can only assume whatever caused the tmpfs problems made it so an attempt to build initramfs previously failed and I didn't catch the error.

Thanks.

Arch Linux

#1 2023-03-13 11:44:43

[SOLVED] Arch won't start after reboot, can't execute init (error -8)

#2 2023-03-13 13:16:56

Re: [SOLVED] Arch won't start after reboot, can't execute init (error -8)

#3 2023-03-13 14:10:09

Re: [SOLVED] Arch won't start after reboot, can't execute init (error -8)

Board footer