I just installed slackware 9.1 and installed a RAID5 on it with reiserfs. It seems to
work just fine with a single processor and the kernel that the slack
install comes with. My system is dual cpu and I
want to compile a kernel with SMP.

So I compiled the kernel source that came with slackware with some added
networking modules and smp support. I added in a new label in lilo and the
new kernel shows up at the boot menu and it starts to boot BUT I get this
error:

Please append correct "root=" boot option
Kernel Panic: VFS: Unable to mount root fs on 09:00

Also, with the kernel that comes with slack (the single cpu version) I can
boot up in VESA mode, but in my custom kernel, it doesn't boot into VESA.
I have compiled reiserfs into the kernel, not as a module. The size of the
bzImage is about 1.4MB.

anyone know whats up?

-ryan

Sorry for the top post

Including either the output of dmesg or the content of lilo.conf would
help...


On Wed, 12 May 2004 17:50:17 -0700, Ryan wrote:

> I just installed slackware 9.1 and installed a RAID5 on it with reiserfs. It seems to
> work just fine with a single processor and the kernel that the slack
> install comes with. My system is dual cpu and I
> want to compile a kernel with SMP.
>
> So I compiled the kernel source that came with slackware with some added
> networking modules and smp support. I added in a new label in lilo and the
> new kernel shows up at the boot menu and it starts to boot BUT I get this
> error:
>
> Please append correct "root=" boot option
> Kernel Panic: VFS: Unable to mount root fs on 09:00
>
> Also, with the kernel that comes with slack (the single cpu version) I can
> boot up in VESA mode, but in my custom kernel, it doesn't boot into VESA.
> I have compiled reiserfs into the kernel, not as a module. The size of the
> bzImage is about 1.4MB.
>
> anyone know whats up?
>
> -ryan

Ryan wrote:

> Kernel Panic: VFS: Unable to mount root fs on 09:00

The kernel can't talk to the device on which the root file system
resides. You said you installed a RAID set on this system. Is your
root filesystem on that RAID set, and if so, is the appropriate driver
compiled into the kernel?

> Also, with the kernel that comes with slack (the single cpu version)
> I can boot up in VESA mode, but in my custom kernel, it doesn't boot
> into VESA.

Check your kernel configuration: do you have support for VESA text
modes enabled?

I hope that helps ...

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Systems analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

On Wed, 12 May 2004, Ryan wrote:
> I just installed slackware 9.1 and installed a RAID5 on it with
> reiserfs. It seems to
> work just fine with a single processor and the kernel that the slack
> install comes with. My system is dual cpu and I
> want to compile a kernel with SMP.
> So I compiled the kernel source that came with slackware with some added
> networking modules and smp support. I added in a new label in lilo and the
> new kernel shows up at the boot menu and it starts to boot BUT I get this
> error:
> Please append correct "root=" boot option
> Kernel Panic: VFS: Unable to mount root fs on 09:00
> Also, with the kernel that comes with slack (the single cpu version) I can
> boot up in VESA mode, but in my custom kernel, it doesn't boot into VESA.
> I have compiled reiserfs into the kernel, not as a module. The size of the
> bzImage is about 1.4MB.
> anyone know whats up?

welllllllllllll, if your kernel is trying to load the reiserfs
modules from a reiser file system, it ain't gonna work, because
the kernel doesn't yet have the reiserfs modules loaded up needed
to access the reiserfs you're trying to load the reiserfs modules
from.

ok?

i might also guess that the kernel config you modified
was not the config for the kernel which you can boot non-SMP.

start with a known working config. compile install and boot it to
be certain that it is a working config. then modify that to get
what you want. remove any unnescessary stuff to make it smaller.
the standard kernels are config'd to work on as many machines as
possible, and so will include lots of things you can remove.




--
Fire the Liars - Impeach Bush!
Corruption starts at the top.

William Hunt, Portland Oregon USA

On Thu, 13 May 2004 04:41:03 +0000, Sylvain Robitaille wrote:

