From owner-freebsd-stable Sat Jun 30 20:30:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mikea.ath.cx (okc-65-26-223-53.mmcable.com [65.26.223.53]) by hub.freebsd.org (Postfix) with ESMTP id 32B6937B407 for ; Sat, 30 Jun 2001 20:30:17 -0700 (PDT) (envelope-from mikea@mikea.ath.cx) Received: (from mikea@localhost) by mikea.ath.cx (8.11.4/8.11.1) id f613TnE86913; Sat, 30 Jun 2001 22:29:49 -0500 (CDT) (envelope-from mikea) Date: Sat, 30 Jun 2001 22:29:48 -0500 From: mikea To: Josh Elsasser Cc: freebsd-stable@FreeBSD.ORG Subject: Re: your mail Message-ID: <20010630222948.A86894@mikea.ath.cx> References: <20010630142808.R70078-100000@jade.elsasser.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20010630142808.R70078-100000@jade.elsasser.org>; from josh@slack.nu on Sat, Jun 30, 2001 at 11:03:01PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Jun 30, 2001 at 11:03:01PM -0400, Josh Elsasser wrote: > I have an extra ata disk called ad2 (my two main disks are scsi), and > I woke up this morning to these messages on my console: > > ad2: READ command timeout tag=0 serv=0 - resetting > ata1: resetting devices .. ata1-slave: timeout waiting for command=ef > s=01 e=04 > done > ad2s1e: soft (ECC corrected) reading fsbn 4255 of 2096-2097 (ad2s1 bn > 4255; cn 4 tn 3 sn 34)ad2s1e: hard error reading fsbn 4255 of > 2096-2097 (ad2s1 bn 4255; cn 4 tn 3 sn 34) status=7f error=7f > > Now anything attempting to access ad2 freezes, and not even a kill -9 > will kill it. I'm guessing that rebooting the machine will "fix" this > problem (for now at least), but I'm hoping for a better solution. > > Here is my uname -a: FreeBSD jade 4.3-STABLE FreeBSD 4.3-STABLE #16: > Fri Jun 15 17:01:28 EDT 2001 joshe@jade:/usr/src/sys/compile/JADE i386 > > Has anyone come across this before? Any help would be appreciated. > Also, please replay to josh@slack.nu as I am not subscribed to this > list. "It's dead, Jim." I hope you had a good recent backup of that disk; you're about to get to use it. Soft and hard errors reading a disk, and especially a system hang when trying to read a disk, indicate serious disk problems or a failure. In your case, I'd say it was a failure. -- Mike Andrews mikea@mikea.ath.cx Tired old sysadmin since 1964 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message