RE: Cannot boot after new Kernel Build

RE: Cannot boot after new Kernel Build

[Zhu, Yi]

Make sure what's your root device with `rdev'.

> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org 
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Alex
> Sent: Sunday, January 11, 2004 12:20 AM
> To: Christian Kivalo
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: Cannot boot after new Kernel Build
> 
> 
> Hi,
> yes I already tried /dev/hda3 but still get the same errors 
> when booting.
> 
> Alex
> 
> Christian Kivalo wrote:
> 
> >>Hi,
> >>I tried changing the fstab, removing the LABLE from the grub.conf, 
> >>removing initrd from it and also tried to boot with /dev/hda3.  
> >>Nothing works, still the same problem.
> >>    
> >>
> >
> >hi!
> >
> >you don't have to change your fstab, there should everything ok with 
> >you fstab.
> >
> >you should change the root= entry in your grub configuration to your 
> >actual root partition. if you don't know what partition your root is 
> >on, do a 'df' and look where '/' is mounted on.
> >
> >the second line of df output should read somewhat similar to:
> >/dev/sda2              4806936   1611232   2951516  36% /
> >
> >that's my fileserver where /dev/sda2 is mounted as '/'.
> >
> >your root= in grub config should read somewhat like this:
> >root=/dev/hda1)
> >
> >hth
> >christian
> >
> >  
> >
> >>Alex
> >>
> >>    
> >>
> >
> >-
> >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/
> >
> >
> >  
> >
> 
> 
> -
> 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: Cannot boot after new Kernel Build

[Joseph Fannin]

[-- Attachment #1: Type: text/plain, Size: 2216 bytes --]

On Sat, Jan 10, 2004 at 05:21:32PM +0900, Alex wrote:
> Hi,
> I am trying to build a new kernel but what ever version 2.4.24, 2.6.0,
> 2.6.1 i am trying to build I come across the same problem.
> 
> when doing a "make install" i get the following error.
> 
> /dev/mapper/control: open failed: No such file or directlry
> Is device-mapper driver missing from kernel?
> Comman failed.
> 
> I have installed the lates packages
> device mapper 1.00.07
> initscripts 7.28.1
> modutils, lvm2.2.00.08
> mkinitrd-3.5.15.1-2
> 
> If I just ignore the message and try to boot the machine with the new
> kernel then I get a Kernel Panic.
> 
> VFS: Cannot open root device "LABEL=/" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unapble to mount root fs on unknown-block(0,0).
> 
> The boot command in grub is
> root (hd0,0)
> kernel /vmlinuz-2.6.1 ro root=LABEL=/ hdc=ide-scsi
> initrd /initrd-2.6.1.img
> 
> It is basically the same (except the version) as I use for 2.4.20-28 so
> I assume the label is correct.

    I went through something similar with Fedora Core 1 recently.  I
have never used initrds before.

    First, be sure that the initrd is in fact getting built; my
experience has been that that device-mapper error is non-fatal, but
there may be other problems.  The command that is generating the
error is mkinitrd; if you need to, run the command manually and read
the mkinitrd man page (the --omit-lvm-modules will make the d-m error
go away, assuming you aren't using LVM, but again, it's not a big deal). 

    You probably don't need to do that though.  More likely, the
problem is the lack of *both* initrd and ramdisk support in your
kernel new kernel config.  Yes, you need to explicitly select ramdisk
support -- I don't know why initrd can be selected without ramdisk on,
but I've been assuming there is a good reason.

    After that, I had a problem with the ramdisk being too big, so
you may want to increase the default ramdisk size to 8192 before
rebuilding your kernel, or otherwise change your kernel command line
to include ramdisk_size=8192.

    HTH.

-- 
Joseph Fannin
jhf@rivenstone.net

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Cannot boot after new Kernel Build

[Alex]

Hi,
yes I already tried /dev/hda3 but still get the same errors when booting.

Alex

Christian Kivalo wrote:

>>Hi,
>>I tried changing the fstab, removing the LABLE from the grub.conf,
>>removing initrd from it and also tried to boot with
>>/dev/hda3.  Nothing
>>works, still the same problem.
>>    
>>
>
>hi!
>
>you don't have to change your fstab, there should everything ok with you
>fstab.
>
>you should change the root= entry in your grub configuration to your
>actual root partition. if you don't know what partition your root is on,
>do a 'df' and look where '/' is mounted on.
>
>the second line of df output should read somewhat similar to:
>/dev/sda2              4806936   1611232   2951516  36% /
>
>that's my fileserver where /dev/sda2 is mounted as '/'.
>
>your root= in grub config should read somewhat like this:
>root=/dev/hda1)
>
>hth
>christian
>
>  
>
>>Alex
>>
>>    
>>
>
>-
>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: Cannot boot after new Kernel Build

