Kernel Panic with Latest AS v.4 update

[Jeff Murphy]

the system is configured correctly. it isn't a grub issue or an fstab issue. 
if i boot the default kernel, 2.6.9-5.EL, everything's OK. if i boot
the custom kernel, 2.6.9-prep, it fails with the 'mkrootdev' error.
here's what i did:

installed RHAS3 previously
upgraded to RHAS4 via the CD anaconda process
booted RHAS4, observed everything was OK
installed pending patches via up2date. rebooted again.
everything still OK.

i then entered the following commands:


cd /usr/src/redhat/SOURCES
up2date --nox --get-source kernel
rpm -iv /var/spool/up2date/kernel-2.6.9-5.0.3.EL.src.rpm
rpmbuild -bp --target=i686 ../SPECS/kernel-2.6.spec
  (all patches applied successfully, no errors reported)
cd ../BUILD/kernel-2.6.9/linux-2.6.9
cp configs/kernel-2.6.9-i686.config .config
make oldconfig
make bzImage
make modules
make modules_install
make install
reboot

selected "2.6.9-prep" from the grub menu, observed that the kernel
panics. power cycled (btw, is it possible to reboot the machine
without power cycling it when the kernel panics before starting init?)
and selected the pre-built kernel. observed that it booted fine.

no adjustments were made to the kernel source, i don't know why it
fails to boot.





On Fri, 4 Mar 2005 11:15:51 +0530, Nick <linuxwatch at gmail.com> wrote:
> Hi Jeff,
> 
> check out your /etc/fstab ur entries must look like this :
> 
> LABEL=/     /      ext3    defaults    1   1
> 
> and u can reinstall ur grub by using
> 
> #grub-install   /dev/sda
> 
> 
> On Thu, 3 Mar 2005 11:23:58 -0500, Jeff Murphy <jeff.murphy at gmail.com> wrote:
> > i'm having a similar problem.
> >
> > i've just installed RHAS4 and then installed the kernel source per the
> > instructions in the release notes for RH4.
> >
> > i copied the i686.config (non-SMP), changed EXTRAVERSION in the
> > Makefile, did the build, installed it and the modules. and the kernel
> > panics with the "mkrootdev: label / not found" message on boot.
> > e2label confirms the label is there. the original kernel boots just
> > fine. the grub.conf entries are virtually identical (see below). i
> > also tried the i686-smp.config with similar results.
> >
> > default=1
> > timeout=10
> > splashimage=(hd0,0)/grub/splash.xpm.gz
> > title Red Hat Enterprise Linux AS (2.6.9-netpass)
> >        root (hd0,0)
> >        kernel /vmlinuz-2.6.9-netpass ro root=LABEL=/
> >        initrd /initrd-2.6.9-netpass.img
> > title Red Hat Enterprise Linux AS (2.6.9-5.EL)
> >        root (hd0,0)
> >        kernel /vmlinuz-2.6.9-5.EL ro root=LABEL=/
> >        initrd /initrd-2.6.9-5.EL.img
> >
> > [root at npw2-d l2]# e2label /dev/sda1
> > /boot
> > [root at npw2-d l2]# e2label /dev/sda2
> > /
> >
> > On Mon, Feb 21, 2005 at 11:20:21AM -0500, Smith, Albert wrote:
> > > > -----Original Message-----
> > > > From: redhat-list-bounces at redhat.com
> > > > [mailto:redhat-list-bounces at redhat.com] On Behalf Of Dean Landry
> > > > Sent: Monday, February 21, 2005 10:38 AM
> > > > To: redhat-list at redhat.com
> > > > Subject: Kernel Panic with Latest AS v.4 update
> > > >
> > > > The RHN just released an update to my kernel
> > > > (2.6.9-5.03.ELsmp).  I installed it using up2date and then
> > > > restarted the machine.  I got a Kernel Panic when I restarted
> > > > so I've rebooted into the old kernel (2.6.9-5.ELsmp).
> > > >
> > > > The lines leading up to the error were:
> > > >
> > > > Red Hat mash version 4.1.18 starting
> > > > Mounted /proc filessystem
> > > > Mounting sysfs
> > > > Creating /dev
> > > > starting udev
> > > > Loading jbd.ko module
> > > > Loading ext3.ko module
> > > > Creating root device
> > > > mkrootdev: label / not found
> >
> > This means that the volume isn't labeled or doesn't match what's in
> > grub.conf.
> >
> > > > 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!
> > > >
> > > > How do I start to troubleshoot this?
> > > >
> > >
> > > When you put the new kernel in did you create a new ramdisk?
> >
> > That's done automatically by the post-install scripts for the kernel.
> > You can see this with:
> > $ rpm -q kernel --scripts
> >
> > As for the original poster, let's have a look at /etc/grub.conf.  Please
> > don't tell us you're still running lilo.
> >
> > --
> > redhat-list mailing list
> > unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> > https://www.redhat.com/mailman/listinfo/redhat-list
> >
> 
> --
> Nick
>