On Tue, 18 May 1999, Ingo Molnar wrote:
> Date: Tue, 18 May 1999 14:05:15 +0200 (CEST)
> From: Ingo Molnar <[EMAIL PROTECTED]>
> To: Robert McPeak <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: RAID0 and RedHat 6.0
>
>
> On Mon, 17 May 1999, Robert McPeak wrote:
>
> > Here are the relevant messages from dmesg:
>
> > hdd1's event counter: 0000000c
> > hdb1's event counter: 0000000c
> > request_module[md-personality-2]: Root fs not mounted
> > do_md_run() returned -22
>
> hm, this is the problem, it tries to load the RAID personality module but
> cannot find it, because the root fs is not yet mounted. But
> 'md-personality-2' is strange as well, it should be 'md-personality-0' for
> RAID0, there is no personality-2 ...
>
> when you run it manually:
>
> > raid0 personality registered
>
> then it correctly registers raid0. You'll definitely get rid of these
> problems if you compile RAID into the kernel (this is only a workaround),
> but these things supposed to work. I'm not sure yet whats going on.
>
> -- mingo
>
>
actually, im not sure if thats the only solution. last night i set up a system
with a raid5 array. i knew this problem would come up because i had raid5
compiled as a module. when i first booted, i noticed the kernel actually
trying to start the array twice, once during the autodetection phase, and once
again when fdisk tried to run. i aliased md-personality-4 (yes, i think it was
complaining about 4, not 5) to raid5 in /etc/conf.modules and rebooted. it
failed to start the array in the autodetection phase as expected, but when it
got around to fdisk'ing /dev/md0, the root partition had already been mounted,
hence it was able to find the module and start the array (kmod is **so** much
more reliable than kerneld ever was!). all was good from there.
i would reason that as long as the md device is not the root partition, and as
long as it is getting fsck'd from /etc/fstab, simply aliasing the personality
in /etc/conf.modules will solve the problem.
wrt to the seemingly wierd numbering of md-personality-#, modprobe -c lists
md-personality-1 as linear and 2 as raid0. logically, 3 would be raid1 and 4
would be raid5 since there isnt a separate raid4 module. i may be remembering
last night wrong though--it might have been complaining about not finding
md-personality-5 (after 12 hours in the office, the hallucinations tend to
get in the way).
