From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 15 14:10:59 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42AA316A4CE for ; Fri, 15 Apr 2005 14:10:59 +0000 (GMT) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41E4D43D54 for ; Fri, 15 Apr 2005 14:10:58 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.12.11/8.13.1) with ESMTP id j3FEArj4097160 for ; Fri, 15 Apr 2005 10:10:53 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.12.11/8.13.1/Submit) id j3FEAqLp097159 for freebsd-hackers@freebsd.org; Fri, 15 Apr 2005 10:10:52 -0400 (EDT) (envelope-from bv) Date: Fri, 15 Apr 2005 10:10:52 -0400 From: Bill Vermillion To: freebsd-hackers@freebsd.org Message-ID: <20050415141052.GB96815@wjv.com> References: <20050415120104.AD04C16A4CF@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050415120104.AD04C16A4CF@hub.freebsd.org> Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.6i X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on bilver.wjv.com Subject: Re: immenent disk failure ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: bv@wjv.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2005 14:10:59 -0000 On or about Fri, Apr 15, 2005 at 12:01 , while attempting a Zarathustra emulation freebsd-hackers-request@freebsd.org thus spake: > Message: 4 > Date: Thu, 14 Apr 2005 10:58:02 -0500 (CDT) > From: "H. S." > Subject: imminent disk failure ? ... > I have a server running 4.X for almost two years now, without > problems - rock solid as it should be - yesterday the server > became unresponsive, now that I have access again, and while > checking the logs, I found this as the last message before the > unresponsiveness: > /kernel: ad0: READ command timeout tag=0 serv=0 - resetting > The next message is the system getting back on, 1hour later. > I have not changed anything kernel-related on this system for > a long time (jul 2004), just apply the occasional kernel patch > and rebuild/reboot the system. I never encountered this problem > before. Could this message mean this disk is giving its last > breaths ? It might help if we knew a bit more about the system such a drive make and model - you can see that in dmesg. That may point out some device that is known to be problematic. The last time I got timeout errors like that was in the 3.x era with a SCSI controller. Last IDE problem I had was a bad read that force the system into PIO mode with over 75% performance decrease. The only way around that one that I was aware of was a reboot. Bill -- Bill Vermillion - bv @ wjv . com