I was trying to update libc in our Ubuntu server but it failed and now when I reboot the server I get a error message:
Kernel panic - not syncing - Attempted to kill init!
and it just hangs.
What is the solution to this problem? The server is used by 10 people so I don't want to reinstall erasing their data.
The first thing to do after seeing a kernel panic error is not to panic ,because now you are aware of the image file related to the error. Step 1: Boot the system normally with your given kernel version. This is your kernel panic situation. Step 2: Reboot your machine again and select the rescue prompt.
Choose Advance option For Ubuntu. A selection menu should appear with list of kernels installed on the system, take note of the version number of the latest kernel ( Usually the First one) choose the recovery option of the old kernel (one with lower version number of the first one, normally the fourth 4th option).
If your Mac restarts unexpectedly, an error known as a kernel panic occurred, and a message indicates that your computer restarted because of a problem. The most likely cause is faulty software. A kernel panic can also be caused by damaged or incompatible hardware, including external devices attached to your Mac.
if the full message is:
kernel panic - not syncing: Attempted to kill inint ! PId: 1, comm: init not tainted 2.6.32.-279-5.2.e16.x86_64 #1
then you should have disabled selinux and after that you have rebooted the system.
The easier way is to use a live OS and re-enable it
vim /etc/selinux/config ... SELINUX=enforcing ...
Second choice is to disable selinux in the kernel arguments by adding selinux=0
vim /boot/grub/grub.conf ... kernel /boot/vmlinuz-2.4.20-selinux-2003040709 ro root=/dev/hda1 nousb selinux=0 ...
source kernel panic - not syncing: Attempted to kill inint !
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With