Kernel Panic: VFS cannot open a root device

Kernel Panic: VFS cannot open a root device

[GlupFire]

Hi , i have kernel 2.4.29 at slack 10.1 and when I upgrade my kernel to
2.6.11 I get these erros on booting

VFS: Cannot open a root device "301" or unknow block
please append a correct "root" boot option
KERNEL PANIC :  not syncing; VFS; Unable to mount root fs on unknown-block
(3,1)

I have compiled my kernel with my IDE support and also with my file system
support with built-in option.

My LILO.CONF
image = /boot/vmlinuz-2.6.11
root = /dev/hda1
label = 2.6.11
initrd = /boot/initrd.gz
read-only

I googled this problem, and I think is a kind of bug, and i tryed to patch
the kernel with Alan Cox patch 2.6.11-ac7.bzip  and I get these ::
bzip2 -dc /usr/src/patch-2.6.11.ac7.bzip | patch -p1 -s
1 out of hunk FAILED --saving rejects to file Makefike.rej

and I cat the file Makefile.rej

***************
*** 1,8 ****
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 11
- EXTRAVERSION =
- NAME=Woozy Numbat

# *DOCUMENTATION*
# To see a list of typical targets execute "make help"
--- 1,8 ---- 
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 11
+ EXTRAVERSION = ac7
+ NAME=AC

# *DOCUMENTATION*
# To see a list of typical targets execute "make help"

I'm stuck! The patch dont work fine ( I think the patch is not installed
succesfully on my kernel )
I'm booting with my image of kernel 2.4.29..... i'm 5 days tryng to solve
this problem ...
any kind of help is wellcome... sorry for my english.

Kernel Panic: VFS cannot open a root device

[GlupFire]

> Hi , i have kernel 2.4.29 at slack 10.1 and when I upgrade my kernel to
> 2.6.11 I get these erros on booting
>
> VFS: Cannot open a root device "301" or unknow block
> please append a correct "root" boot option
> KERNEL PANIC :  not syncing; VFS; Unable to mount root fs on unknown-block
> (3,1)
>
> I have compiled my kernel with my IDE support and also with my file system
> support with built-in option.
>
> My LILO.CONF
> image = /boot/vmlinuz-2.6.11
> root = /dev/hda1
> label = 2.6.11
> initrd = /boot/initrd.gz
> read-only
>
> I googled this problem, and I think is a kind of bug, and i tryed to patch
> the kernel with Alan Cox patch 2.6.11-ac7.bzip  and I get these ::
> bzip2 -dc /usr/src/patch-2.6.11.ac7.bzip | patch -p1 -s
> 1 out of hunk FAILED --saving rejects to file Makefike.rej
>
> and I cat the file Makefile.rej
>
> ***************
> *** 1,8 ****
> VERSION = 2
> PATCHLEVEL = 6
> SUBLEVEL = 11
> - EXTRAVERSION =
> - NAME=Woozy Numbat
>
> # *DOCUMENTATION*
> # To see a list of typical targets execute "make help"
> --- 1,8 ---- 
> VERSION = 2
> PATCHLEVEL = 6
> SUBLEVEL = 11
> + EXTRAVERSION = ac7
> + NAME=AC
>
> # *DOCUMENTATION*
> # To see a list of typical targets execute "make help"
>
> I'm stuck! The patch dont work fine ( I think the patch is not installed
> succesfully on my kernel )
> I'm booting with my image of kernel 2.4.29..... i'm 5 days tryng to solve
> this problem ...
> any kind of help is wellcome... sorry for my english.
>

Re: Kernel Panic: VFS cannot open a root device

[porranenhuma]

I already done that things , and I still getting these errors ... I dont
no what to do , and I'm getting desesperated...

 '>'-- Mensagem Original --
 '>'From: Norbert van Nobelen <norbert@edusupport.nl>
 '>'To: "GlupFire" <porranenhuma@globo.com>
 '>'Subject: Re: Kernel Panic: VFS cannot open a root device
 '>'Date: Sun, 17 Jul 2005 10:16:37 +0000
 '>'
 '>'
 '>'You should compile in the filesystem (reiserfs?) into the kernel (*
instead
 '>'of 
 '>'M), or put the correct module in initrd (usually done by mkinitrd).

 '>'After that run lilo, and it should boot just fine.
 '>'
 '>'Norbert
 '>'
 '>'Op zaterdag 16 juli 2005 20:57, schreef u:
 '>'> > Hi , i have kernel 2.4.29 at slack 10.1 and when I upgrade my kernel
 '>'to
 '>'> > 2.6.11 I get these erros on booting
 '>'> >
 '>'> > VFS: Cannot open a root device "301" or unknow block
 '>'> > please append a correct "root" boot option
 '>'> > KERNEL PANIC :  not syncing; VFS; Unable to mount root fs on
 '>'> > unknown-block (3,1)
 '>'> >
 '>'> > I have compiled my kernel with my IDE support and also with my file
 '>'> > system support with built-in option.
 '>'> >
 '>'> > My LILO.CONF
 '>'> > image = /boot/vmlinuz-2.6.11
 '>'> > root = /dev/hda1
 '>'> > label = 2.6.11
 '>'> > initrd = /boot/initrd.gz
 '>'> > read-only
 '>'> >
 '>'> > I googled this problem, and I think is a kind of bug, and i tryed
