From owner-freebsd-current@FreeBSD.ORG Wed May 12 05:45:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E42B16A4CE for ; Wed, 12 May 2004 05:45:36 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id C92A343D39 for ; Wed, 12 May 2004 05:45:35 -0700 (PDT) (envelope-from sos@DeepCore.dk) Received: from DeepCore.dk (sos.deepcore.dk [194.192.25.130]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i4CCjG7s034130; Wed, 12 May 2004 14:45:21 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <40A21C5C.8080800@DeepCore.dk> Date: Wed, 12 May 2004 14:45:16 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.5 (X11/20040329) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Drew Broadley References: <20040512145212.62e7db1e@it.buh.cameradicommercio.ro> <40A21204.7070806@corrupt.co.nz> In-Reply-To: <40A21204.7070806@corrupt.co.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: Ion-Mihai Tetcu cc: freebsd-current@freebsd.org Subject: Re: ad0: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=21267353 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 12:45:36 -0000 Drew Broadley wrote: > I am getting a slightly similar error but on the other end, (READ) > > May 11 13:01:34 taz kernel: ad0: FAILURE - READ_DMA > status=51 error=40 LBA=4818191 > > Is this possibly a result of a bad hdd sector ? This is not semilar :) this is a genuine bad sector on the disk. You could try to write to that sector and hope it gets remapped by the drive. If more shows up (try smartctl to get SMART status of the drive) it might be time to backup :) -- -Søren