From owner-freebsd-stable@FreeBSD.ORG Wed Feb 18 15:23:03 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FF6016A4CF for ; Wed, 18 Feb 2004 15:23:03 -0800 (PST) Received: from sv07e.atm-tzs.kmjeuro.com (sv07e.atm-tzs.kmjeuro.com [193.81.94.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id A903643D1F for ; Wed, 18 Feb 2004 15:23:02 -0800 (PST) (envelope-from k.joch@kmjeuro.com) Received: from kmjeuro.com (adsl.sbg.kmjeuro.com [62.99.198.46]) (authenticated bits=0)i1INMfeB088937 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 19 Feb 2004 00:22:47 +0100 (CET) (envelope-from k.joch@kmjeuro.com) Message-ID: <4033F3C1.30101@kmjeuro.com> Date: Thu, 19 Feb 2004 00:22:41 +0100 From: "Karl M. Joch" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20040218190837.GA47526@dogma.freebsd-uk.eu.org> In-Reply-To: <20040218190837.GA47526@dogma.freebsd-uk.eu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: please visit www.ctseuro.com for further instructions. Protected by www.ctseuro.com X-MailScanner: Found to be clean Subject: Re: 'ad0: READ/WRITE command timeout' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2004 23:23:03 -0000 Jonathon McKitrick wrote: > I'm getting this error during heavy disk activity: > > ad0: READ command timeout > tag=0 serv=0 - resetting > ata0: resetting devices .. done > > This happens with READ and WRITE from time to time. Recently I saw: > > Falling back to PIO mode > and > Waiting for DRQ (IIRC) > > This sounds ominous. Is my drive on its last leg? > > > NOTE: Please CC me, as I am not currently subscribed. Thanks. > > jm I always change the harddisks when having errors like this. Mostly its the drive or the cable. And finally since a few days one server made big problems with the above error. Changing the drive, cables aso wasnt helpful. Found out it was the power supply which was buggy after 2 or 3 years :-(. New power supply and all errors are gone. -- Best regards / Mit freundlichen Gruessen, Karl M. Joch k.joch@ctseuro.com http://www.ctseuro.com