[Christian Kivalo]

> Hi,
> I tried changing the fstab, removing the LABLE from the grub.conf,
> removing initrd from it and also tried to boot with
> /dev/hda3.  Nothing
> works, still the same problem.

hi!

you don't have to change your fstab, there should everything ok with you
fstab.

you should change the root= entry in your grub configuration to your
actual root partition. if you don't know what partition your root is on,
do a 'df' and look where '/' is mounted on.

the second line of df output should read somewhat similar to:
/dev/sda2              4806936   1611232   2951516  36% /

that's my fileserver where /dev/sda2 is mounted as '/'.

your root= in grub config should read somewhat like this:
root=/dev/hda1)

hth
christian

>
> Alex
>

Re: Cannot boot after new Kernel Build

[Alex]

Hi,
I tried changing the fstab, removing the LABLE from the grub.conf, 
removing initrd from it and also tried to boot with /dev/hda3.  Nothing 
works, still the same problem.

Alex

Christian Kivalo wrote:

>>Hi,
>>I am trying to build a new kernel but what ever version 2.4.24, 2.6.0,
>>2.6.1 i am trying to build I come across the same problem.
>>
>>when doing a "make install" i get the following error.
>>
>>/dev/mapper/control: open failed: No such file or directlry
>>Is device-mapper driver missing from kernel?
>>Comman failed.
>>
>>I have installed the lates packages
>>device mapper 1.00.07
>>initscripts 7.28.1
>>modutils, lvm2.2.00.08
>>mkinitrd-3.5.15.1-2
>>
>>If I just ignore the message and try to boot the machine with the new
>>kernel then I get a Kernel Panic.
>>
>>VFS: Cannot open root device "LABEL=/" or unknown-block(0,0)
>>Please append a correct "root=" boot option
>>Kernel panic: VFS: Unapble to mount root fs on unknown-block(0,0).
>>
>>The boot command in grub is
>>root (hd0,0)
>>kernel /vmlinuz-2.6.1 ro root=LABEL=/ hdc=ide-scsi
>>initrd /initrd-2.6.1.img
>>
>>It is basically the same (except the version) as I use for
>>2.4.20-28 so
>>I assume the label is correct.
>>
>>I saw quite a few messages of similar type but no real answer to the
>>problem. Any Ideas what it could be ?  I am using RH9.0
>>    
>>
>
>hi!
>
>as mentioned in this thread
>(http://marc.theaimsgroup.com/?l=linux-kernel&m=107330398724534&w=2) a
>few days ago, christophe saout wrote: "LABEL= is a RedHat extension.
>Please use the normal root options that is described in the Grub or
>kernel documentation."
>rik van riel mentioned: "It's not even a Red Hat extension.  The LABEL=
>stuff is done entirely in userspace, on the initrd.
>
>If you do not want to use an initrd, you need to use the normal root
>options instead, something like root=/dev/hda3" that thread also offers
>some information to the problem."
>
>have you created an initrd? if not, comment that line out of your grub
>config.
>
>you can leave your fstab like it is, using labels in fstab is ok.
>
>hth
>christian
>
>  
>
>>Thanks
>>Alex
>>    
>>
>
>-
>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: Cannot boot after new Kernel Build

[Christian Kivalo]

> Hi,
> I am trying to build a new kernel but what ever version 2.4.24, 2.6.0,
> 2.6.1 i am trying to build I come across the same problem.
>
> when doing a "make install" i get the following error.
>
> /dev/mapper/control: open failed: No such file or directlry
> Is device-mapper driver missing from kernel?
> Comman failed.
>
> I have installed the lates packages
> device mapper 1.00.07
> initscripts 7.28.1
> modutils, lvm2.2.00.08
> mkinitrd-3.5.15.1-2
>
> If I just ignore the message and try to boot the machine with the new
> kernel then I get a Kernel Panic.
>
> VFS: Cannot open root device "LABEL=/" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unapble to mount root fs on unknown-block(0,0).
>
> The boot command in grub is
> root (hd0,0)
> kernel /vmlinuz-2.6.1 ro root=LABEL=/ hdc=ide-scsi
> initrd /initrd-2.6.1.img
>
> It is basically the same (except the version) as I use for
> 2.4.20-28 so
> I assume the label is correct.
>
> I saw quite a few messages of similar type but no real answer to the
> problem. Any Ideas what it could be ?  I am using RH9.0

hi!

as mentioned in this thread
(http://marc.theaimsgroup.com/?l=linux-kernel&m=107330398724534&w=2) a
few days ago, christophe saout wrote: "LABEL= is a RedHat extension.
Please use the normal root options that is described in the Grub or
kernel documentation."
rik van riel mentioned: "It's not even a Red Hat extension.  The LABEL=
stuff is done entirely in userspace, on the initrd.

If you do not want to use an initrd, you need to use the normal root
options instead, something like root=/dev/hda3" that thread also offers
some information to the problem."

have you created an initrd? if not, comment that line out of your grub
config.

you can leave your fstab like it is, using labels in fstab is ok.

hth
christian

> Thanks
> Alex

Re: Cannot boot after new Kernel Build

[Bongani Hlope]

[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]

On Sat, 10 Jan 2004 17:21:32 +0900
Alex <alex@meerkatsoft.com> wrote:

> Hi,
> I am trying to build a new kernel but what ever version 2.4.24, 2.6.0,
> 2.6.1 i am trying to build I come across the same problem.
> 
> when doing a "make install" i get the following error.
> 
> /dev/mapper/control: open failed: No such file or directlry
> Is device-mapper driver missing from kernel?
> Comman failed.
> 
> I have installed the lates packages
> device mapper 1.00.07
> initscripts 7.28.1
> modutils, lvm2.2.00.08
> mkinitrd-3.5.15.1-2
> 
> If I just ignore the message and try to boot the machine with the new
> kernel then I get a Kernel Panic.
> 
> VFS: Cannot open root device "LABEL=/" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unapble to mount root fs on unknown-block(0,0).
> 
> The boot command in grub is
> root (hd0,0)
> kernel /vmlinuz-2.6.1 ro root=LABEL=/ hdc=ide-scsi
> initrd /initrd-2.6.1.img
> 
> It is basically the same (except the version) as I use for 2.4.20-28 so
> I assume the label is correct.
	     ^^^^^^^^^
The label is the problem

update your /etc/fstab file to something like

/dev/hda1 / ext3 defaults 1 1

instead of
/ / ext3 default 1 1 (IIRC)

> 
> I saw quite a few messages of similar type but no real answer to the
> problem. Any Ideas what it could be ?  I am using RH9.0
> 
> Thanks
> Alex





[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Cannot boot after new Kernel Build

[Alex]

Hi,
I am trying to build a new kernel but what ever version 2.4.24, 2.6.0,
2.6.1 i am trying to build I come across the same problem.

when doing a "make install" i get the following error.

/dev/mapper/control: open failed: No such file or directlry
Is device-mapper driver missing from kernel?
Comman failed.

I have installed the lates packages
device mapper 1.00.07
initscripts 7.28.1
modutils, lvm2.2.00.08
mkinitrd-3.5.15.1-2

If I just ignore the message and try to boot the machine with the new
kernel then I get a Kernel Panic.

VFS: Cannot open root device "LABEL=/" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic: VFS: Unapble to mount root fs on unknown-block(0,0).

The boot command in grub is
root (hd0,0)
kernel /vmlinuz-2.6.1 ro root=LABEL=/ hdc=ide-scsi
initrd /initrd-2.6.1.img

It is basically the same (except the version) as I use for 2.4.20-28 so
I assume the label is correct.

I saw quite a few messages of similar type but no real answer to the
problem. Any Ideas what it could be ?  I am using RH9.0

Thanks
Alex