From owner-freebsd-current@FreeBSD.ORG Fri Nov 7 11:07:22 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09B4E16A4CE for ; Fri, 7 Nov 2003 11:07:22 -0800 (PST) Received: from mail.speakeasy.net (mail8.speakeasy.net [216.254.0.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CD8843FD7 for ; Fri, 7 Nov 2003 11:07:18 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 16037 invoked from network); 7 Nov 2003 19:07:18 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 7 Nov 2003 19:07:18 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id hA7J6sce095507; Fri, 7 Nov 2003 14:06:54 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20031107181007.GA19911@rot13.obsecurity.org> Date: Fri, 07 Nov 2003 14:06:54 -0500 (EST) From: John Baldwin To: Kris Kennaway X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: re@FreeBSD.org cc: current@FreeBSD.org cc: sos@FreeBSD.org Subject: RE: Too many uncorrectable read errors with atang X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 19:07:22 -0000 On 07-Nov-2003 Kris Kennaway wrote: > So far this has happened (well, the panic above was new) on 5 separate > machines that were all working on older -current. Now, these are all > IBM DeathStar drives, but previously I was only experiencing ata > errors every month or two, and they were correctable for another month > or two by /dev/zero'ing the drive. > > To suddenly start receiving errors on 5 out of 7 drives in the past > few weeks is a significant anomaly. Perhaps one of the following is > happening: > > 1) All my drives have performed mass suicide at once > > 2) ATAng is detecting errors that the ATAog did not > > 3) ATAng is not trying as hard as ATAog to recover from the errors > from the crappy drives > > 4) ATAng has a bug on this hardware. 5) Interference from abnormally high solar activity. It is known to cause an increase in NMI's from ECC errors, so it could be a possible explanation here even if it's a bit far-fetched. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/