From owner-freebsd-questions@FreeBSD.ORG Fri Mar 30 13:44:36 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 1ABC416A403 for ; Fri, 30 Mar 2007 13:44:36 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by mx1.freebsd.org (Postfix) with ESMTP id D3AF213C4D1 for ; Fri, 30 Mar 2007 13:44:35 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.137] (helo=anti-virus01-08) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1HXHP8-000442-U5; Fri, 30 Mar 2007 14:44:34 +0100 Received: from [62.31.10.181] (helo=[192.168.0.2]) by asmtp-out4.blueyonder.co.uk with esmtp (Exim 4.52) id 1HXHP7-0000yf-59; Fri, 30 Mar 2007 14:44:33 +0100 Message-ID: <460D1441.60904@dial.pipex.com> Date: Fri, 30 Mar 2007 14:44:33 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20061205 X-Accept-Language: en MIME-Version: 1.0 To: Christian Walther References: <14989d6e0703291420y1ed229dej7e2808a859f6efa6@mail.gmail.com> <14989d6e0703300200j670a46f3s6369d8132b76ba62@mail.gmail.com> In-Reply-To: <14989d6e0703300200j670a46f3s6369d8132b76ba62@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Users Questions 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 13:44:36 -0000 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. --Alex