Kernel panic

Hi,

RH4 AS after reboot, generate few error lines (attached screenshot) the first is regarding the RAID controller I think, (it is on HP DL 360G4) and it finish with:
"Kernel panic - not syncing: Attempted to kill init!"

After that the system is not booting... any idea how to fix it? screenshot
questilAsked:
Who is Participating?
 
questilAuthor Commented:
I booted with the installation cd in rescue mode, run chroot, moved the kernel img file to another name:
#mv HP-initrd-2.6.9-11.ELsmp.img HP-initrd-2.6.9-11.ELsmp.img.old

Run the mkinitrd command:
#mkinitrd HP-initrd-2.6.9-11.ELsmp.img 2.6.9-11.ELsmp

And then rebooted with the new kernel and everything is working!

Thanks everyone!
0
 
ByteSleuthCommented:
Hello,

if you start your box, do you have the possibility to enter menu from your controller?

for me it looks like your volume-groups are gone or not working.

HTH
0
 
Hatrix76Commented:
No, the problem seems to be that your initrd image is out of sync with the current kernel, the line with the insmod error at the beginning is the problem. It can not load the cciss.ko kernel module, which is responsible for the raid array. It seems at some point the kernel got upgraded, but a problem occured while the kernel tried to generate the new initrd image.

The initrd image is a small mini-image, that get's loaded at kernel boot. This image contains all modules which are needed for the kernel to prepare the installed hardware.

My suggestion would be to boot with a RedHat 4 disk, boot in emergency or rescue mode. I do not know how it's done on a Redhat CD, on debian / ubuntu installer you have always the option to boot into a rescue mode.

When booted in the rescue-mode, mount all the filesystems you had in the right place, chroot into it and try to reinstall the kernel image. Take note of any problems that might occur. e.g. It could be that, if your /boot resides on a seperate partition, that there is not enough space for the temporary new initrd image.

If the kernel installs fine and the new initrd image is generated (take a note of the datestamps of the files before / after in /boot) you will be able to successfully boot once again!

best
Ray
0
 
tuxnaniCommented:
you must reinstall kernel image using yacht.
0
 
questilAuthor Commented:
The other solutions didn't work.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.