Red Hat Kernel - unable to mount root fs

This is Interesting: Free IT Magazines  
Home > Archive > Red Hat Kernel > January 2004 > unable to mount root fs





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author unable to mount root fs
tonic889@nothanks.earthlink.net

2004-01-23, 7:28 pm

I tried to upgrade my RedHat 9 system from kernel 2.4.20 to v2.4.23,
using the sources from kernel.org (not the RedHat-distributed kernel
versions). I have successfully upgraded my kernel before, so I used
make oldconfig to create my .config file, and modified a few options.
But after 'make dep bzImage modules modules_install install' (and
reboot), I got an error message that says:

VFS: Cannot open root device "302" or 03:02
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 03:02

At that point, I decided to try to recompile the 2.4.20 using the
original .config I had used to successfully compile the first time.
Boy, was that a mistake. I didn't realize it was going to overwrite my
existing /lib/modules/2.4.20. And to top it off, I'm still getting the
above error message in 2.4.20, even though I'm using the exact same
..config and the exact kernel version that worked for me before! I don't
understand how this is possible. What am I missing?

I tried googling around on this error message and found other people
with this problem, and the common solution seemed to be that the / fs
type was not compiled into the kernel. However my root fs type is EXT2
(according to a previous kernel which runs OK), and I have
CONFIG_EXT2_FS=y in my .config file. So I don't think that is the
problem. Any other ideas would be greatly appreciated.

The relevant entries from my lilo.conf are as follows:

prompt
timeout=50
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear

image=/boot/vmlinuz-2.4.20
label=2.4.20
initrd=/boot/initrd-2.4.20.img
read-only
root=/dev/hda2

image=/boot/vmlinuz-2.4.23
label=linux_2.4.23
initrd=/boot/initrd-2.4.23.img
read-only
root=/dev/hda2

Thanks,
Brian

Rick10

2004-01-23, 7:28 pm

Make sure you have the driver of the partition type of your root
filesystem compild into the kernel and not as a module.

tonic889@nothanks.earthlink.net wrote:
quote:

> I tried to upgrade my RedHat 9 system from kernel 2.4.20 to v2.4.23,
> using the sources from kernel.org (not the RedHat-distributed kernel
> versions). I have successfully upgraded my kernel before, so I used
> make oldconfig to create my .config file, and modified a few options.
> But after 'make dep bzImage modules modules_install install' (and
> reboot), I got an error message that says:
>
> VFS: Cannot open root device "302" or 03:02
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 03:02
>
> At that point, I decided to try to recompile the 2.4.20 using the
> original .config I had used to successfully compile the first time.
> Boy, was that a mistake. I didn't realize it was going to overwrite my
> existing /lib/modules/2.4.20. And to top it off, I'm still getting the
> above error message in 2.4.20, even though I'm using the exact same
> .config and the exact kernel version that worked for me before! I don't
> understand how this is possible. What am I missing?
>
> I tried googling around on this error message and found other people
> with this problem, and the common solution seemed to be that the / fs
> type was not compiled into the kernel. However my root fs type is EXT2
> (according to a previous kernel which runs OK), and I have
> CONFIG_EXT2_FS=y in my .config file. So I don't think that is the
> problem. Any other ideas would be greatly appreciated.
>
> The relevant entries from my lilo.conf are as follows:
>
> prompt
> timeout=50
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> message=/boot/message
> linear
>
> image=/boot/vmlinuz-2.4.20
> label=2.4.20
> initrd=/boot/initrd-2.4.20.img
> read-only
> root=/dev/hda2
>
> image=/boot/vmlinuz-2.4.23
> label=linux_2.4.23
> initrd=/boot/initrd-2.4.23.img
> read-only
> root=/dev/hda2
>
> Thanks,
> Brian
>




--
Rick Stanback
rstanback@starband.net
"Chance only favors the prepared mind" Louis Pasteur.

tonic889@nothanks.earthlink.net

2004-01-23, 7:28 pm

Rick10 wrote:
quote:

> Make sure you have the driver of the partition type of your root
> filesystem compild into the kernel and not as a module.



As I mentioned before:
quote:


Is there something else I should be doing to compile EXT2 file support?
I thought setting CONFIG_EXT2_FS=y was all I needed.

Thanks,
Brian
[QUOTE][color=darkred]
> tonic889@nothanks.earthlink.net wrote:
>
>
>



Dennis

2004-01-23, 7:28 pm

Brian,

have you checked your lilo configuration? I've had the same problem after
upgrading the kernel. When I manually checked my lilo conf, there was a line
saying append='root=' added to the configuration. After I removed this line
and reinstalled lilo, all was working fine.

Hope this helps,

Regard,

Dennis

<tonic889@nothanks.earthlink.net> wrote in message
news:KQ7Db.3278$mC1.886@newsread1.news.atl.earthlink.net...
quote:

> Rick10 wrote:
>
> As I mentioned before:
>
>
> Is there something else I should be doing to compile EXT2 file support?
> I thought setting CONFIG_EXT2_FS=y was all I needed.
>
> Thanks,
> Brian
>
don't[QUOTE][color=darkred]
greatly appreciated.[QUOTE][color=darkred]
>




Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com