Hi Bill,
You need to get the latest raid kernel patch (ignore the errors it gives... 
one hunk is included in the 2.2.12/2.2.13 kernel) and the latest raidtools 
(0.90).


At 03:17 PM 10/27/99 -0500, Bill Carlson wrote:
>Hello,
>
>I'm trying to setup your basic RAID0 Software raid and running into some
>problems.
>
>Details:
>
>Mandrake 6.1,(not RedHat!)
>Kernel 2.2.13 and 2.2.12
>2 SCSI drives, completely seperate from root, 4 GB each
>
>My test raidtab (/etc/raidtab.test)
>
>raiddev /dev/md0
>         raid-level      0
>         nr-raid-disks   2
>         persistent-superblock   1
>         chunk-size      8
>
>         device  /dev/sdb1
>         raid-disk       0
>
>         device  /dev/sdc1
>         raid-disk       1
>
>
>
>
>When I run mkraid I get the following:
>
>[root@washu /root]# mkraid -c /etc/raidtab.test /dev/md0
>handling MD device /dev/md0
>analyzing super-block
>disk 0: /dev/sdb1, 4192933kB, raid superblock at 4192832kB
>disk 1: /dev/sdc1, 4192933kB, raid superblock at 4192832kB
>mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
>
>Output from /proc/mdstat:
>
>[root@washu /root]# chkraid
>Personalities : [2 raid0]
>read_ahead not set
>md0 : inactive
>md1 : inactive
>md2 : inactive
>md3 : inactive
>[root@washu /root]#
>
>Nothing of note in syslogd (*.* >> /dev/tty12)
>
>Any ideas on what I am doing wrong?
>
>I just joined the list, are there any searchable archives?
>Is a kernel patch still required for the 2.2.1x series?
>
>Thanks in advance,
>
>
>Bill Carlson
>------------
>Systems Programmer    [EMAIL PROTECTED]    |  Opinions are mine,
>Virtual Hospital      http://www.vh.org/        |  not my employer's.
>University of Iowa Hospitals and Clinics        |
>
>

===========================================================
            David Cooley N5XMT           Internet: [EMAIL PROTECTED]
      Packet: N5XMT@KQ4LO.#INT.NC.USA.NA   T.A.P.R. Member #7068
    Sponges grow in the ocean... Wonder how deep it would be if they didn't?!
===========================================================

Reply via email to