Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Sep 1999 09:00:21 +1200 (NZST)
From:      Jonathan Chen <jonc@logisticsoftware.co.nz>
To:        Michael Kennett <mike@laurasia.com.au>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: hard error reading fsbn...
Message-ID:  <Pine.SC5.4.10.9909280858450.26691-100000@kiwi.logisticsoftware.co.nz>
In-Reply-To: <199909270849.QAA29456@laurasia.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 27 Sep 1999, Michael Kennett wrote:

> 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 <rdy, seekdone, drq, error> error 40 <uncorr>
> 
> 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.

Toss it. Don't wait until your file-system tries to allocate those
bad areas on your disk.

Jonathan Chen
--------------------------------------------------------------------
The Internet: an empirical test of the idea that a million monkeys
              banging on a million keyboards can produce Shakespeare



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SC5.4.10.9909280858450.26691-100000>