/bin/init exists but couldn't execute it (error -8)

This forum is for discussion about general software issues.

/bin/init exists but couldn't execute it (error -8)

Postby SomeGuy » Tue Jan 18, 2022 5:57 am

Hi,

I've extracted the rootfs according to instructions with bsdtar to a root partition. I have another FAT poartition on this SD Card with the kernel and the dtb file. it starts to boot fine but doesn't complete, it gets to:
Code: Select all
[    2.130381] Run /sbin/init as init process
[    2.186062] request_module: kmod_concurrent_max (0) close to 0 (max_modprobes: 50), for module binfmt-0000, throttling...
[    7.404188] request_module: modprobe binfmt-0000 cannot be processed, kmod busy with 50 threads for more than 5 seconds now
[    7.418934] Starting init: /sbin/init exists but couldn't execute it (error -8)
[    7.437406] Run /etc/init as init process
[    7.451369] Run /bin/init as init process
[    7.462442] request_module: kmod_concurrent_max (0) close to 0 (max_modprobes: 50), for module binfmt-0000, throttling...
[   12.537018] request_module: modprobe binfmt-0000 cannot be processed, kmod busy with 50 threads for more than 5 seconds now
[   12.551740] Starting init: /bin/init exists but couldn't execute it (error -8)
[   12.570123] Run /bin/sh as init process
[   12.590015] request_module: kmod_concurrent_max (0) close to 0 (max_modprobes: 50), for module binfmt-0000, throttling...
[   17.669870] request_module: modprobe binfmt-0000 cannot be processed, kmod busy with 50 threads for more than 5 seconds now
[   17.684650] Starting init: /bin/sh exists but couldn't execute it (error -8)
[   17.703046] Kernel panic - not syncing: No working init found.  Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
[   17.717206] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.19.165-cip41-yocto-standard #1
[   17.725108] Hardware name: Evaluation board based on r9a07g044l2 (DT)
[   17.731535] Call trace:
[   17.733989]  dump_backtrace+0x0/0x198
[   17.737645]  show_stack+0x14/0x20
[   17.740956]  dump_stack+0xa8/0xd0
[   17.744267]  panic+0x140/0x29c
[   17.747317]  kernel_init+0xec/0x104
[   17.750799]  ret_from_fork+0x10/0x18
[   17.754369] SMP: stopping secondary CPUs
[   17.758284] Kernel Offset: disabled
[   17.761764] CPU features: 0x4,20002218
[   17.765503] Memory Limit: none
[   17.768555] ---[ end Kernel panic - not syncing: No working init found.  Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. ]---


I have verified that the files are executable on the SD Card on my Desktop and that looks fine:
Code: Select all
user@Desktop /r/m/u/1327444c-38c6-4b88-83fb-c1da950ee6c6> cd sbin/
user@Desktop /r/m/u/1/sbin> pwd
/run/media/user/1327444c-38c6-4b88-83fb-c1da950ee6c6/sbin
user@Desktop /r/m/u/1/sbin> ls -l init
lrwxrwxrwx 1 root root 22 Nov 12 06:10 init -> ../lib/systemd/systemd
user@Desktop /r/m/u/1/sbin> ls -l sh
lrwxrwxrwx 1 root root 4 May 12  2021 sh -> bash


Why can /sbin/init not be executed? The FS on the partition is ext4
SomeGuy
 
Posts: 1
Joined: Tue Jan 18, 2022 5:39 am

Re: /bin/init exists but couldn't execute it (error -8)

Postby Mettacrawler » Wed Jan 26, 2022 1:03 am

Error number eight is ENOEXEC Exec format error

ENOEXEC
An executable is not in a recognized format, is for the wrong
architecture, or has some other format error that means it can‐
not be executed.

I think the "wrong architecture" part is the issue. Please make sure you pick the rootfs that is the correct type for the computer you are installing.
Mettacrawler
 
Posts: 21
Joined: Sun Mar 18, 2018 7:19 pm


Return to General

Who is online

Users browsing this forum: No registered users and 5 guests