lkml.org 
[lkml]   [2004]   [Jan]   [10]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateSat, 10 Jan 2004 11:37:12 +0200
FromBongani Hlope <>
SubjectRe: Cannot boot after new Kernel Build
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




[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2005-03-22 12:59    [W:27.438 / U:0.110 seconds]
©2003-2008 Jasper Spaans