[RE]Promise FastTrak66 - dmraid doesn't recognize striped array on pair of Maxto
mauelshagen at redhat.com
Thu Apr 19 09:17:19 UTC 2007
both offsets added.
If this offset story turns out to be ongoing, I need to address
this by a flexible algorithm for pdc metadata discovery...
On Mon, Apr 16, 2007 at 10:13:50AM -0400, Woody Suwalski wrote:
> Bob Stewart wrote:
> >--- James Olson <big_spender12 at lycos.com> wrote:
> > Hi Bob,
> >I ran into a similar problem with the same controller on certain older
> >drives. The problem has to do with the way the fasttrak bios sees the
> >drive size and
> >geometry as opposed to the way linux sees it as reported by the old drive's
> >firmware. Normally the drive metadata sector is located on the last
> >of the drive, about 63 sectors before the end. Anyway you can probably
> >get it
> >to work if you look through the data on your drive to find out what sector
> >metadata is on, and then modify the dmraid source (pdc.c?) to add it to the
> >list of sector offsets from the end of the disk to try.
> > -James
> >This was actually pretty easy to do. May I suggest the following change to
> >pdc.h? Seems like there should be some rhyme or reason for the offset,
> > Or is it just dependent on the model and revision of the controller?
> > This is
> >a "hacked" Utra66 controller with BIOS V1.30.
> >#define PDC_CONFIGOFFSETS 63,255,256,16,399,735
> >#define PDC_CONFIGOFFSETS 63,255,256,16,399,735,675
> Actually we have found yet another PDC location=991:
> #define PDC_CONFIGOFFSETS 63,255,256,16,399,735,675,991
> I think I have sent Heinz a patch for this, however it somehow got lost?
> Anyway, thanks for the 675...
> Woody, Xandros
> Ataraid-list mailing list
> Ataraid-list at redhat.com
Heinz Mauelshagen Red Hat GmbH
Consulting Development Engineer Am Sonnenhang 11
Storage Development 56242 Marienrachdorf
Mauelshagen at RedHat.com PHONE +49 171 7803392
FAX +49 2626 924446
More information about the Ataraid-list