Derek,
You need to patch your kernel and re-compile it.
If you downloaded the 0.90 raidtools, you need to patch the kernel. It was
designed to run the 0.4X raidtools.
At 07:11 PM 3/2/00, Derek Shaw wrote:
>this is likely a problem that has been solved many times before, so
>I'm hoping there's a FAQ with the answer somewhere. If not, ....
>
>I've just hit the first implementation snag with raidtools-0.90 on a
>slackware 7 kernel 2.2.13.
>
>I've re-compiled the kernel to have md support at RAID-1 included in
>the kernel. I believe I compiled and installed the raidtools
>correctly (is there a better set of instructions than "unpack,
>configure, compile and install the RAID tools" ?) These are
>raidtools-19990824-0.90.tar.gz from the archive at
>ftp.fi.kernel.org/pub/linux/daemons/raid/alpha/
>
>As described in Jakob's HOWTO, I've set up an instance of /etc/raidtab
>to try mirroring my two data drives (/dev/sdb1 and /dev/hdb1), which
>have been created with mke2fs and fsck'd.
>
>mkraid /dev/md0 yields the message
>
>handling MD device /dev/md0
>analyzing super-block
>disk 0: /dev/hdb1, 4217031kB, raid superblock at 4216960kB
>disk 1: /dev/sdb1, 4217031kB, raid superblock at 4216960kB
>mkraid: aborted, see the syslog and /proc/mdstat for potential clues
>
>but syslog is not recording anything to do with mkraid, and I have no
>clue what the contents of /proc/mdstat mean.
>
>here's what's in /proc/mdstat
>Personalities : [3 raid1]
>read_ahead not set
>md0 : inactive
>md1 : inactive
>md2 : inactive
>md3 : inactive
>
>
>
>
>
>--
>Derek Shaw
>Business Information Systems
>Voice:250-885-2021 Fax:250-386-4060
>
===========================================================
David Cooley N5XMT Internet: [EMAIL PROTECTED]
Packet: N5XMT@KQ4LO.#INT.NC.USA.NA T.A.P.R. Member #7068
We are Borg... Prepare to be assimilated!
===========================================================
