• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6851
  • Last Modified:

Kernel panic - not syncing: Attempted to kill init!

I upgraded my Red Hat enterprise version 3.9 to version 4.3 and now I get the following error when trying to boot.

Creating root device
mkrootdev: label / not found
Mounting root filesystem
mount: error 2 mounting ext3
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!


Anyone have any ideas on how to fix this??  I tried a few diff. things but nothing is working so far.
0
bbarac
Asked:
bbarac
1 Solution
 
arrkerr1024Commented:
Sounds like either your hard drives aren't found or the label is screwed up.

What hard drive controller do you have?

If you boot from the 4.3 CD drive do you see hard drives?  If you do you could either try re-writing the label on the partition, or edit grub.conf and fstab to use the actual partition (something like /dev/sda1 instead of LABEL=/).
0
 
Kerem ERSOYPresidentCommented:
Hi,

Are you using any ATA drives? If this is the case then it is likely that your previous release was using it in PATa compatiblity mode and now th kernel thinks it is a SATA drive hence looking for /dev/sdx while th setup was for /dev/hdx.

Please reboot from a rescue disk and mount your /boot volume and edit  your grub/device list file and correct it if id displays a wrong drive there.
0
 
Kerem ERSOYPresidentCommented:
Sorry for the mistake the file is named: grub/device.map
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
remeshkCommented:
Go to rescue mode , try to mount  / partition automatically . If its not possible  , check your partition label using e2label command  . If its correct , mount / partition manually  and  boot partition is there that also . Check your grub.conf entry and /etc/fstab .
0
 
bbaracAuthor Commented:
I should mention that that this is running on ESX so this is a virtual machine.  The hard drvies are detected fine, when going into rescue mode the original installation is found and i've done an upgrade from 3.9 to 4.3 so the original install was OK.  Currently if I go into rescue mode and do a df I see the following

/dev/sda1   /
/dev/sda2    /boot
/dev/sda3     /home

if I go into fstab file I see

LABEL=/      /
LABEL=/boot    /boot
none     /dev/pts
LABEL=/home     /home
none     /proc
none    /dev/shm
/dev/sda4    swap
......


If I go into grub.conf file then I see.

title red hat.......
root (hd0,0)
kernel /vmlinuz-2... ro  root=dev/sda5
initrd /initrd-2.4.9-e.72.smp.img


I tried changing the fstab and grub file to point to sda1 and sda2 but it made no difference.
0
 
Kerem ERSOYPresidentCommented:
Hi from what you post here I see thet yout gru.bconf trying to boot /dev/sda5 which is non-existent.

Just confitm that /boot/grub/device.map points to /dev/hda
then edit your /etc/grub.conf to change your
kernel /vmlinuz-2.... root=/dev/sda5
to
kernel /vmlinuz-2.... root=/dev/sda1

save and reboot. Thats it.
0
 
elf_binCommented:
Probably due to initrd either:
1) Being corrupt
2) Missing some drivers
3) Not actually being there.

mkinitrd (redhat) will solve that problem for you :o)
0
 
bbaracAuthor Commented:
I have it fixed, had to make quite a few changes to the grub.config, it was pointing to a wrong kernel and initrd version, also had to change some sym links.  So basically the grub.config was completely wrong.  
0
 
Kerem ERSOYPresidentCommented:
Congratulations. But what do you think might caused that?
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now