New install worked great, then dies with kernel panic

thender · Tux's lil' helper Joined: 26 Aug 2013 Posts: 125

Starting init: /bin/sh exists but couldn't execute it (error-8)
Kernel panic - not syncing: No working init found. Try passing init= option to kernel.

In my grub config, I have root=/dev/sda2 init=/usr/lib/systemd/systemd

I am confused. I chrooted in and re-emerged glibc and systemd as was suggested in another thread, but this hasn't solved the problem. I also tried compiling a new kernel but this did not solve the problem.

Selenia · n00b Joined: 12 Nov 2014 Posts: 42

I am just getting a running system myself. This helped me http://wiki.gentoo.org/wiki/Systemd Try making the symlinks and other steps. Then chroot in and regenerate initrd. I would think it would work then.

The_Great_Sephiroth · Posted: Thu Nov 13, 2014 3:09 am Post subject:

You don't need systemd to boot and it should not be the cause or solution to your problem. I am actually here with Gentoo now because systemd is being forced upon many other distros and it is a very bad thing, but I digress.

I am a seasoned Debian user (since 1999) but have only recently moved to Gentoo. I am by no means a Gentoo professional. However, what that error tells me is that the shell executable exsists, but it is not marked as executable. In other words, it may be 644 instead of 755. What filesystem is it installed on? Do you have a separate /usr or /var? Do you have a initramfs? I am sure the pros will be along to help soon, but those would be good pieces of information to start with.

dataking · Apprentice Joined: 20 Apr 2005 Posts: 251

thender · Tux's lil' helper Joined: 26 Aug 2013 Posts: 125

No initramfs, I don't recall setting one up. No separate /var or /usr partition either, all basic vanilla.

I did double check the symlinks, I can chroot in but not really sure what to do from there, I've never had this issue before on any other machine.

thender · Tux's lil' helper Joined: 26 Aug 2013 Posts: 125

Proof that you can use gentoo for twelve years and still be a complete idiot

I didn't have 64 bit checked in the newer kernel. I recompiled it to try and fix a sound issue.

What's interesting is with a Haswell 6 core i7 processor, is that it doesn't check the 64 bit kernel box by default.

Ah well. I'm still an idiot. SOLVED!