Yeah, that was my though. I left sectors free at the front, but that
wasn't it.
Soren was looking at seeing if there was some way to read the promise
label/record keeping, and turn that into a vinum setup somehow, so it
would be relatively transparent. But I don't think he could get the docs
from Promise, or perhaps just got busy.
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
c: 80041248 0 unused 0 0 # (Cyl. 0 -
79405)
d: 80040224 1024 vinum # (Cyl. 1*-
79405*)
On Fri, 2 Jun 2000, Greg Lehey wrote:
> On Thursday, 1 June 2000 at 23:56:44 -0700, Jaye Mathisen wrote:
> >
> > I have 2 maxtor 40GB's running off a Promise FastTrak 66 under 4.0-stable,
> > and it's working fine, except for one teensy problem.
> >
> > vinum (striping them), apparently overwrote whatever the promise uses to
> > track them as part of a stripe set... So on reboot, I have to hit an F2
> > configure, because the promise thinks the array is unconfigured...
>
> Interesting. Can you find out where the controller keeps its config?
> You probably would have been OK if you had left some space free at the
> beginning or the end of the drive. That's probably worth a word of
> warning somewhere.
>
> Greg
> --
> Finger [EMAIL PROTECTED] for PGP public key
> See complete headers for address and phone numbers
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
