[afnog] kernel panic attempted to kill init
Tracy Musaza
cocko_mirindi at yahoo.fr
Thu Aug 27 12:19:15 UTC 2009
Hello Kone !!
Is one or two Kernels images in your boot loader? if so, just select the second and see if your system can boot with. in your case, I think the SOLUTION IS TO FIX the /boot/initrd.img-* file relating to the kernel image and the grub or lilo (bootloader) initrd item.
The thing is, your boot-loader may still be able to access other previously installed kernels, unless you installed and removed at the same time. in this case, your system is completely down and unusable and it is thus critical, then I'm not really sure where to put the bug fix, I guess it would be handy if the kernel post-inst checked for this.
If it already does the check or notTRY this solution :
regenerate ramdisk :
mkinitrd -o /boot/initrd.img-VERSIONNAMEHERE VERSIONNAMEHERE
don't forget you neet to inform your boot loader if there is an initrd.img change of name.Best regards,
Coko TracyKigali- Rwanda
--- En date de : Mer 26.8.09, Ernest Byaruhanga <e.byaru at gmail.com> a écrit :
De: Ernest Byaruhanga <e.byaru at gmail.com>
Objet: Re: [afnog] kernel panic attempted to kill init
À: "Kone" <enokb at yahoo.fr>
Cc: afnog at afnog.org
Date: Mercredi 26 Août 2009, 18h14
Kone wrote thus on 8/13/09 10:52 PM:
> Hello all,
> I have a server running with Debian 4.0 after the power down i restart
> it and /var was not correctly mounted so i use fsck /de/sdb1 to repair.
> After that i restart and get a following error :
> pivot_root : No such file or directory
> /sbin/init : 432 : Cannot open dev/console : no such file
> kernel panic attempted to kill init
how does your /etc/fstab look like?
eb
_______________________________________________
afnog mailing list
http://afnog.org/mailman/listinfo/afnog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://afnog.org/pipermail/afnog/attachments/20090827/cd615fbe/attachment.html>
More information about the afnog
mailing list