hi!
this weekend i wanted to install slackware 9.1 on my "new" server.
i have two harddrives: hda and hdc
hda is a 45 gb ibm drive
hdc is a 4,3 gb seagate drive

i partitioned the drives after i booted from the slackware cd

hda1 boot linux raid autodetect 4 gb
hda2 linux swap 300 mb
hda3 linux 40 gb

hdc1 boot linux raid autodetect 4gb
hdc2 linux swap 300 mb

after creating those partitions on the drives, i created the file
/etc/raidtab...

raidtab looks like this:
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistens-superblock 1
chunk-size 4

device /dev/hda1
raid-disk 0
device /dev/hdc1
raid-disk 1

after that i created the raid using:
mkraid /dev/md0
then i enabled the swap partions using
swapon /dev/hda2
swapon /dev/hdc2
after that i used the normal slackware 9.1 setup program and installed
everything. i set up everything using the default settings (at least with
lilo and kernel)
and after rebooting the system i get a
"kernel panic:VFS: unable to mount root fs on 9:00" or something like that
i guess i missed something... but i don´t know really what.
maybe i have to modify the fstab file myself?

i already tried to goolge on this, but the things i found didn´t help at
all. also searching through this (and other newsgroups) didn´t show any
related articles...

so does anybody know what i´m doing wrong? and help me solving this problem


thanks
andre

andre

Your setup looks ok.

I think the problem is in the adaptec.s image setup used for your lilo.
From what I rember it loads raid as a module. It has to be compiled in to
the kernel if your boot drive is going to be a raid drive. I got around
this by installing everything I wanted. rebooting using the cd when you
get to the first prompt boot as root=/dev/md0 from there recompile your
kernel with scsi and raid built in.


good Luck

Jeremy

> I think the problem is in the adaptec.s image setup used for your lilo.
> From what I rember it loads raid as a module. It has to be compiled in to
> the kernel if your boot drive is going to be a raid drive. I got around
> this by installing everything I wanted. rebooting using the cd when you
> get to the first prompt boot as root=/dev/md0 from there recompile your
> kernel with scsi and raid built in.

its working now, i had to add md0 and some other things to my fstab file
manually. thought "setup" would do that for me, since it had recognized
md0, swap drives and the other partions, formated them and stuff.. but it
just didnt add any of them into the fstab file.
i tried it several times with no success...

thansk for your help anyway!

now i´m getting my hands dirty getting some other things running redhat
was so much more like windows... one klick and everything was working, but
i never really knew what it was doing

Andre Nottenkaemper wrote:
> hi!
> this weekend i wanted to install slackware 9.1 on my "new" server.
> i have two harddrives: hda and hdc
> hda is a 45 gb ibm drive
> hdc is a 4,3 gb seagate drive
>
> i partitioned the drives after i booted from the slackware cd
>
> hda1 boot linux raid autodetect 4 gb
> hda2 linux swap 300 mb
> hda3 linux 40 gb
>
> hdc1 boot linux raid autodetect 4gb
> hdc2 linux swap 300 mb
[snip]
> and after rebooting the system i get a
> "kernel panic:VFS: unable to mount root fs on 9:00" or something like that

OK, so the error says that the kernel can't find a root filesystem on on
device 9:0, and some research shows that block special device 9:0 is /dev/md0.

Where did you install your system to? Did you install it to /dev/hda1,
/dev/hda3, /dev/hdc1, or /dev/md0? Where ever you installed it to, you'll have
to make sure that the kernel knows that it can find the root filesystem there
(or you'll have to move it to /dev/md0, where the kernel expects to find it).

How is /dev/md0 formatted? /Is/ it formatted? What's on /dev/md0 right now?


--
Lew Pitcher

Master Codewright and JOAT-in-training
Registered Linux User #112576 (http://counter.li.org/)
Slackware - Because I know what I'm doing.