encrypted fs over raid5?

["M.G." <glasgow@beer.net>]

Has anyone successfully set up an encrypted filesystem using loopback
on top of raid5?  I am very interested in getting this working,
but right now I'm stuck very early on in the process just getting
raid5 to work.

I am running potato and I've custom compiled a fresh 2.2.18 kernel
with patch-int-2.2.18.3 from kerneli.org.  I compiled almost every
kernel option as a module, including the crypto and raid stuff.

Here's the error I get and some more relevant info about my system:

drink:~$ sudo mkraid /dev/md0
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sdc1, 8883913kB, raid superblock at 8883840kB
disk 1: /dev/sdd1, 8883913kB, raid superblock at 8883840kB
disk 2: /dev/sde1, 8883913kB, raid superblock at 8883840kB
disk 3: /dev/sdf1, 8883913kB, raid superblock at 8883840kB
disk 4: /dev/sdg1, 8883913kB, raid superblock at 8883840kB
mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
drink:~$ cat /proc/mdstat 
Personalities : [1 linear] [2 raid0] [3 raid1] [4 raid5]
read_ahead not set
md0 : inactive
md1 : inactive
md2 : inactive
md3 : inactive
drink:~$ cat /etc/raidtab 
raiddev /dev/md0
    raid-level      5
    nr-raid-disks   4
    nr-spare-disks  1
    persistent-superblock 1
    parity-algorithm left-symmetric
    chunk-size      32
    device          /dev/sdc1
    raid-disk       0
    device          /dev/sdd1
    raid-disk       1
    device          /dev/sde1
    raid-disk       2
    device          /dev/sdf1
    raid-disk       3
    device          /dev/sdg1
    spare-disk      0
drink:~$ lsmod
Module                  Size  Used by
nbd                    13384   0 (unused)
linear                  1208   0 (unused)
loop                    8192   0 (unused)
raid1                   7104   0 (unused)
raid0                   2168   0 (unused)
raid5                  16160   0 (unused)
vfat                    9668   1
fat                    31008   1 [vfat]
drink:~$ dpkg -l | grep raid
ii  raidtools2     0.90.990824-5  Utilities to support 'new-style' RAID disks
drink:~$ uname -a
Linux drink 2.2.18 #1 SMP Thu Mar 15 22:24:33 CST 2001 i686 unknown


Unfortunately mkraid lies about there being additional info logged
to syslog or /proc/mdstat.  I enabled *.debug in syslog and still
get nothing.  Is it possible I need to have another module loaded
in order for raid to function?  What gives?

Thanks,

-- 
Michael Glasgow <glasgow@beer.net> | "The people never give up their
PGP Fingerprint: 7D CD 24 D2 94 0F | liberties but under some delusion."
     66 F0 8A 8A 39 8D B4 11 89 AE |                --Edmund Burke, 1784