Here's a little more info that might inspire some ideas out there in gentoo land. Since my /boot partition was possibly in a generally unhappy state, I booted the 2006.0 livecd, did a "mkfs /dev/sda1" (my /boot partition), then put grub and kernel stuff back on /boot. I was confident this would do it, but no go. Just to be sure nothing was left out, I even went through the grub set up process again as Daniel recommended in another post in this thread. Still no change.
The boot process continues just prior to the "INIT 2.86" line when the init.d stuff is kicked off. While booted with the livecd, I checked and /sbin/init really is there (mine, not the livecd one). But when I tried to pass "init=/sbin/init" as a kernel arg in grub.conf, I got the same panic along with a message that /sbin/init couldn't be executed (or something similar - I forgot to write it down). But since I only hosed /boot and then reinstalled grub and kernel, I'm not sure why I'm not in business yet. Any ideas? "Bueller? Bueller?" Thanks, Frustrated in Pennsylvania (aka Mike) Mike Markowski wrote: > Well, when I do it, I do it right. Through a bad combination of typos > and missing an <enter> I deleted everything in /boot. :-( > > This is what I did to (try to) recover: > > # cd /boot > # mklost+found > # emerge grub > [...edited grub.conf...] > [...recompiled kernel & modules and installed...] > > I *thought* that's all I'd need, but upon boot up: > > Warning:unable to open an initial console > Kernel panic- not syncing: no init found. Try passing init= option to kernel > > I compiled the kernel myself, not with genkernel. I'm stumped at the > moment & would be glad to try any ideas anyone might have. > > Many thanks! > Mike -- gentoo-user@gentoo.org mailing list
