From owner-freebsd-questions@FreeBSD.ORG Fri Mar 30 16:09:15 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3DB8A16A405 for ; Fri, 30 Mar 2007 16:09:15 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.freebsd.org (Postfix) with ESMTP id 1417E13C43E for ; Fri, 30 Mar 2007 16:09:14 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from gumby.homeunix.com (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 24AD051941 for ; Fri, 30 Mar 2007 12:09:12 -0400 (EDT) Date: Fri, 30 Mar 2007 17:09:08 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20070330170908.120a69c1@gumby.homeunix.com> In-Reply-To: <460D1441.60904@dial.pipex.com> References: <14989d6e0703291420y1ed229dej7e2808a859f6efa6@mail.gmail.com> <14989d6e0703300200j670a46f3s6369d8132b76ba62@mail.gmail.com> <460D1441.60904@dial.pipex.com> X-Mailer: Claws Mail 2.8.1 (GTK+ 2.10.11; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: ad0: TIMEOUT - Is my disk dying? 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: Fri, 30 Mar 2007 16:09:15 -0000 On Fri, 30 Mar 2007 14:44:33 +0100 Alex Zbyslaw wrote: > Christian Walther wrote: > > >> > >> > > I'm seeing a lot of the following messages lately: > >> > > > >> > > Mar 29 21:02:01 pixie kernel: ad0: TIMEOUT - READ_DMA retrying > >> > > (1 retry left) LBA=13554983 > >> > > Mar 29 21:02:34 pixie kernel: ad0: TIMEOUT - READ_DMA retrying > >> > > (1 retry left) LBA=35376691 > >> > > Just thought I should point out that you can get errors like this if > your disk drive *cable* is faulty or has wiggled loose. > > I spent hours testing a 250Gb drive with manufacturer tools only to > solve the problem by replacing the SATA cable. I suspect the cable > was fine and had just wiggled loose. SATA may be thinner, but > they're still a bugger to route because they pull out so easily. > Even an IDE cable could have gone faulty or wiggled out; but in 15 > years that's never happened to me whereas I've seen 2 SATA cables > wiggle out in an untouched tower case in two years. This happened to me a couple of months ago, the problem went away after I reseated the SATA connectors.