Linux error no init found

«Kernel panic — not syncing: No init found. Try passing init = option to kernel» after installing Ubuntu with UEFI

I decided to install Ubuntu 12.04 LTS second system with windows 7, UEFI. Made a LiveUSB, downloaded, started the installation. The installer showed four sections, one for efi already existed (windows loader seems named, 100 MB), the other three, ntfs. One of them I erased (of course, partition with windows I saved), and created two partitions — swap and / . The installation was successful, no errors. But after the reboot comes to grub, the choice of Windows 7 again returns to the grub, when choosing Ubuntu — gives black screen with error:

[1.310472] Kernel panic — not syncing: No init found. Try passing init = option to kernel. See Linux Documentation / init.txt for guidance.

6 Answers 6

Please fix the bootsector of your sda1 partition this way: https://help.ubuntu.com/community/BootSectorFix

This should fix your Windows error.

I had the same problem when I installed Ubuntu 13.10 alongside Windows 8. It turned out that the problem was UNetbootin (the LiveUSB image), which I had created on Fedora. Once I created a LiveUSB from Windows using http://www.pendrivelinux.com/ and reinstalled Ubuntu, everything worked fine.

In my case, the solution to this error turned out to be disabling Secure Boot in the BIOS. Initially, I was not able to boot from my hard drive or from a Live DVD. However, I could boot from a live USB. Different distros behaved a little differently, but none would fully boot and no solutions others had posted worked for me. This was a Lenovo x201 laptop, after replacing Windows 7 with Ubuntu.

Your Windows boot error sounds like you ran Boot Repair on the computer some time ago, then subsequently re-installed GRUB. Up to a couple of months ago, Boot Repair was aggressive in renaming Microsoft’s boot loader ( bootmgfw.efi ) and replacing it with another copy of GRUB, which would create the problem you describe. If I’m right, re-running Boot Repair and using the Advanced option to restore backed-up files may fix that part of the problem. You’ll need to boot from an emergency/live CD to do this, of course.

Your Linux problem is more obscure. It may indicate a problem in the initial RAM disk (initrd) or on your installed system. Either is a very strange error, since this is very basic stuff that should not be causing problems. A problem here is most likely a symptom of some other problem, like a disk that’s full or otherwise failing. Perhaps more clues would be present in the Boot Repair logs; when you run that program, it spits back a URL with logs. Post that URL here for us to see.

I can still add (may be it is important for finding solution), that before installing ubuntu, I used your program FixParts, because installer didn’t see windows partitions.

LovinBuntu’s suggestion for fixing your Windows partition ( /dev/sda1 ) sounds promising to me. I’m still not sure exactly what’s causing the Linux problem. Since you’ve just installed, the cowardly suggestion to re-install from scratch may be the easiest solution — but do not install GRUB in /dev/sda1 ! GRUB needs to go in the MBR ( /dev/sda ), or occasionally in a Linux partition.

If I understand correctly from logs paste.ubuntu.com/6272840, now I have two grubs, on /dev/sda1/ and /dev/sda/ ? That is, boot-repair installed grub on /dev/sda/ but didn’t delete from /dev/sda1/ ? P.s. windows now ships normal

Источник

Explaining the «No working init found.» boot hang message¶

This document provides some high-level reasons for failure (listed roughly in order of execution) to load the init binary.

1. Unable to mount root FS: Set «debug» kernel parameter (in bootloader config file or CONFIG_CMDLINE) to get more detailed kernel messages.
2. 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).
3. 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= .
4. 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 |grep NEEDED to find out which libraries are required.
5. 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.

Источник

13.04: Kernel panic — not syncing: No init found

I am quite new to Ubuntu, what next steps can I take? How can I pass init= option to the kernel?

Thank you very much in advance!

This error means you loaded the kernel without an initramfs. If this happened after a clean install ( repeat it to make sure ), then you have found a bug and need to file a bug report against the grub2 package.

5 Answers 5

I tried a lot of things, it apparently was no mistake during the installation, since I tried it many times. I think it is a hardware/driver issue in 13.04.

