From owner-freebsd-questions@FreeBSD.ORG Tue Oct 28 11:04:53 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C63731065673; Tue, 28 Oct 2008 11:04:53 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id E9B068FC1B; Tue, 28 Oct 2008 11:04:52 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.3/8.14.2) with ESMTP id m9SB4ntr003414; Tue, 28 Oct 2008 12:04:49 +0100 (CET) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.3/8.14.2/Submit) with ESMTP id m9SB4nSb003411; Tue, 28 Oct 2008 12:04:49 +0100 (CET) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Tue, 28 Oct 2008 12:04:49 +0100 (CET) From: Wojciech Puchar To: Jeremy Chadwick In-Reply-To: <20081028024143.GA37131@icarus.home.lan> Message-ID: <20081028120407.G3326@wojtek.tensor.gdynia.pl> References: <49067148.6080307@telus.net> <20081028024143.GA37131@icarus.home.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Carl Voth , freebsd-questions@freebsd.org Subject: Re: gmirror slice insertion, "FAILURE - READ_DMA status=51" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2008 11:04:53 -0000 >> error=40 LBA=134802751 > > Are you sure you don't have a bad hard disk? This looks to be like a > classic block/sector failure. This does not appear to be the infamous > famous "DMA timeout" problem, especially if this is the only error > you're getting. he can temporarity boot with hw.ata.ata_dma=0 but i think his drive failed. > >> I reinstalled FB7 to ad4, redid the /boot.config modification to make >> ad6/gm0 bootable again and retried the insertion of ad4 into gm0. Exact >> same error messages at exactly the same point with same consequences. so IT IS FAILED drive!