Explaining the “No working init found.” boot hang message — The Linux Kernel documentation
The Linux Kernel 7.4.0-rc3 Quick search Contents Working with the development community Development process Submitting patches Code of conduct Maintainer handbook All development-process docs Internal API manuals Core API Driver APIs Subsystems Locking Development tools and processes Licensing rules Writing documentation Development tools Testing guide Hacking guide Tracing Fault injection Livepatching Rust User-oriented documentation Administration General guides to kernel administration Booting the kernel Tracking down and identifying problems Reporting issues Reporting regressions How to quickly build a trimmed Linux kernel How to verify bugs and bisect regressions Bug hunting Bisecting a regression Tainted kernels Ramoops oops/panic logger Dynamic debug Explaining the “No working init found.” boot hang message Documentation for Kdump - The kexec-based Crash Dumping Solution Performance monitor support pstore block oops/panic logger Clearing WARN_ONCE Reducing OS jitter due to per-cpu kthreads Softlockup detector and hardlockup detector (aka nmi_watchdog) Reliability, Availability and Serviceability (RAS) Error decoding Address translation Linux Magic System Request Key Hacks Core-kernel subsystems Block-layer and filesystem administration Device-specific guides Workload analysis Everything else Build system Reporting issues Userspace tools Userspace API Firmware-related documentation Firmware Firmware and Devicetree Architecture-specific documentation CPU architectures Other documentation Unsorted documentation Translations Translations This Page Show Source English Chinese (Simplified) Chinese (Traditional) Explaining the “No working init found.” boot hang message ¶ Authors : Andreas Mohr <andi at lisas period de> Cristian Souza <cristianmsbr at gmail period com> This document provides some high-level reasons for failure (listed roughly in order of execution) to load the init binary.
Unable to mount root FS : Set “debug” kernel parameter (in bootloader config file or CONFIG_CMDLINE) to get more detailed kernel messages. init binary doesn’t exist on rootfs : Make sure you have the correct root FS type (and root= kernel parameter points to the correct partition), required drivers such as storage hardware (such as SCSI or USB!) and filesystem (ext3, jffs2, etc.) are builtin (alternatively as modules, to be pre-loaded by an initrd).
Broken console device : Possibly a conflict in console= setup --> initial console unavailable. E.g. some serial consoles are unreliable due to serial IRQ issues (e.g. missing interrupt-based configuration). Try using a different console= device or e.g. netconsole= . Binary exists but dependencies not available : E.g. required library dependencies of the init binary such as /lib/ld-linux.so.2 missing or broken. Use readelf -d <INIT>|grep NEEDED to find out which libraries are required.
Binary cannot be loaded : Make sure the binary’s architecture matches your hardware. E.g. i386 vs. x86_64 mismatch, or trying to load x86 on ARM hardware. In case you tried loading a non-binary file here (shell script?), you should make sure that the script specifies an interpreter in its shebang header line ( #!/... ) that is fully working (including its library dependencies). And before tackling scripts, better first test a simple non-script binary such as /bin/sh and confirm its successful execution.
To find out more, add code to init/main.c to display kernel_execve() s return values. Please extend this explanation whenever you find new failure causes (after all loading the init binary is a CRITICAL and hard transition step which needs to be made as painless as possible), then submit a patch to LKML. Further TODOs: Implement the various run_init_process() invocations via a struct array which can then store the kernel_execve() result value and on failure log it all by iterating over all results (very important usability fix).
Try to make the implementation itself more helpful in general, e.g. by providing additional error messages at affected places. ©The kernel development community. | Powered by Sphinx 5.3.0 & Alabaster 0.7.16 | Page source