That will most probably fix the issue. I am trying to
understand why am I getting this error in the first
place.
I mean, when running 2.6.9, all the "label" stuff must
be correct, as 2.6.9 boots and runs fine. All I did
is replace 2.6.9 kernel with 2.6.10, same fstab file,
same hda parition, same partition label. Why the
error?
-A.
--- Vaughn Clinton <vclinton@xxxxxxx> wrote:
>
> A quick fix is to change the grub.conf file to point
> to the root device - "kernel
> /boot/vmlinuz-2.6.9-55.ELsmp ro root=/dev/hda2" for
> the kernel.
>
> That's assuming that the root device is configured
> on "hda2". Boot it again with the kernel that's
> bootable and using "df" check to see which device
> root ("/") is on and change the above line to point
> to that device.
>
> Cheers,
>
> > Date: Tue, 4 Mar 2008 14:16:18 -0800> From:
> ahmedcali@xxxxxxxxx> Subject: Bootup error:
> mkrootdev: label \1 not found > To:
> kernelnewbies@xxxxxxxxxxxx> > Hello,> > I am running
> Redhat 4 distro, kernel 2.6.9. I> downloaded 2.6.10,
> build the image, created an initrd> image, and
> updated the grub.conf file. > > The entries my
> grub.conf looks as follows:> > default=1> timeout=5>
> splashimage=(hd0,2)/boot/grub/splash.xpm.gz>
> hiddenmenu> title Red Hat Enterprise Linux AS 4
> Update 5> (2.6.9-55.ELsmp)> root (hd0,2)> kernel
> /boot/vmlinuz-2.6.9-55.ELsmp ro root=LABEL=/1>
> console=ttyS0,9660 rhgb quiet> initrd
> /boot/initrd-2.6.9-55.ELsmp.img> title Linux 2.6.10>
> root (hd0,2)> kernel /boot/vmlinuz-2.6.10 ro
> root=LABEL=/1> console=ttyS0,9660 rhgb quiet> initrd
> /boot/initrd-2.6.10.img> > When I boot into 2.6.10,
> I get the error "mkrootdev:> label \1 not found"
> right at the begining, followed by> a kernel panic.
> Screen output as follows:> > Red Hat nash version
> 4.2.1.10 starting> ^[[C^[[Dmkrootdev: labelKernel
> panic - not syncing:> Attempted to kill init!> /1
> not found> > > My 2.6.9 was booting fine, so the all
> the "label"> stuff should be fine. I checked with
> "e2label", the> root partition has the right label.
> What could be the> issue. Is the right driver not
> getting included in the> initrd image? Any help is
> very appreciated.> > Thank you,> A.> > >
>
____________________________________________________________________________________>
> Never miss a thing. Make Yahoo your home page. >
> http://www.yahoo.com/r/hs> > --> To unsubscribe from
> this list: send an email with> "unsubscribe
> kernelnewbies" to ecartis@xxxxxxxxxxxx> Please read
> the FAQ at http://kernelnewbies.org/FAQ>
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
