RE: grub/boot redhat9 problem

RE: grub/boot redhat9 problem

[Stephen Reese]

I ran the quickinstall, but I think missed something in the kernel
configuration. I attempted to copy as many setting as I could from a
stock functional kernel, but I think I missed a switch...

-----Original Message-----
From: Kerry Thompson [mailto:kerry@crypt.gen.nz] 
Sent: Tuesday, July 22, 2003 8:58 PM
To: sreese@prcdigital.com
Subject: Re: grub/boot redhat9 problem


Yikes, something's weird. Looks like the ide-disk kernel module isn't
there. Did you run 'make modules_install' after building the kernel to
install the kernel modules ?

Kerry

Stephen Reese said:
> kmod: failed to exec /sbinmodprobe -s -k ide-disk, errno2
> VFS: Cannot open root device "hda2" or 03:02
> Please apend a correct "root" boot option
> Kernel panic: VFS: Unable to mount root fs on 03:02
>
>
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/hda2              25G  1.8G   22G   8% /
> /dev/hda1              99M   39M   56M  41% /boot
> none                  504M     0  504M   0% /dev/shm
>
> # grub.conf generated by anaconda
> #
> # Note that you do not have to rerun grub after making changes to this

> file # NOTICE:  You have a /boot partition.  This means that
> #          all kernel and initrd paths are relative to /boot/, eg. #
>      root (hd0,0)
> #          kernel /vmlinuz-version ro root=/dev/hda2
> #          initrd /initrd-version.img
> #boot=/dev/hda
> default=2
> timeout=10
> splashimage=(hd0,0)/grub/splash.xpm.gz
> title Red Hat Linux (2.4.21-selinux)
> 	root (hd0,0)
> 	kernel /vmlinuz-2.4.21-selinux ro root=/dev/hda2
> 	initrd /initrd-2.4.21-selinux.img
> title Red Hat Linux (2.4.20-19.9)
> 	root (hd0,0)
> 	kernel /vmlinuz-2.4.20-19.9 ro root=LABEL=/
> 	initrd /initrd-2.4.20-19.9.img
> title Red Hat Linux (2.4.20-19.9smp)
> 	root (hd0,0)
> 	kernel /vmlinuz-2.4.20-19.9smp ro root=LABEL=/
> 	initrd /initrd-2.4.20-19.9smp.img
> title Red Hat Linux (2.4.20-18.9)
> 	root (hd0,0)
> 	kernel /vmlinuz-2.4.20-18.9 ro root=LABEL=/
> 	initrd /initrd-2.4.20-18.9.img
> title Red Hat Linux (2.4.20-18.9smp)
> 	root (hd0,0)
> 	kernel /vmlinuz-2.4.20-18.9smp ro root=LABEL=/
> 	initrd /initrd-2.4.20-18.9smp.img
> title Red Hat Linux (2.4.20-8smp)
> 	root (hd0,0)
> 	kernel /vmlinuz-2.4.20-8smp ro root=LABEL=/
> 	initrd /initrd-2.4.20-8smp.img
> title Red Hat Linux-up (2.4.20-8)
> 	root (hd0,0)
> 	kernel /vmlinuz-2.4.20-8 ro root=LABEL=/
> 	initrd /initrd-2.4.20-8.img
> -----Original Message-----
> From: owner-selinux@tycho.nsa.gov [mailto:owner-selinux@tycho.nsa.gov]
> On Behalf Of Kerry Thompson
> Sent: Monday, July 21, 2003 10:59 PM
> To: sreese@prcdigital.com
> Cc: selinux@tycho.nsa.gov
> Subject: RE: make quickinstall redhat9 problem
>
>
> Stephen Reese said:
>> installing tk and tcl was the trick thanks for the help now I get to 
>> figure out where I went wrong with the kernel complile =)
>>
>> VFS: cannot open root device "Label=/"
>
> Change your bootloader ( /boot/grub/grub.conf for GRUB ) to use 
> root=/dev/hda1 or wherever your root is rather than using Label=/
>
> Kerry
>
>
> --
> Kerry Thompson, CCNA CISSP
> Information Systems Security Consultant http://www.crypt.gen.nz  
> kerry@crypt.gen.nz
>
>
>
> --
> This message was distributed to subscribers of the selinux mailing 
> list. If you no longer wish to subscribe, send mail to 
> majordomo@tycho.nsa.gov with the words "unsubscribe selinux" without 
> quotes as the message.
>
>
> --
> This message was distributed to subscribers of the selinux mailing 
> list. If you no longer wish to subscribe, send mail to 
> majordomo@tycho.nsa.gov with the words "unsubscribe selinux" without 
> quotes as the message.





--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: grub/boot redhat9 problem

[Russell Coker]

On Wed, 23 Jul 2003 01:07, Stephen Reese wrote:
> I ran the quickinstall, but I think missed something in the kernel
> configuration. I attempted to copy as many setting as I could from a
> stock functional kernel, but I think I missed a switch...

