suddenly while booting my centos system it shows that kernel panic not syncing attempting to kill init.. i have lot of data in it please help me to recover it

hi,


once i have faced this kind of issue in my cent os too, if any of your ram is not proper or failed in that case you can face this kind of error too.

once check/change your RAM and try.

Have you performed an update before the problems started? If not, you can try to test the memory. In the meantime, download a LiveCD. For example from http://mirrors.usc.edu/pub/linux/dis...3/isos/x86_64/
It should give you access to your files so you can copy them.

Just to be safe, I suggest booting to a Live CD of something and copying your crucial data to external media or a network share before continuing your troubleshooting.

yes i updated recently.

try booting into an older kernel, the update you did might not have all the drivers, so its throwing a panic.

Can you please share with us complete panic logs..What version you are trying to update..may be we get some clue...

Red hat linux starts
JBD: failed to read block at offset 200
JBD:recovery failed
EXT3-fs error loading journal
mount:error mounting/dev/root
setuproot:mount/dev failed:no such file/directory
setuproot:error mounting/sys:no such file or directory
switchroot:mount failed:no such file or directory
kernel panic-not syncing:attempting to kill init


hangs on there..............

After update it worked fine up to one week..then suddenly

I used a ubuntu bootable flash drive but I could not able to mount the hard disk drive......

download live cd of cent os from http://mirrors.usc.edu/pub/linux/dis...3/isos/x86_64/ and try

Here is what happened and here is what that message means:

• A "kernel panic" is any condition from which the system cannot continue; it must stop immediately.
• The message "not syncing" is actually unrelated to what precedes it: it means that the system was not in the middle of doing a disk-write at the time that the failure occurred. (Which is a Good Thing.)
• The specific message, "attempted to kill 'init'," is a bit of a misnomer. What it actually means is that the init process died, or couldn't be started.

The init process (pid #1) is special: it is hand-made by the kernel during initialization, it must start successfully, and it must never, ever die. It's a privileged, user-land process that carries out very important duties without which system operation cannot continue.

Usually, when you see this message, it's at startup, and other messages immediately precede it to show you why the process couldn't start.

The best solution usually is to boot a kernel DVD, use it to check the filesystems (if the vendor-provided scripts don't do this automagically), then use it to repeat the Linux install procedure. You only need to install the core system files: you should not, for example, reinitialize the disks. This is probably the most reasonable and easy-to-do process that is likely to succeed.

For the more adventurous, It can also be useful to boot up the DVD, enter the command line, cd to the directory where this program is located, and type, init. (It is an ordinary program...) If an error-message pops up to the effect that the program doesn't start running, there probably is your answer.

If the drive won't mount, perhaps an fsck is called for.

Please suggest any free linux data recovery software for recovering kernel paniced un bootable hard disk drive.............

what Operating system ?
there is a bad kernel update on ScientificLinux 6.3
( so RHEL6.3 and CentOS 6.3 will also be affected )
that causes the "menu.lis" to not be correctly updated
the "root uuid line is BLANK

boot into the old kernel ( the 3 sec. countdown )
and look at your /boot/grub/menu.lis file

and compaire the NEW boot line to the OLD boot line