Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am using Linux 2.6.32-33-server #70-Ubuntu 10.04.3 as Data-Nodes and Name-Node in my Hadoop cluster, but one of my data node is down since morning. When i restarted that particular system it showed an error "Kernel panic - not syncing - Attempted to kill init!"

I dont know how to fix it!! Is this a problem with RAM of that system!!

share|improve this question

migrated from Aug 23 '12 at 2:36

This question came from our site for professional and enthusiast programmers.

/sbin/init is always the first process launched on your system. If the binary doesn't exists, the system cannot start. I don't know what happened, but it seems it has been erased from your disk, the easiest way to repair it is to reinstall the entire system. If you did correctly install your system first, you'll just have to reinstall the root partition, and just link your others (/home, /boot, etc...).

If you don't want to do that, first check if the /sbin/init binary exists, you can do that mounting the partition from another one or a LiveCD.

share|improve this answer
it is also saying run -init:/sbin/init : no such file or directory – vikash Aug 22 '12 at 9:43
/sbin/init is the first process launched on a computer. If it doesn't exists, your system crashes. I think the simplest way for you is to reinstall it... – Bartimeus Aug 22 '12 at 11:52

In all recent systems initd is started from initrd image. If the kernel can not find it this means that initrd is missing or corrupted.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.