RAID should not be dependent on raidtab to start. In fact, there are plenty of circumstances where one might have a raidtab that is inconsistent with your actual setup. RAID should be started by default using autorecognition based on partition type. The stuff in the init scripts should, at most, be a fallback, where autorecognition has failed to start arrays. Even then, there should probably be some means to indicate that this is what you want to do, rather than just doing it by default, as you might have wanted to temporarily disable the array by changing the partition type. You don't really want to have to edit your raidtab to decide which arrays will or won't start.
I pointed out this (and problems with mkraid during beta3 install) a week ago, but it doesn't seem to have grabbed anyone's attention. Basically, Mandrake could solve their RAID failings once and for all if they would just build RAID (at least 1 and 5) support into their default kernels. Of course, there are other ways of doing it, but no one seems to have figured out how to do it in a more complicated way without breaking various setups. Building RAID into the kernel would cut the Gordian knot.
Cheers,
Bruno Prior
Oden Eriksson wrote:
torsdagen den 20 februari 2003 13.57 skrev Oden Eriksson:Hi.Nice job with the text mode network install (9.0), it automatically found my old md arrays on some old drives I had. Very cool! Didn't know that.
Duh!, i spoke too soon..., it f*cked up the boot since no valid raidtab was created. I was lucky to have that file on backup.