to
 '>'> > patch the kernel with Alan Cox patch 2.6.11-ac7.bzip  and I get
these
 '>'::
 '>'> > bzip2 -dc /usr/src/patch-2.6.11.ac7.bzip | patch -p1 -s
 '>'> > 1 out of hunk FAILED --saving rejects to file Makefike.rej
 '>'> >
 '>'> > and I cat the file Makefile.rej
 '>'> >
 '>'> > ***************
 '>'> > *** 1,8 ****
 '>'> > VERSION = 2
 '>'> > PATCHLEVEL = 6
 '>'> > SUBLEVEL = 11
 '>'> > - EXTRAVERSION =
 '>'> > - NAME=Woozy Numbat
 '>'> >
 '>'> > # *DOCUMENTATION*
 '>'> > # To see a list of typical targets execute "make help"
 '>'> > --- 1,8 ----
 '>'> > VERSION = 2
 '>'> > PATCHLEVEL = 6
 '>'> > SUBLEVEL = 11
 '>'> > + EXTRAVERSION = ac7
 '>'> > + NAME=AC
 '>'> >
 '>'> > # *DOCUMENTATION*
 '>'> > # To see a list of typical targets execute "make help"
 '>'> >
 '>'> > I'm stuck! The patch dont work fine ( I think the patch is not installed
 '>'> > succesfully on my kernel )
 '>'> > I'm booting with my image of kernel 2.4.29..... i'm 5 days tryng
to solve
 '>'> > this problem ...
 '>'> > any kind of help is wellcome... sorry for my english.
 '>'>
 '>'> -
 '>'> 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: Kernel Panic: VFS cannot open a root device

[Fawad Lateef]

On 7/18/05, porranenhuma@globo.com <porranenhuma@globo.com> wrote:
> I already done that things , and I still getting these errors ... I dont
> no what to do , and I'm getting desesperated...
> 
>  '>'
>  '>'You should compile in the filesystem (reiserfs?) into the kernel (*
> instead
>  '>'of
>  '>'M), or put the correct module in initrd (usually done by mkinitrd).
> 
>  '>'After that run lilo, and it should boot just fine.
>  '>'
>  '>'Norbert
>  '>'
>  '>'Op zaterdag 16 juli 2005 20:57, schreef u:
>  '>'> > Hi , i have kernel 2.4.29 at slack 10.1 and when I upgrade my kernel
>  '>'to
>  '>'> > 2.6.11 I get these erros on booting
>  '>'> >
>  '>'> > VFS: Cannot open a root device "301" or unknow block
>  '>'> > please append a correct "root" boot option
>  '>'> > KERNEL PANIC :  not syncing; VFS; Unable to mount root fs on
>  '>'> > unknown-block (3,1)
>  '>'> >
>  '>'> > I have compiled my kernel with my IDE support and also with my file
>  '>'> > system support with built-in option.
>  '>'> >
>  '>'> > My LILO.CONF
>  '>'> > image = /boot/vmlinuz-2.6.11
>  '>'> > root = /dev/hda1
>  '>'> > label = 2.6.11
>  '>'> > initrd = /boot/initrd.gz
>  '>'> > read-only
>  '>'> >

I saw this prob when my boot device/partition in the bootloader config
was wrong or the filesystem of my root partition is not compiled as a
kernel image rather compiled as module, so plz try to solve this prob
by selecting your desired filesystem in kernel configuration as Y
rather than M ...... I hope this will work

>  '>'> > I'm booting with my image of kernel 2.4.29..... i'm 5 days tryng
> to solve
>  '>'> > this problem ...

Upgrading from 2.4.xx kernel series to 2.6.xx series what I found is
that the filesystem must be compiled into the kernel image not as a
module b/c in 2.4.xx filesystem compiled as module also work ........

And another thing is that I never succedded in booting the 2.6.xx
kernel __successfully__ compiled from 2.4.xx series (distribution with
default 2.4.xx series kernel like Fedora Core 1 or Redhat Linux 9) and
found that my mouse won't work on 2.6.xx series kernel, but the
distribution with 2.6.xx kernel series by default works fine .....


-- 
Fawad Lateef

Re: Kernel Panic: VFS cannot open a root device

[Ed Tomlinson]

On Sunday 17 July 2005 22:46, Fawad Lateef wrote:
> I saw this prob when my boot device/partition in the bootloader config
> was wrong or the filesystem of my root partition is not compiled as a
> kernel image rather compiled as module, so plz try to solve this prob
> by selecting your desired filesystem in kernel configuration as Y
> rather than M ...... I hope this will work

One further tip.  Make your root FS's type the only one that is not a module.
Once you have it booting then, if you want, flip other FSes to in kernel.

Ed Tomlinson