The problem here is that 2.4.21 needs different settings to 2.4.20.  This is 
not a SE Linux issue, I strongly recommend that you ask on your local LUG 
mailing list or another resource for solving general Linux problems.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

RE: grub/boot redhat9 problem

[Stephen Reese]

Well if that's the issue then I'll simply wait until redhat release the
*.21 release for my system and then go from there. Thank you and
everyone else for your time.

-----Original Message-----
From: Russell Coker [mailto:russell@coker.com.au] 
Sent: Thursday, July 24, 2003 11:02 AM
To: Stephen Reese; selinux@tycho.nsa.gov
Subject: Re: grub/boot redhat9 problem


On Wed, 23 Jul 2003 01:07, Stephen Reese wrote:
> I ran the quickinstall, but I think missed something in the kernel 
> configuration. I attempted to copy as many setting as I could from a 
> stock functional kernel, but I think I missed a switch...

The problem here is that 2.4.21 needs different settings to 2.4.20.
This is 
not a SE Linux issue, I strongly recommend that you ask on your local
LUG 
mailing list or another resource for solving general Linux problems.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux
packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page



--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: grub/boot redhat9 problem

[Russell Coker]

On Tue, 22 Jul 2003 19:25, Stephen Reese wrote:
> kmod: failed to exec /sbinmodprobe -s -k ide-disk, errno2
> VFS: Cannot open root device "hda2" or 03:02
> Please apend a correct "root" boot option
> Kernel panic: VFS: Unable to mount root fs on 03:02

That's an issue of configuring the modules for a 2.4.21 kernel in a way that 
doesn't work (kernel is buggy).  Compile the IDE drivers into the kernel to 
solve this.

Also I strongly recommend that you compile and boot a non-SE kernel first 
before you try to get SE Linux running.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page



--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

grub/boot redhat9 problem

[Stephen Reese]

kmod: failed to exec /sbinmodprobe -s -k ide-disk, errno2
VFS: Cannot open root device "hda2" or 03:02
Please apend a correct "root" boot option
Kernel panic: VFS: Unable to mount root fs on 03:02


Filesystem            Size  Used Avail Use% Mounted on
/dev/hda2              25G  1.8G   22G   8% /
/dev/hda1              99M   39M   56M  41% /boot
none                  504M     0  504M   0% /dev/shm

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this
file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/hda2
#          initrd /initrd-version.img
#boot=/dev/hda
default=2
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.21-selinux)
	root (hd0,0)
	kernel /vmlinuz-2.4.21-selinux ro root=/dev/hda2
	initrd /initrd-2.4.21-selinux.img
title Red Hat Linux (2.4.20-19.9)
	root (hd0,0)
	kernel /vmlinuz-2.4.20-19.9 ro root=LABEL=/
	initrd /initrd-2.4.20-19.9.img
title Red Hat Linux (2.4.20-19.9smp)
	root (hd0,0)
	kernel /vmlinuz-2.4.20-19.9smp ro root=LABEL=/
	initrd /initrd-2.4.20-19.9smp.img
title Red Hat Linux (2.4.20-18.9)
	root (hd0,0)
	kernel /vmlinuz-2.4.20-18.9 ro root=LABEL=/
	initrd /initrd-2.4.20-18.9.img
title Red Hat Linux (2.4.20-18.9smp)
	root (hd0,0)
	kernel /vmlinuz-2.4.20-18.9smp ro root=LABEL=/
	initrd /initrd-2.4.20-18.9smp.img
title Red Hat Linux (2.4.20-8smp)
	root (hd0,0)
	kernel /vmlinuz-2.4.20-8smp ro root=LABEL=/
	initrd /initrd-2.4.20-8smp.img
title Red Hat Linux-up (2.4.20-8)
	root (hd0,0)
	kernel /vmlinuz-2.4.20-8 ro root=LABEL=/
	initrd /initrd-2.4.20-8.img
-----Original Message-----
From: owner-selinux@tycho.nsa.gov [mailto:owner-selinux@tycho.nsa.gov]
On Behalf Of Kerry Thompson
Sent: Monday, July 21, 2003 10:59 PM
To: sreese@prcdigital.com
Cc: selinux@tycho.nsa.gov
Subject: RE: make quickinstall redhat9 problem


Stephen Reese said:
> installing tk and tcl was the trick thanks for the help now I get to 
> figure out where I went wrong with the kernel complile =)
>
> VFS: cannot open root device "Label=/"

Change your bootloader ( /boot/grub/grub.conf for GRUB ) to use
root=/dev/hda1 or wherever your root is rather than using Label=/

Kerry


-- 
Kerry Thompson, CCNA CISSP
Information Systems Security Consultant
http://www.crypt.gen.nz  kerry@crypt.gen.nz



--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov
with the words "unsubscribe selinux" without quotes as the message.


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.