From owner-freebsd-questions@FreeBSD.ORG Sat Feb 16 17:28:21 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 EEF9B16A419 for ; Sat, 16 Feb 2008 17:28:21 +0000 (UTC) (envelope-from lavalamp@spiritual-machines.org) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 98EEF13C458 for ; Sat, 16 Feb 2008 17:28:21 +0000 (UTC) (envelope-from lavalamp@spiritual-machines.org) Received: from [172.16.156.151] (pool-71-182-130-225.pitbpa.fios.verizon.net [71.182.130.225]) (AUTH: LOGIN seklecki, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Sat, 16 Feb 2008 12:28:20 -0500 id 00056407.47B71D34.000064C1 From: "Brian A. Seklecki" To: Peter Boosten In-Reply-To: <47B71686.7000906@boosten.org> References: <47B71686.7000906@boosten.org> Date: Sat, 16 Feb 2008 12:28:18 -0500 Message-Id: <1203182898.3213.2.camel@new-host.l33tsdal3.biz> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Evolution 2.12.3 (2.12.3-1.fc8) Cc: FreeBSD Questions Subject: Re: disk error 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: Sat, 16 Feb 2008 17:28:22 -0000 On Sat, 2008-02-16 at 17:59 +0100, Peter Boosten wrote: > Hi all, > > Just found these messages in my logfile. Is it something to worry about? > I've never seen them before upgrading to 6.3. > > ra kernel: ad0: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=281550271 > ra kernel: ad0: FAILURE - READ_DMA48 status=51 > error=4 LBA=281550271 Yea -- normally that means a bad sector(*), and where there's one, there's bound to be more. Failed drive eventually. I would pull this server from rotation and run a full surface sector scan on it (download an ISO of "Hiran's Boot CD") Or if its a geom mirror raid-1, test this component. If it was scsi, I would recommend camcontrol(8) to query the disk for a list of grown defect sectors. ~BAS *. If you've never seen it before and it developed. Bad cables/controllers/drives/interference can cause it too, but you would have seen it from inception. > ra kernel: g_vfs_done():ad0s1f[READ(offset=138248126464, > length=16384)]error = 5 > ra kernel: handle_workitem_freeblocks: block count > ra kernel: handle_workitem_freeblks: got error 5 while accessing filesystem > > Peter