From owner-freebsd-stable@FreeBSD.ORG Sun Jul 4 07:17:09 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98D3316A4CE for ; Sun, 4 Jul 2004 07:17:09 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5484043D1F for ; Sun, 4 Jul 2004 07:17:09 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by cs1.cs.huji.ac.il with esmtp id 1Bh1FM-0000vh-AA; Sun, 04 Jul 2004 10:17:08 +0300 X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: "Derkjan de Haan" In-reply-to: Your message of Sun, 4 Jul 2004 08:46:38 +0200 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Jul 2004 10:17:08 +0300 From: Danny Braniss Message-Id: <20040704071709.5484043D1F@mx1.FreeBSD.org> cc: freebsd-stable@freebsd.org Subject: Re: problems with RAID0 and Intel/SE7501WV2/Promise X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jul 2004 07:17:09 -0000 > > ----- Original Message ----- > From: "Doug White" > To: "Danny Braniss" > Cc: ; "Soren Schmidt" > Sent: Sunday, July 04, 2004 4:45 AM > Subject: Re: problems with RAID0 and Intel/SE7501WV2/Promise > > > > OK, so you used the ATA controller's menu to construct the RAID array, > > then used sysinstall to slice the ensuing volume. Hm. It appears that > > writes to sector 0 are disallowed. Can you try installing without the > > array defined, to make sure the disks are writable otherwise? > > Can this be some kind of virus protection (against boot sector viruses) > setting in the system bios ? Some systems have this, and activate it when > doing a 'load setup defaults'. Don't know if this applies to RAID arrays > though. > i doubt it, since the program/kernel had INHO no reason to write there in the first place. danny