From owner-freebsd-isp Thu Jun 21 16:58:56 2001 Delivered-To: freebsd-isp@freebsd.org Received: from psknet.com (voyager.psknet.com [63.171.251.15]) by hub.freebsd.org (Postfix) with SMTP id 5BC5737B401 for ; Thu, 21 Jun 2001 16:58:51 -0700 (PDT) (envelope-from troy@psknet.com) Received: (qmail 5636 invoked by uid 85); 21 Jun 2001 23:58:43 -0000 Received: from troy@psknet.com by voyager.psknet.com with qmail-scanner-0.95 (uvscan: v4.1.20/v4143. . Clean. Processed in 0.208141 secs); 21 Jun 2001 23:58:43 -0000 X-Qmail-Scanner-Mail-From: troy@psknet.com via voyager.psknet.com X-Qmail-Scanner-Rcpt-To: freebsd-isp@freebsd.org X-Qmail-Scanner: 0.95 (No viruses found. Processed in 0.208141 secs) Received: from arcadia.psknet.com (HELO arcadia) (63.171.251.7) by voyager.psknet.com with SMTP; 21 Jun 2001 23:58:43 -0000 From: "Troy Settle" To: Subject: RE: RAID/vinum options (mail server) Date: Thu, 21 Jun 2001 19:58:49 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Took somewhere between 2 and 3 hours. Guess the AMI cards are a good bet, even if we don't have tools from the OS to monitor/manage them. -- Troy Settle Pulaski Networks 540.994.4254 http://www.psknet.com ** -----Original Message----- ** From: owner-freebsd-isp@FreeBSD.ORG ** [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of Troy Settle ** Sent: Thursday, June 21, 2001 1:22 PM ** To: Forrest W. Christian ** Cc: freebsd-isp@freebsd.org ** Subject: RE: RAID/vinum options (mail server) ** ** ** ** As requested, here's an update. ** ** Airborne just dropped off the replacement drive, I screwed it into the ** caddy, inserted, turned the key to lock the caddy in, and after ** spinning up, ** the AMI Express 200 (series 466) started automatically ** rebuilding the array. ** ** Will let y'all know when it's done to see how long it takes ** (4x18gb, RAID5, ** 16MB ram on the controller). ** ** -- ** Troy Settle ** Pulaski Networks ** 540.994.4254 ** http://www.psknet.com ** ** ** ** -----Original Message----- ** ** From: owner-freebsd-isp@FreeBSD.ORG ** ** [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of Forrest W. ** Christian ** ** Sent: Wednesday, June 20, 2001 5:13 PM ** ** To: Troy Settle ** ** Cc: freebsd-isp@freebsd.org ** ** Subject: RE: RAID/vinum options (mail server) ** ** ** ** ** ** On Wed, 20 Jun 2001, Troy Settle wrote: ** ** ** ** > I just had a drive fail on me today. I'm using an AMI ** Expres 200 (466) ** ** > controller, and while the alarm drove me nutz for a while ** until I could ** ** > silence it, I was able to pull the bad drive, and the array is still ** ** > trucking right along. ** ** > ** ** > If you like, I'll post an update when I get the new drive ** ** installed and the ** ** > array repaired. ** ** ** ** Please do. This looks like an interesting option. ** ** ** ** Just curious, how do you manage these in the FreeBSD context? ** ** ** ** - Forrest W. Christian (forrestc@imach.com) AC7DE ** ** ---------------------------------------------------------------------- ** ** The Innovation Machine Ltd. P.O. Box 5749 ** ** http://www.imach.com/ Helena, MT 59604 ** ** Home of PacketFlux Technogies and BackupDNS.com (406)-442-6648 ** ** ---------------------------------------------------------------------- ** ** Protect your personal freedoms - visit http://www.lp.org/ ** ** ** ** ** ** To Unsubscribe: send mail to majordomo@FreeBSD.org ** ** with "unsubscribe freebsd-isp" in the body of the message ** ** ** ** ** ** ** To Unsubscribe: send mail to majordomo@FreeBSD.org ** with "unsubscribe freebsd-isp" in the body of the message ** ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message