Explaining the "No working init found." boot hang message — The Linux Kernel documentation
The Linux Kernel 6.6.0 Quick search Contents A guide to the Kernel Development Process Submitting patches: the essential guide to getting your code into the kernel Code of conduct Kernel Maintainer Handbook All development-process docs Core API Documentation Driver implementer's API guide Kernel subsystem documentation Locking in the kernel Linux kernel licensing rules How to write kernel documentation Development tools for the kernel Kernel Testing Guide Kernel Hacking Guides Linux Tracing Technologies fault-injection Kernel Livepatching Rust The Linux kernel user's and administrator's guide Linux kernel release 6.x <http://kernel.org/> The kernel's command-line parameters Linux allocated devices (4.x+ version) Documentation for /proc/sys Linux ABI description Feature status on all architectures Hardware vulnerabilities Reporting issues Reporting regressions How to quickly build a trimmed Linux kernel Bug hunting Bisecting a bug 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 Rules on how to access information in sysfs Discovering Linux kernel subsystems used by a workload ACPI Support ATA over Ethernet (AoE) Auxiliary Display Support A block layer cache (bcache) The Android binderfs Filesystem Kernel Support for miscellaneous Binary Formats (binfmt_misc) Block Devices Boot Configuration Linux Braille Console btmrvl driver Control Groups version 1 Control Group v2 CIFS Clearing WARN_ONCE CPU load How CPU topology info is exported via sysfs Dell Remote BIOS Update driver (dell_rbu) Device Mapper EDID The EFI Boot Stub ext4 General Information File system Monitoring with fanotify NFS gpio Notes on the change from 16-bit UIDs to 32-bit UIDs Hardware random number generators Using the initial RAM disk (initrd) I/O statistics fields Java(tm) Binary Kernel Support for Linux v1.03 IBM's Journaled File System (JFS) for Linux Reducing OS jitter due to per-cpu kthreads Laptop Drivers Parallel port LCD/Keypad Panel support LDM - Logical Disk Manager (Dynamic Disks) Softlockup detector and hardlockup detector (aka nmi_watchdog) Linux Security Module Usage RAID arrays Media subsystem admin and user guide Memory Management Kernel module signing facility Mono(tm) Binary Kernel Support for Linux Namespaces Numa policy hit/miss statistics Parport Perf events and tool security Power Management Linux Plug and Play Documentation RapidIO Subsystem Guide Reliability, Availability and Serviceability Real Time Clock (RTC) Drivers for Linux Linux Serial Console Video Mode Selection Support 2.13 Syscall User Dispatch Linux Magic System Request Key Hacks Thermal Subsystem USB4 and Thunderbolt Using UFS Unicode support Software cursor for VGA Video Output Switcher Control The SGI XFS Filesystem The kernel build system Reporting issues User-space tools The Linux kernel user-space API guide The Linux kernel firmware guide Open Firmware and Devicetree CPU Architectures Unsorted Documentation Translations This Page Show Source 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.0.1 & Alabaster 0.7.12 | Page source