"Unable to mount root fs on unknown-block(0,0)"
(I have sent this message twice before but it did not appear on the list .. seems that there is some prob)
Yes I am booting with an initrd. Basically I do a 'make install' after make 'make modules_install'. The steps that I perform:
make mrproper
make menuconfig
make clean
make bzImage
make modules
make modules_install
make install
I also updated the mkinitrd (now i have the 3.4.42 version). Does that have the patch ? Btw I did not find any documentation in linux2.6/README about the patch for the mkinitrd script. ( I hope i looked at the right README !!! ).
The system is still giving the same error !
Also I am resending the .config file.
Thanks,
-Ripin
----- Original Message -----
From: "Stephen Smalley" <[email protected]>
To: "Ripin Natani" <[email protected]>
Sent: Tuesday, August 19, 2003 9:01 AM
Subject: Re: "Unable to mount root fs on unknown-block(0,0)"
Quoted 3 lines · Ripin Natani
Quoted 2 lines
Hi,
I am trying to run a custom compiled SElinux kernel with as small
as
Quoted 19 lines
Quoted 4 lines
possible (with support for nfs and mounting and basic networking capabilities). I get the following error when i use the custom compiled image
"Unable to mount root fs on unknown-block(0,0)"Are you boot it with an initrd? Did you patch your mkinitrd script per the README so that the initial policy load will occur from the initrd?
The root=LABEL=/ should work fine as long as you are using an initrd (which you should be using, to perform the initial policy load, unless using the old 2.4-based SELinux). If you weren't using an initrd, you would need to specify the actual root device, e.g. root=/dev/hda2 or whatever is appropriate for your system.
--
Stephen Smalley <[email protected]>
National Security Agency
Quoted 6 lines · Ripin Natani
I also updated the mkinitrd (now i have the 3.4.42 version). Does that have the patch ? Btw I did not find any documentation in linux2.6/README about the patch for the mkinitrd script. ( I hope i looked at the right README !!! ).
The system is still giving the same error !
Also I am resending the .config file.
The .config file you attached still has the CONFIG_SECURITY options turned off which means that either you attached the wrong .config file or you did not compile a SE Linux kernel.
If the .config file is the correct file then it indicates that the problem is a general 2.6 kernel issue not a SE Linux issue, in which case this list probably isn't going to be the best source of advice on the matter.
Signature · 10 lines
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 [email protected] with the words "unsubscribe selinux" without quotes as the message.