From owner-freebsd-hardware Thu Nov 8 11:54:47 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from tartarus.telenet-ops.be (tartarus.telenet-ops.be [195.130.132.34]) by hub.freebsd.org (Postfix) with ESMTP id 5F40637B405 for ; Thu, 8 Nov 2001 11:54:46 -0800 (PST) Received: from alfa (D5E00941.kabel.telenet.be [213.224.9.65]) by tartarus.telenet-ops.be (Postfix) with ESMTP id 7AB8021772E; Thu, 8 Nov 2001 20:54:45 +0100 (CET) From: "Thomas Coppens" To: Cc: Subject: RE: Installing FreeBSD on a RAID0 array with onboard RAID Date: Thu, 8 Nov 2001 20:54:30 +0100 Message-ID: <004a01c1688f$314a00b0$0202a8c0@alfa> 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, Build 10.0.2627 In-Reply-To: <20011108111915.A18589@Odin.AC.HMC.Edu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > It is supposed to be supported (that's what the ar0 device is) though > it's a truly pointless feature. Even in Windows it doesn't even manage > to allow you to boot reliably in the face of drive failure because the > BIOS level support fails in many cases. A friend of mine had both disks > corrupted when one of them was pulled to test the failure recovery. Data reliability isn't the biggest issue here, speed is. This Promise chip is a cheap solution and critical files are stored on a server (backup). Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message