I finally solved the issue by installing Ubuntu 12.04 LTS, which worked immediately. Maybe this is helpful for somebody facing the same problem.

I have the same error on Lenovo Ideapad Yoga 2 Pro with Kubuntu 13.10 64 Bit. No problems with Kubuntu 13.10 32 Bit though

Kernel panic can mean many things. My guess is you made some mistake during installation, related to formatting the drive.

Here is a guide on Kernel boot parameters and how to enter them dynamically when booting via grub.

Thank you for your answer. What kind of formatting mistake could I have made? In the meantime I found an error message when starting in recovery mode, right after the no init found error: ————— WARNING: at /build/buildd/linx-3.8.0/arch/x86/kernel/smp.c:123 native_smp_send_reschedule+0x4b/0x50() Hardware name: Aspire E1-571G Modules linked in: Pid: 1, comm: swapper/0 Not tainted 3.8.0-generic #29-Ubuntu Call Trace: (list with call trace, tell me if you need it) ———— Does this help in finding a solution?

I had same problem with kubuntu 14.04 install. I tried a number of times and got kernel panic — no init each time. The problem (I think) was some left over files (from previous crunchbang install) on the bootable USB created with unetbootin. After reformatting the USB stick and redoing unetbootin iso > USB, everything went OK on next install.

I had the same problem. Thanks to @Lawrie’s answer I figured out why this happened:

While making the bootable USB, I had not previously formatted the USB and Unetbootin mixed somehow the files, allowing me to boot as a live USB and even go through the whole installation process without any error message (that’s why I did not think about it), but not properly installing it at the end.

Just make sure to format the USB prior to using Unetbootin or use another software (maybe that is the problem). That worked for me. Also try another .iso or another distribution and see if you get the same problem.

Источник

Fix the error “No init found Try passing init bootarg”

If a system with Ubuntu Linux does not shut down correctly, but suddenly fails due to a power failure without UPS backup, it can at the next start attempt for error message No init found. Try passing init = bootarg. come. The computer will not start in this case. With a file system check you can usually fix this problem.

problem

When starting the computer, the following error message appears (in the example with Ubuntu 10.10):

[1.917875] BUG: unable to handle kernel paging request at 02342000 [. ] [1.921820] --- [end trace 68f29c77e5e41c76] --- Killed mount: mounting / dev on / rott / dev failed: No such file or directory mount: mounting / sys on / rott / sys failed: No such file or directory mount: mounting / proc on / rott / proc failed: No such file or directory Target filesystem does not have requested / sbin / init. No init found. Try passing init = bootarg. BusyBox v1.15.3 (Ubuntu 1: 1.15.3-1ubuntu5) built-in shell (ash) Enter 'help' for a list of built-in commands. (Initramfs)

solution

A file system check often fixes the problem.

1. Start from a Linux Live Boot CD or from the TK USB Stick .
2. Perform a file system check of the boot partition (in this case / dev / sda1):

knoppix @ Microknoppix: ~ $ su - root @ Microknoppix: ~ # fdisk -l / dev / sda Disk / dev / sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors / track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical / physical): 512 bytes / 512 bytes I / O size (minimum / optimal): 512 bytes / 512 bytes Disk identifier: 0x000d8343 Device Boot Start End Blocks Id System / dev / sda1 * 1 2432 19530752 83 Linux / dev / sda2 2432 112100 880905217 5 Extended / dev / sda5 2432 2681 1998848 82 Linux swap / Solaris / dev / sda6 2681 112100 878905344 83 Linux root @ Microknoppix: ~ # fsck / dev / sda1 fsck from util-linux-ng 2.17.2 e2fsck 1.41.12 (17-May-2010) / dev / sda1: recovering journal Clearing orphaned inode 264826 (uid = 0, gid = 0, mode = 0100600, size = 72) / dev / sda1: clean, 261098/1222992 files, 1293526/4882432 blocks (check in 2 mounts) root @ Microknoppix: ~ #

The system can usually be restarted now.

Share this:

Источник