From owner-freebsd-bugs@FreeBSD.ORG Tue Jul 6 22:00:45 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 170BC16A4CF for ; Tue, 6 Jul 2004 22:00:44 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDE9F43D55 for ; Tue, 6 Jul 2004 22:00:44 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i66M0e8J070048 for ; Tue, 6 Jul 2004 22:00:40 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i66M0eO6070041; Tue, 6 Jul 2004 22:00:40 GMT (envelope-from gnats) Date: Tue, 6 Jul 2004 22:00:40 GMT Message-Id: <200407062200.i66M0eO6070041@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "Alexander Weisel" Subject: Re: kern/68313: Installing/Updating to Release 5.2.1 destroys RAID on Promise Controllers (i386, ACPI, SMP) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Alexander Weisel List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2004 22:00:45 -0000 The following reply was made to PR kern/68313; it has been noted by GNATS. From: "Alexander Weisel" To: Cc: Subject: Re: kern/68313: Installing/Updating to Release 5.2.1 destroys RAID on Promise Controllers (i386, ACPI, SMP) Date: Tue, 6 Jul 2004 22:00:32 -0000 Update: Took apart and reassembled every pice of my system to find the problem. Tried all combinations of disk combos on different controllers and found only this: one older drive was ATA REV 4, the other REV 5. Drives are on a different bus (ata1 , other drive ata2), both as slaves. Master drives are identical. Only in this configuration the error occurred. I replaced both drives and all is going well. On same cables, so this is not the prob this time :) Looks like a very mystic mirror, but most likely faulty and/or old hardware was the cause.