Kernel panic - not syncing: Attempted to kill init
Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Kernel panic - not syncing: Attempted to kill init
Just restored my RHEL 5.3 LINUX system to to different hardware using MONDO. Now while I was successful in doing this on my 32bit system, my 64bit system is giving me the following errors when trying to boot from GRUB:
mount: could not find filestystem '/dev/root'.
Setting up other filesystems
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init
unmounting old /dev/
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init
Here is what I have done in an attempt to resolve:
1. reboot system off of red hat rescue cd
2. changed all my devices in the fstab to not point to LABELS but to the actual device I am trying to mount ex:.. /dev/cciss/c0d0p*
3. reconfigured kernel using mkinitrd -v -f initrd*****.img (kernel)
4. changed the mtab, grub.conf and devices file to point to the correct devices and not labels
5. reboot
And continues to give me the same kernel error. ANY HELP is greatly appreciated.
First off, if you copied entire partitions, LABELS should be just fine.
That device paths are very strange to me, never saw it. Cna you post details of your old and new hardware? As much as possible, with the special attention to MB chipset and HDD contrlorers. Also, have you used RAID on any of the systems?
Here is what the grub.conf looks like:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,0)
# kernel /boot/vmlinuz-version ro root=/dev/sda1
# initrd /boot/initrd-version.img
#boot=/dev/sda
default=0
timeout=5
#splashimage=(hd0,0)/boot/grub/splash.xpm.gz
#hiddenmenu
title Enterprise Linux Enterprise Linux Server (2.6.18-128.1.1.0.1.el5)
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-128.1.1.0.1.el5 ro root=LABEL=/
initrd /boot/initrd-2.6.18-128.1.1.0.1.el5.img
Original device.map file:
# this device map was generated by anaconda
(hd0) /dev/sda
Here are the same files on the system that I have cloned from the original to different hardware:
Partition Table of cloned system:
Disk /dev/cciss/c0d0: 146.7 GB, 146778685440 bytes
255 heads, 63 sectors/track, 17844 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 1276 10249438+ 83 Linux
/dev/cciss/c0d0p2 1277 4337 24587482+ 82 Linux swap / Solaris
/dev/cciss/c0d0p3 4338 4720 3076447+ 83 Linux
/dev/cciss/c0d0p4 4721 17844 105418530 5 Extended
/dev/cciss/c0d0p5 4721 5103 3076416 83 Linux
/dev/cciss/c0d0p6 5104 5486 3076416 83 Linux
/dev/cciss/c0d0p7 5487 10586 40965718+ 83 Linux
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,0)
# kernel /boot/vmlinuz-version ro root=/dev/sda1
# initrd /boot/initrd-version.img
#boot=/dev/sda
default=0
timeout=5
#splashimage=(hd0,0)/boot/grub/splash.xpm.gz
#hiddenmenu
title Enterprise Linux Enterprise Linux Server (2.6.18-128.1.1.0.1.el5)
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-128.1.1.0.1.el5 ro root=/dev/cciss/c0d0p1
initrd /boot/initrd-2.6.18-128.1.1.0.1.el5.img
device.map.clone
# this device map was generated by anaconda
(hd0) /dev/cciss/c0d0
I would guess that your problem is related to cciss kernel driver. It's for HP Smar-tarray controller that you obviously have on your new sever. maybe you heed to change the type of the driver in initrd image or was it somwhere it /etc/folder? I think I have done something like that when I changed my motherboard from ATI to Nvidia chipset.
You could plug in some other SAS disk and install RHEL and use that kernel and settings for your current server.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.