On Tue, Apr 10, 2001 at 05:31:00PM +0200, [EMAIL PROTECTED] wrote:
>
>
> Hi Ulf, Jim,
>
> thanks for the replies so far.
>
> Ulf wrote:
>
> > I had the same problem with autodetect. It seems that they turned of the
> > partitition detection mode in favor of a kernel command line. Look for
> > ./linux/Documentation/md.txt
> > Its something like md=<dev.nr>,<raidlevel>,<dev1>,<dev2>,<dev3>,...
> > for new kernel.
>
> The md= ... kernel command line did not do the trick for me.
>
> I tried some more and made the following observations:
>
> The RAID-1 array is autodetected fine with my low-level SCSI
> drivers (aic7xxx and qlogicfc) and the RAID drivers compiled
> into the kernel. But this is not the way I want to go. It
> messes up the rest of the system.
>
> With the low level drivers scsi loaded as modules via initrd
> the autodetection fails, with or without kernel command line.
>
> Any ideas?
I think you need to arrange for raidstart to be invoked once
the scsi driver modules are loaded. The raid s/w only does its
autodetect if it is compiled in to the kernel, and does it only at
boot time, so if the scsi drivers are not present at the time, the
raid s/w wont find and start your arrays. raidstart needs to see
/etc/raidtab, which might be a problem if you are starting from
an initrd. In that case, if the raid s/w is compiled in, you can
do an ioctl() to the raid code to trigger it to do autostart once
the scsi drivers are loaded.
That is based on my interpretation of 2.4.3 kernel source, and some
experimentation, but may not be 100% accurate.
Richard
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
