Booting 2.6.10-rc3

Booting 2.6.10-rc3

[Anandraj]

hi,
My linux box with 2.6.9 kernel patched with 2.6.10-rc3 patch doesnot
come up.
It shows the following while booting-

root(hd0,4)
Filesystem type is ext2fs , partition type 0x83
kernel /vmlinuz-2.6.10-rc3 ro root=LABLE=/ rhgb quiet
    [Linux-bzImage, setup=0x1400,size=0x187b53]
initrd /initrd-2.6.10-rc3.img
    [Linux-initrd @ 0x1fcb1000,0x2eb22 bytes]

Uncompressing Linux... Ok, booting kernel
audit(1102189352.204:0):initialized
Red Hat nash version 3.5.22 starting 
mount: error 6 mounting ext3
pivotroot: pivo_root(/sysroot,/sysroot/initrd) failed : 2
umount /initrd/proc failed: 2
Kenel panic - not syncing: No init found. Try Passing init=option to
kernel.


I am using Fedora 2 distro!
The default kernel 2.6.5-1.358 that comes along with the distro works !

I had looked into various forums for "mount: error 6 mounting ext3",
none of the aswers given by them worked,
the answers like , making your ext3 module inbuilt ,also does not work !

Mine is a simple desktop PC with Pentium 4 512MB RAM, it does not deal
with any SCSI stuff!
Can somebody help me on this !! ??

TIA,
Anand

Re: Booting 2.6.10-rc3

[Jon Masters]

Anandraj wrote:

> Red Hat nash version 3.5.22 starting 
> mount: error 6 mounting ext3
> pivotroot: pivo_root(/sysroot,/sysroot/initrd) failed : 2
> umount /initrd/proc failed: 2
> Kenel panic - not syncing: No init found. Try Passing init=option to
> kernel.

> Can somebody help me on this !! ??

You need to read the build instructions for a Fedora Core distribution. 
Briefly however, modern distros rely upon an initial RAMdisk which sets 
up various hardware drivers before changing the root filesystem with the 
pivot_root utility and booting the main system proper.

There's probably a missing mkinitrd et al. in there.

Cheers,

Jon.

Re: Booting 2.6.10-rc3

[Jim Nelson]

Anandraj wrote:
> hi,
> My linux box with 2.6.9 kernel patched with 2.6.10-rc3 patch doesnot
> come up.
> It shows the following while booting-
> 
> root(hd0,4)
> Filesystem type is ext2fs , partition type 0x83
> kernel /vmlinuz-2.6.10-rc3 ro root=LABLE=/ rhgb quiet

try root=LABEL=/.

If that does not work, try passing the root fs as something like:

root=/dev/hda3

or wherever your root filesystem is.

>     [Linux-bzImage, setup=0x1400,size=0x187b53]
> initrd /initrd-2.6.10-rc3.img
>     [Linux-initrd @ 0x1fcb1000,0x2eb22 bytes]
> 
> Uncompressing Linux... Ok, booting kernel
> audit(1102189352.204:0):initialized
> Red Hat nash version 3.5.22 starting 
> mount: error 6 mounting ext3
> pivotroot: pivo_root(/sysroot,/sysroot/initrd) failed : 2
> umount /initrd/proc failed: 2
> Kenel panic - not syncing: No init found. Try Passing init=option to
> kernel.
> 
> 
> I am using Fedora 2 distro!
> The default kernel 2.6.5-1.358 that comes along with the distro works !
> 
> I had looked into various forums for "mount: error 6 mounting ext3",
> none of the aswers given by them worked,
> the answers like , making your ext3 module inbuilt ,also does not work !
> 
> Mine is a simple desktop PC with Pentium 4 512MB RAM, it does not deal
> with any SCSI stuff!
> Can somebody help me on this !! ??
> 

If you did not build an initrd, you do not need reference to an initrd in the 
grub.conf file.

> TIA,
> Anand
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

Re: Booting 2.6.10-rc3

[Anandraj]

hi , 

Now it works after makingsome changes in the grub.conf

all i did was, in the grub.conf changed the 

kernel /vmlinuz-2.6.10-rc3 ro root=LABLE=/ rhgb quiet

to 

kernel /vmlinuz-2.6.10-rc3

but, i have no idea , this works!
can anybody shed some light on this ?

TIA,
Anand



On Sun, 05 Dec 2004 15:06:53 -0500, "Jim Nelson" <james4765@verizon.net>
said:
> Anandraj wrote:
> > hi,
> > My linux box with 2.6.9 kernel patched with 2.6.10-rc3 patch doesnot
> > come up.
> > It shows the following while booting-
> > 
> > root(hd0,4)
> > Filesystem type is ext2fs , partition type 0x83
> > kernel /vmlinuz-2.6.10-rc3 ro root=LABLE=/ rhgb quiet
> 
> try root=LABEL=/.
> 
> If that does not work, try passing the root fs as something like:
> 
> root=/dev/hda3
> 
> or wherever your root filesystem is.
> 
> >     [Linux-bzImage, setup=0x1400,size=0x187b53]
> > initrd /initrd-2.6.10-rc3.img
> >     [Linux-initrd @ 0x1fcb1000,0x2eb22 bytes]
> > 
> > Uncompressing Linux... Ok, booting kernel
> > audit(1102189352.204:0):initialized
> > Red Hat nash version 3.5.22 starting 
> > mount: error 6 mounting ext3
> > pivotroot: pivo_root(/sysroot,/sysroot/initrd) failed : 2
> > umount /initrd/proc failed: 2
> > Kenel panic - not syncing: No init found. Try Passing init=option to
> > kernel.
> > 
> > 
> > I am using Fedora 2 distro!
> > The default kernel 2.6.5-1.358 that comes along with the distro works !
> > 
> > I had looked into various forums for "mount: error 6 mounting ext3",
> > none of the aswers given by them worked,
> > the answers like , making your ext3 module inbuilt ,also does not work !
> > 
> > Mine is a simple desktop PC with Pentium 4 512MB RAM, it does not deal
> > with any SCSI stuff!
> > Can somebody help me on this !! ??
> > 
> 
> If you did not build an initrd, you do not need reference to an initrd in
> the 
> grub.conf file.
> 
> > TIA,
> > Anand
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> > 
> 

Re: Booting 2.6.10-rc3

[Jon Masters]

Anandraj wrote:

> Now it works after makingsome changes in the grub.conf
> 
> all i did was, in the grub.conf changed the 
> 
> kernel /vmlinuz-2.6.10-rc3 ro root=LABLE=/ rhgb quiet
> 
> to 
> 
> kernel /vmlinuz-2.6.10-rc3
> 
> but, i have no idea , this works!
> can anybody shed some light on this ?

There's a repeated typo in your root=LABLE=/ entry, since it should be 
LABEL instead of LABLE.

That entry tells the kernel to look for a filesystem which contains a 
label in its superblock that matches the one you gave via grub.

Cheers,

Jon.