Problem with FastTrak S150 SX4-M

[ctodd at chrismiller.com]

Dave,
	one last note. Be sure to copy your dmesg output when modifying
the controller mode and driver as this may indicate how the chip presents
itself to the kernel and provide hints if a patch is needed.

Chris

On Wed, 26 Jan 2005 ctodd at chrismiller.com wrote:

>
> On Wed, 26 Jan 2005, Dave Myron wrote:
>
> > It's not red but it is the PRI_RAID IDE connector. I have the controller set
> > to IDE in the BIOS so it should act just as any other IDE controller
> > (according to the manual and many other sources).
>
> True, but you know how that goes.
>
> > I have two hard drives on the primary IDE (not on the controller) and a CD
> > drive on the secondary IDE (also not on the controller). Then I have two
> > more hard drives on the PRI_RAID channel (which *is* the P-ATA channel on
> > the controller). Those two drives are getting the failure (or at least one
> > is - see the error messages in my original text).
> >
> > I wish I had an S-ATA drive to test with so that I could verify that it's a
> > problem with the P-ATA part of this controller.
> >
> > Any more ideas?
>
> Did you try leaving the Promise controller (in IDE mode) enabled and
> disconnecting the drives? What about setting the controller into raid mode
> with or without the drives attached? Obviously don't do anything that
> would cause any data loss on those drives (i.e. init the raid array).
>
> Sounds like something to do with Promise in the IDE mode. Perhaps the
> kernel is detecting the chip and assuming raid is enabled. You could also
> try disabling the ar driver in the kernel for grins, then perhaps the chip
> will just show up as an IDE controller.
>
> I'm suspect the SATA raid functions work fine, but I believe the
> controller also supports a non raid mode for SATA drives, unfortunately I
> don't have a spare to test this.
>
> In any event report back what you find so the driver can be fixed if
> it seems to be the problem.
>
> Chris
>