On Wed, Feb 01, 2006 at 08:45:42AM -0500, Peter wrote:
> --- Ho?=kan Olsson <[EMAIL PROTECTED]> wrote:
>
> > On 1 feb 2006, at 08.38, Jurjen Oskam wrote:
> >
> > > On Wed, Feb 01, 2006 at 01:19:58AM -0500, Peter wrote:
> > >
> > >> raid0: Device already configured!
> > >> "ioctl (RAIDFRAME_CONFIGURE) failed"
> > >>
> > >> Can anyone lend a hand in this important matter?
> > >
> > > Let me guess (since you didn't post any configuration): you
> > > enabled RAID-autoconfiguration by the kernel *and* you
> > > configure the same RAID-device during the boot sequence using
> > > raidctl?
> >
> > /etc/rc includes commands to configure the raid devices, and if
> > they've been setup to use autoconfiguration then this is indeed what
> > happens. Expected and nothing to worry about, although noisy. For my
> > raidframe devices, I just removed the autoconfigure flag.
>
> Oh that's a relief. Yes, now I see in /etc/rc the raid commands. So I
> should leave everything as is?
You should probably disable either /etc/raid0.conf or the autodetection.
The former is most easily achieved by mv
/etc/raid0.conf{,.autodetected}; the latter is achieved by either not
compiling with the option RAID_AUTOCONFIG, or running raidctl -A no
raid0.
> Side question:
> I tried unsuccessfully using the same procedure to set up two disks (sd0
> and sd1) attached to a QLogic FibreChannel controller (isp driver). I
> probably don't have the correct terminology but upon startup the boot code
> could not be found (would not get beyond the point where the kernel
> usually kicks in). I'm wondering whether RAIDframe has limitations with
> this hardware.
I don't know anything about this card, but the isp(4) man page seems to
suggest that adding ISP_COMPILE_FW to the kernel configuration may be
helpful.
This should not be relevant to RAIDframe operation, though - does it
work without RAIDframe?
Please note that RAIDframe is software RAID - hardware RAID is handled
differently.
Joachim
