> From [EMAIL PROTECTED] Wed Jan 6 11:25:19 1999
>
> Jack Gavigan wrote:
> >
> > >While I'm not new to Linux or RAID, I am new to RAID on Linux.
> > >I've read the Root-RAID-HOWTO about 10 times and I'm about as
> > >confused as when I first started.
> >
>
> > My question, I guess, is: Am I right in thinking that it's necessary to
> > create a script in rc2.d which executes raidrun and mount, and another in
> > rc0.d which runs unmount and raidstop, to mount and unmount my raid
> > partition?
> >
> > The OS I'm using is Redhat 5.2, 2.0.38 kernel recompiled for SMP (2
> > Pentiums, 320Mb RAM) with RAID support included at compile time. Version of
> > raidtools in use is raidtools-0.50beta10 (off the RedHat CD). Setup is a
> > pair of internal 2Gb Seagate Barracudas, sda1/sdb1 are the root partitions
> > which aren't going to be raided, partitions 2 and 3 are swap and tmp and
> > sda4/sdb4 are the two partitions I'm mirroring as md0. There's also a
> > JADLogic RAID on /dev/sdc, but that doesn't have anything to do with the
> > software raid - it's hardware. The only other idiosyncracy is that there are
> > two network cards...
>
> Get rid of the raidtools that shipped with RedHat. Then remove all reference to
> RAID in /etc/rc.d/rc.sysinit and /etc/rc.d/init.d/halt. Then get hold of the
> raidtools 0.90 source, and compile that. Kernel - 2.0.38 doesn't exist :-). I
> suggest using a clean 2.0.36 source tree, and patching that for RAID support.
> Don't use the kernel source provided with RH 5.2, it's a 2.0.36 pre release,
> with lots of weird patches added. Compile, and enable RAID-autostart. Then,
> use fdisk to change the partition id's of the partitions making up your RAID
> devices to 0xfd. After this, the kernel will auto-start and auto-stop your RAID
> devices at boot and shutdown. You will not need any support in scripts at all.
Aha!!!!! I was having all kinds of problems with 2.1.127 and raidtools0.90.
Redhat 5.2 installs the broken raidtools 0.50beta by default. I had to
rpm -e the package and then things worked normally afterwards.
Thanks!
Chris
--
Christopher Mauritz
[EMAIL PROTECTED]
