From owner-freebsd-questions Mon Sep 27 1:49:59 1999 Delivered-To: freebsd-questions@freebsd.org Received: from laurasia.com.au (lauras.lnk.telstra.net [139.130.93.142]) by hub.freebsd.org (Postfix) with ESMTP id 6878C14BF3 for ; Mon, 27 Sep 1999 01:49:55 -0700 (PDT) (envelope-from mike@laurasia.com.au) Received: (from mike@localhost) by laurasia.com.au (8.9.3/8.9.3) id QAA29456 for freebsd-questions@freebsd.org; Mon, 27 Sep 1999 16:49:54 +0800 (WST) (envelope-from mike) From: Michael Kennett Message-Id: <199909270849.QAA29456@laurasia.com.au> Subject: hard error reading fsbn... To: freebsd-questions@freebsd.org Date: Mon, 27 Sep 1999 16:49:53 +0800 (WST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, I recently had a filesystem (unfortunately /) fail, with a number of kernel error messages logged as follows: wd0s1a: hard error reading fsbb 196734 (wd0s1 bn 1976734; cn 12 tr 62; sn 48) (status 59 error 40 I was able to recover the filesystem without any major loss, and I've been testing the drive extensively since. It has not failed again, but I'm left with a quesy feeling about using this drive on a production machine. I'd be interested in knowing peoples opinion on the stability of the drive, and whether it should be scrapped (ie. used on a linux machine :-) or not. Notes: The /var/log/messages file has since been rotated, and I've lost the exact kernel message. The above text has been recreated from my (paper) notes. The failure occured during a 'make installworld' of -current, and I'll admit to a bad freebsd-karma day :-) However, to the best of knowledge the failure was *not* due to changes in -current. Regards, Mike Kennett (mike@laurasia.com.au) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message