kernel panic

[talpa_sai]

Dear friends,

I have a system whose configuration is as hereunder:

AMD Sempron processor 2800+ with 1 GB of RAM and two hard disks, one of

120 GB and the other of 320GB.

The partitions are as follows:

 

Code:

Disk /dev/hda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks            Id      System
/dev/hda1               1             2432    19535008+     83      Linux
/dev/hda2            2433          4864     19535040      83      Linux
/dev/hda3   *        4865          7296     19535040        c      W95 FAT32 (LBA)
/dev/hda4            7297        14593    58613152+       5      Extended
/dev/hda5            7297          7420     995998+        82       Linux swap / Solaris
/dev/hda6            7421          9852    19535008+       b      W95 FAT32
/dev/hda7            9853        12284    19535008+       b      W95 FAT32
/dev/hda8           12285       14593    18547011      83       Linux

Disk /dev/hdc: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks            Id        System
/dev/hdc1   *           1       25496   204796588+        7        HPFS/NTFS
/dev/hdc2           25497       38913   107772052+    7        HPFS/NTFS

 

I have three operating systems in the partitions mentioned below:

 

Code:

/dev/hda1            RedHat Enterprise Linux 5
/dev/hda2            Fedora Core 7
/dev/hda3            Windoze XP

 

Today, while trying to boot into Fedora Core 7, the system could not boot and the following message was spit out.

 

Code:

mount: could not find filesystem '/dev/root'
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
kernel panic - not syncing: Attempted to kill init!

 

The kernel version of Fedora Core 7 is 2.6.21-1.3194.fc7. Is there any way to set the system right and boot into Fedora Core 7 ? The contents of the file

"/boot/grub/menu.ist" are as follows:

 

Code:

# 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/hda1
#          initrd /boot/initrd-version.img
#boot=/dev/hda
default=0
timeout=30
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
#hiddenmenu
title Red Hat Enterprise Linux Server (2.6.18-8.el5)
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-8.el5 ro root=LABEL=/1 rhgb quiet crashkernel=128M@16M
initrd /boot/initrd-2.6.18-8.el5.img
title Fedora-base (2.6.21-1.3194.fc7)
root (hd0,1)
kernel /boot/vmlinuz-2.6.21-1.3194.fc7 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.21-1.3194.fc7.img
title Win XP
rootnoverify (hd0,2)
chainloader +1

 

I also ran the command "fsck.ext3 -fv /dev/hda2 after ensuring that /dev/hda2 is unmounted and no errors/bad blocks are reported. Can anybody enlighten me as to how to go about to boot into Fedora Core 7. I further inform that I could boot into the other two OS's, i.e., RHEL-5 and Windoze XP.

[anyweb]

what happened before this problem ? did f7 work fine ? did you recently change any hardware ? did you do a kernel or other update ? please explain

[talpa_sai]

what happened before this problem ? did f7 work fine ? did you recently change any hardware ? did you do a kernel or other update ? please explain

Dear friend,

FC 7 worked fine. I did not change any hardware and did not go in for updates recently. There are some RPM's in FC 7. I booted into

RHEL 5, cded to /mnt/fedora and installed some RPM's from there instead of copying them to RHEL 5 partition, i.e. /dev/hda1 and then

installing them. I don't think this may be the cause of FC 7 boot failure.

 

Yours faithfully,

talpa_sai.