kernel panic - not syncing : attempted to kill init
 

Hi Guys,

I have Installed linux 5.1 and facing below error when server booting. after this error server stucked.

Memory for crash kernel (0x0 to 0x0) notwithin permissible range
i8042.c: No controller found.
Red Hat nash version 5.1.19.6 starting
Reading all physical volumes. This may take a while...
Found volume group "VolGroup00" using metadata type lvm2
2 logical volume(s) in volume group "VolGroup00" now active
EXT3-fs error (device dm-0) ext3_lookup: unlinked inode 29556737 in dir #2
EXT3-fs error (device dm-0) ext3_lookup: unlinked inode 67502081 in dir #2
EXT3-fs error (device dm-0) ext3_lookup: unlinked inode 29556737 in dir #2
EXT3-fs error (device dm-0) ext3_lookup: unlinked inode 45088769 in dir #2
EXT3-fs error (device dm-0) ext3_lookup: unlinked inode 45088769 in dir #2
worning :can't access (null)
exec of init ((null)) failes!!!! bad address
kernel panic - not syncing : attempted to kill init
kernel alive
kernel direct mapping tables up to 870000000 @ 10000-33000

Regards
Khan

Did you shutdown the machine properly? Seems like there corrupted fs on root directory.
If you have access to Live cd or recovery console - check those reported inodes. And also run fsck and see it helps or not.

Can you guide me , how I can check the mentioned inodes.

Regards,
Khan

Do you have live-cd or live-usb? If so, you can use that mount the drive and do 'ls -li'.
If the device is unmountable, you can try using 'debugfs' command from e2fsprogs.


--
Is the system crashed after installation ? Or it happened after some upgrade?

This system was in production and reported when crashed. No new installation and no upgrade made and was running fine from 2 years. CISCO application running on that server. I have physical access of this server. I have tried from grub but no luck.

Regards
Khan

Whats the distro and kernel version?

Data center have long distance from my place. I need to check and will update threat by tomorrow. Currently I have just kernel " vmlinuz-2.6.18-194.e15" and "initrd-2.6.18-194.e15.img" version info.

Regards,
Khan

We actually have a sticky on this very topic.

Superficially, this indeed appears to be some kind of mis-configuration of the volume groups. And/or you may need to boot a rescue-DVD and run fsck on volumes. Might you have a failing disk drive?