Solved

Kernel panic

Posted on 2010-11-15
5
893 Views
Last Modified: 2012-05-10
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
0
Comment
Question by:questil
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
5 Comments
 
LVL 5

Expert Comment

by:ByteSleuth
ID: 34134357
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
 
LVL 7

Expert Comment

by:Hatrix76
ID: 34134810
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
 
LVL 1

Expert Comment

by:tuxnani
ID: 34135318
you must reinstall kernel image using yacht.
0
 

Accepted Solution

by:
questil earned 0 total points
ID: 34154559
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
 

Author Closing Comment

by:questil
ID: 34186345
The other solutions didn't work.
0

Featured Post

Why Off-Site Backups Are The Only Way To Go

You are probably backing up your data—but how and where? Ransomware is on the rise and there are variants that specifically target backups. Read on to discover why off-site is the way to go.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

rdate is a Linux command and the network time protocol for immediate date and time setup from another machine. The clocks are synchronized by entering rdate with the -s switch (command without switch just checks the time but does not set anything). …
I. Introduction There's an interesting discussion going on now in an Experts Exchange Group — Attachments with no extension (http://www.experts-exchange.com/discussions/210281/Attachments-with-no-extension.html). This reminded me of questions tha…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question