Kernel panics!!!
 

alright guys, I really need some help here....

I am using RedHat 8.0 + updates to phoebe and with the updates also came a new kernel. First I updated the kernel from the up2date feature to 2.4.20-2.21 and when I rebooted I had two options. I could either boot up with the old kernel (2.4.18-14) OR the new one (2.4.20-2.21). When I tried selecting the new one I got a "kernel panic: init not found error". However, before this line was another line saying "error 19: cannot mount ext3 file-system". Anyways, I asked in the distro forum and got nowhere with it.
Today I updated the kernel again to 2.4.20-2.24 (hoping that it'd work this time) but this time I get the same kernel panic with the same "init not found" message but this time the line above that says "error 6: cannot mount ext3 file-system".
I have searched through google, redhat bugzilla etc with no luck. Does anyone know how to get this thing to work?

Thanks.

you probably use ext3 as the root partition and probably this fs type is not compiled (statically) into the kernel
show the results of mount command

here it is....

mount...
/dev/hdb2 on / type ext3 (rw)
none on /proc type proc (rw)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
/dev/hdb1 on /boot type ext3 (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
none on /dev/shm type tmpfs (rw)

Re: Kernel panics!!!
 

Like dorian said, ext3 support is definitely not complied in.

You need an initrd ( initial Ram Disk ). The last time I up2dated my kernel, it downloaded the appropriate initrd as well and configured my boot loader so it would be used by the new kernel boot option. Rescue the system using the install CD, mount and chroot your root fs and run mkinitrd --with-module=ext3 to make an initrd. Modify your boot loader to use the file.

could you please give me a step-by-step instructions?
I sort of got what you're sayin' but I don't think I can do it :(

1. Boot from install disk #1 aka 'rescue cd'
2. Type in 'linux rescue' at the boot prompt.
3. Redhat will tell you if it detected your root filseystem and mounted it. ( usually under /mnt/sysimage. if not, do it manually)
4. Logon as root.
5. chroot /mnt/sysimage /bin/bash --login
6. /sbin/mkinitrd /initrd.img --with=ext3 2.4.20-2.24
7. cp ./initrd.img /boot/initrd-2.4.20-2.24.img ( Note: if your /boot is a separate partition, mount it first before you do this.)
8. edit /etc/grub.conf in your favourite text ed. ( vim rules, if you can work it )
9. under kernel /vmlinuz-2.4.20-2.24
add
initrd /initrd-2.4.20-2.24.img
10. Save, Exit, Reboot, Pray.

hey,
thanks for the help. I followed your instructions and now I get a different error...something about "LABEL=/" error.
any ideas?
here is my lilo.conf

boot="/dev/hda"
prompt
timeout="50"
message=/boot/message
root=/dev/hdb2
linear

image=/boot/vmlinuz-2.4.20-2.24
label="2.4.20-2.24"
root=/dev/hdb2
read-only
initrd="/boot/initrd-2.4.20-2.24.img"
append="root=LABEL=/"

image=/boot/vmlinuz-2.4.18-14
label="2.4.18-14"
root=/dev/hdb2
read-only
initrd="/boot/initrd-2.4.18-14.img"

image="/boot/vmlinuz-2.4.20-2.21"
label="2.4.20-2.21"
root="/dev/hdb2"
read-only
initrd="/boot/initrd-2.4.20-2.21.img"

image=/usr/src/linux/arch/i386/boot/bzImage
label="Linux_Compiled"
root=/dev/hdb2
read-only
optional

other=/dev/hda1
label="NT"

Rescue.. mount chroot etc.

remove the append= line from under your latest kernel
Now run /sbin/lilo.
Reboot.

alright man, I'll give it a shot and be back in 5-8 minutes. Please stick around if you don't mind.
thanks a bunch.

wohoo...it worked!!!
thanks man, now I can finally sleep (I've been up from over 48 hours)
I tried deleting the line before myself, but I didn't know I had to use "/sbin/lilo" afterwards.

once again, thank you.
LQ all the way!!!

P.S: one last question...now that I have this kernel working, can I remove the rpms of the old kernels??

Good!

Yes, I'd manually remove the old kernels but whatever floats your boat.

Curious.. where are you located, deewane?

Toronto, Canada :D

Not too far, I guess.