fc2 kernel panic

[Ted Kaczmarek]

On Mon, 2004-05-24 at 06:52 -0400, Thomas Molina wrote:
> > root at inyoureyes boot]# ls -latr initrd-2.*
> > -rw-rw-r--  1 root root 276009 Aug 20  2003 initrd-2.4.20-20.9.img
> > This one post yum upgrade.
> > -rw-r--r--  1 root root 195900 May 23 18:28initrd-2.6.5-1.358smp.img.old
> > This one I created "mkinitrd 2.6.5-1.358"
> > -rw-r--r--  1 root root 194628 May 23 18:34 initrd-2.6.5-1.358smp.img
> > And Arjans latest test kernel.
> > -rw-r--r--  1 root root 195429 May 23 19:13 initrd-2.6.6-1.376smp.img
> > 
> > 
> > mkrootdev: label / not found
> > mount: error 2 mounting ext3
> > pivotroot: pivot_root(/sysroot/initrd) failed: 2
> > umount /initrd/proc failed: 2
> > Freeing unused kernel memory: 188k freed
> > Kernel panic: No init found. Try passing init=option to kernel
> > 
> > default=0
> > timeout=10
> > splashimage=(hd0,0)/grub/splash.xpm.gz
> > password --md5 $1$l0WNN0$rK69CoayY343p0GqclgL/1
> > title Fedora Core (2.6.6-1.376smp)
> >         root (hd0,0)
> >         kernel /vmlinuz-2.6.6-1.376smp ro root=LABEL=/ acpi=on
> >         initrd /initrd-2.6.6-1.376smp.img
> > title Fedora Core (2.6.5-1.358smp)
> >         root (hd0,0)
> >         kernel /vmlinuz-2.6.5-1.358smp ro root=LABEL=/ acpi=on
> >         initrd /initrd-2.6.5-1.358smp.img
> 
> 
> > Any thought's?
> 
> I typically see the above panic message when I have rebuilt something and 
> end up with an initrd not containing modular ext3 and jbd.  My solution to 
> this is edit the /boot/grub/grub.conf file to replace the "root=LABEL=/" 
> part with a reference to a specific device (root=/dev/hda2 in my case).  
> This can be done either from the rescue cd or from one of the other 
> kernels, which are still bootable.  

Tried that, 
changed "ro root=LABEL=/"
to "ro root=/dev/sda7",
but if the ext3 module doesn't load, the root partion won't be either.

Ted