Date: Mon, 4 Sep 2000 12:39:43 -0500 From: "Brandon DeYoung" <brandon@schoolpeople.net> To: "Brandon S. DeYoung" <brandon@schoolpeople.net>, "Mike Smith" <msmith@FreeBSD.ORG> Cc: <freebsd-hardware@FreeBSD.ORG> Subject: Re: Problems installing 4.1 on 3ware RAID 5200 & 6200 Message-ID: <003101c01697$1ccacf20$4702a8c0@schoolpeople.net> References: <200009040134.SAA01957@mass.osd.bsdi.com> <005e01c01675$68d13660$9e0e1b18@austin.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks Mike,
I rebooted before it was done profiling and this allowed the OS to
install. Also that "INIT Array (after F8)" is gone from the boot message.
And it only took a few minutes to do newfs as opposed to over an hour.
Now on to the next problem. When setting it up this way the controller
is unable to "verify" the array (from the "Maintain Array" menu). I tried
testing the fault tolerance, by unplugging one of the drives while the
system was off. It came back up in degraded mode alright, but I have been
unable to get the array to rebuild. Right now I'm getting this message from
the controller during boot:
3ware Storage Controller BIOS BEXX 1.03.00.019
Array Unit 0 - Mirror 30.6 GB Rebuilding (after F8)
Port 0 - ST330630A 30.6 GB
Port 1 - ST330630A 30.6 GB
I've tried rebuilding the degraded array both with new (identical) hard
drives as well as with the one I unplugged, so far no luck. I'm trying again
with a fresh drive and I stopped the OS from loading in case it's a similar
issue. I don't really hear much disk activity but it might be doing
something. I'll let it sit over night, just in case. Think there's any
chance I got one of those "southern hemisphere" controllers and don't have
my box properly oriented?
~B
----- Original Message -----
From: "Brandon S. DeYoung" <brandon@schoolpeople.net>
To: "Mike Smith" <msmith@FreeBSD.ORG>
Cc: <freebsd-hardware@FreeBSD.ORG>
Sent: Monday, September 04, 2000 8:38 AM
Subject: Re: Problems installing 4.1 on 3ware RAID 5200 & 6200
> Mike Smith <msmith@FreeBSD.ORG> wrote:
>
>
> >1) When the 3ware BIOS is running the 'profiling' phase, reboot the
> > machine. This *may* result in slightly lower performance.
> >2) Let the FreeBSD installer start but do nothing until all the drives
> > are idle. This may take a long time. It appears that the array
> > enters an "initialisation" phase if profiling is allowed to complete,
> > and while this phase is active, the driver can upset the controller.
>
> Thanks Mike,
> Just so I'm clear here.
> 1) When you say profiling, you're talking about the initial array set up
> done after pushing Alt-3? And you're suggesting rebooting the machine
before
> it gets to 100%?
> 2) Allow profiling to complete, but leave the installer on the first
screen
> ("skip kernel configuration.....") until drives are idle.
>
> Best Regards,
> ~Brandon
>
> ...It don't mean a thing
> If you cain't get that ping...
>
> Brandon S. DeYoung
> Senior Engineer
> SchoolPeople
> brandon@schoolpeople.net
>
>
> ----- Original Message -----
> From: "Mike Smith" <msmith@FreeBSD.ORG>
> To: "Brandon DeYoung" <brandon@schoolpeople.net>
> Cc: <freebsd-hardware@FreeBSD.ORG>
> Sent: Sunday, September 03, 2000 8:34 PM
> Subject: Re: Problems installing 4.1 on 3ware RAID 5200 & 6200
>
>
> > > Hello all,
> > > ...I must be doing something wrong.
> > > I've been trying to get a new FreeBSD 4.1 (Release) system up using
the
> > > 3ware 5200 ATA RAID controller for the past few days. In short the
> install
> > > exists after "Extracting manpages into / directory" with the following
> > > error:
> >
> > This appears to be a bad interaction between the driver and the
> > controller; I'm still working on it, but in the meantime you can do one
> > of two things:
> >
> > 1) When the 3ware BIOS is running the 'profiling' phase, reboot the
> > machine. This *may* result in slightly lower performance.
> > 2) Let the FreeBSD installer start but do nothing until all the drives
> > are idle. This may take a long time. It appears that the array
> > enters an "initialisation" phase if profiling is allowed to
complete,
> > and while this phase is active, the driver can upset the controller.
> >
> > Regards,
> >
> >
> > --
> > ... every activity meets with opposition, everyone who acts has his
> > rivals and unfortunately opponents also. But not because people want
> > to be opponents, rather because the tasks and relationships force
> > people to take different points of view. [Dr. Fritz Todt]
> >
> >
> >
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hardware" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003101c01697$1ccacf20$4702a8c0>