Thanks, I checked all 4 of your bullets -
(1) I assume I have autodetection since dmesg|more says
autodetecting RAID arrays
and then gives facts about the raid like
(read) sdc2's sb offset: 2835392 [events: 00000002]
...
autorun ...
...
created md1
bind <sdc2,1>
...
running: <sde2><sdd2><sdc2>
now!
sde2's event counter: 00000002
...
kmod: failed to exec /sbin/modprobe -s -k md-personality-4, errno = 2
do_md_run() returned -22
unbind<sde2,2>
...
and from there it's all downhill.
(2) persistent-superblock yes
(3) partition types fd - yes, though it was AFTER my mkraid, I'm trying a
redo of that now
(4) a modprobe -c revealed md-personality-4 raid5 (and all the others) and
I even added it to conf.modules, with no improvement.
The key is obviously that modprobe -s -k event but there is nothing in the
modprobe doc that describes these "secret" options or the meaning of error 2.
Thanks,
Larry
At 11:23 PM 6/11/99 +0200, you wrote:
>Hi,
>
>> Personalities:
>> read-ahead not set
>> unused devices: <none>
>>
>> All the partitions are type 83, does that make a difference? I
>> seem to remember something about a type fd partition?
>
>Quoting from the current Software-RAID.HOWTO.txt.0.90.3
>(from http://ostenfeld.dk/~jakob/Software-RAID.HOWTO/. )
>
> 1. You need autodetection support in the kernel. Check this
>
> 2. You must have created the RAID devices using persistent-superblock
>
> 3. The partition-types of the devices used in the RAID must be set to
> 0xFD (use fdisk and set the type to `fd'')
>
>
>And, of course, you should have built the needed type of RAID (0145)
>built into the kernel (or use initrd i think).
>
>Should do the trick.
>
>
>