> Ryan wrote:
>
>> Kernel Panic: VFS: Unable to mount root fs on 09:00
>
> The kernel can't talk to the device on which the root file system
> resides. You said you installed a RAID set on this system. Is your
> root filesystem on that RAID set, and if so, is the appropriate driver
> compiled into the kernel?
>
> Check your kernel configuration: do you have support for VESA text
> modes enabled?
>
> I hope that helps ...

Well, somehow my .config file had gotten mangled. I enabled most things I
had off before and some things had mysteriously gotten turned off or not
saved. So after a few more painful recompiles, I got it to boot, I'm not
100% exactly what the problem was, I assume my RAID modules weren't all
there.

Either way, I now have 2 CPUs, but the only thing that doesn't make sense
to me now is this.

When I did a df in the first kernel I saw /dev/md0 and /dev/md1. In my newly
compiled kernel I see only /dev/md0, which is my main RAID partition. I
don't see any errors in the /var/log/messages. I haven't changed anything
in lilo*.conf, except telling the files to point to my new kernel. My
raidtab has remained untouched.

Only /dev/md0 was appearing in my 'cat /proc/mdstat' so I did a 'raidstart
/dev/md1' and now the drives are trying to resync. This doesn't seem right
since they already synced last night (but with a different kernel).

Should all I see is /dev/md0? or should I also see /dev/md1. This is a
RAID5 running reiserfs.

thanks
-ryan

Ryan wrote:
>
> When I did a df in the first kernel I saw /dev/md0 and /dev/md1. In my newly
> compiled kernel I see only /dev/md0, which is my main RAID partition. I
> don't see any errors in the /var/log/messages. I haven't changed anything
> in lilo*.conf, except telling the files to point to my new kernel. My
> raidtab has remained untouched.
>
> Only /dev/md0 was appearing in my 'cat /proc/mdstat' so I did a 'raidstart
> /dev/md1' and now the drives are trying to resync. This doesn't seem right
> since they already synced last night (but with a different kernel).
>
> Should all I see is /dev/md0? or should I also see /dev/md1. This is a
> RAID5 running reiserfs.

Did you set the RAID partitions with fdisk to type "FD" so it is
found during boot? Be sure to run raidstop before making the
change with fdisk.

--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.1.0 Kernel 2.4.26 SMP i686 (GCC) 3.3.3
Uptime: 8 days, 12:47, 2 users, load average: 0.01, 0.15, 0.68

>
> Did you set the RAID partitions with fdisk to type "FD" so it is
> found during boot? Be sure to run raidstop before making the
> change with fdisk.


yes, all the RAID types are 'FD'.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, Martin Lefebvre dared to utter,
> Sorry for the top post

Then why did you do it? Pan is perfectly capable of in-line posting.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFApB4xL3KiNGOqr6ERAkw4AJwPxq7CbGx9cXY3wiUQp+ LXlkAmWgCfeiEC
LB5OLefHAv0RZqqe7dZvC40=
=Root
-----END PGP SIGNATURE-----

Alan Hicks <alan@lizella.network> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> In alt.os.linux.slackware, Martin Lefebvre dared to utter,
> > Sorry for the top post

> Then why did you do it? Pan is perfectly capable of in-line posting.

A better question would be why do you include pgp trash in your
postings? Nobody wants to see it and it serves no purpose.

Does it make you feel secure?

cordially, even to real trash,

rm

NOTE: This message was sent thru a mail2news gateway.
No effort was made to verify the identity of the sender.
--------------------------------------------------------

pgp trash troll delete

Alan Hicks <alan@lizella.network> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> In alt.os.linux.slackware, Martin Lefebvre dared to utter,
> > Sorry for the top post

> Then why did you do it? Pan is perfectly capable of in-line posting.

> - --
> It is better to hear the rebuke of the wise,
> Than for a man to hear the song of fools.
> Ecclesiastes 7:5
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)

> iD8DBQFApB4xL3KiNGOqr6ERAkw4AJwPxq7CbGx9cXY3wiUQp+ LXlkAmWgCfeiEC
> LB5OLefHAv0RZqqe7dZvC40=
> =Root
> -----END PGP SIGNATURE-----