Carl,
The 2.2.4 kernel does not have the latest raid code. But, the raid
patches do not yet cleanly apply to the 2.2.4 kernel. I suggest you
start with the 2.2.3 kernel, apply the appropriate raid patches
(raid0145-19990309-2_2_3.gz), and get the latest raidtools
(raidtools-19990309-0_90_tar.gz). The best, but not great,
documentation comes with the raidtools.
<>< Lance.
> Carl Hilinski wrote:
>
> I am quickly reaching the end of the rope. I wanted to learn about
> RAID in linux (having used it much in NT), so I tried to patch Redhat
> 2.0.36 with the 0145 raid patch, which simply returned "XXXXX not set"
> messages in defconfig.rej. Since I could find no info on what to do to
> solve that, I upgraded to kernel 2.2.4 (which I assume doesn't need
> the 0145 patch since it has the "personalities" and raid 1 and 5 can
> be selected in the make config). So I set up a 100+mb partition as
> hda5 and a 100+mb partition on hdb1(both of which were configured
> under the original Redhat 5.2 install), umounted them, set up the
> raidtab to say use Raid 1 with the /dev/hda5 and /dev/hdb1 partitions,
> no spares and the persistent superblock 1 value. When I do a
> mkraid --really-force /dev/md1, I get the message:
> disk 0: /dev/hdb1 166129kb, raid superblock at 166016kb
> disk 1: /dev/hda5 167296kb, raid superblock at 167232kb
> mkraid: aborted
>
> What happened? I've spent days and days on trying to make this work (I
> had to install a WinNT server because I had a deadline and couldn't
> make this work). What did I do wrong? And how would I know? There's no
> docs on what happens when it all goes wrong.
>
> ch
