From owner-freebsd-hardware Wed Feb 12 21:09:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA18422 for hardware-outgoing; Wed, 12 Feb 1997 21:09:55 -0800 (PST) Received: from cold.org (cold.org [206.81.134.103]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA18416 for ; Wed, 12 Feb 1997 21:09:52 -0800 (PST) Received: from localhost (brandon@localhost) by cold.org (8.8.5/8.8.3) with SMTP id WAA00958; Wed, 12 Feb 1997 22:09:30 -0700 (MST) Date: Wed, 12 Feb 1997 22:09:29 -0700 (MST) From: Brandon Gillespie To: Mike Kerr cc: freebsd-hardware@freebsd.org Subject: Re: HD Problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Anybody have any idea what the following error messages can be attributed > to, and/or what I can do to fix the problem? > > wd0s2f: soft error reading fsbn 1246379 of 1246256-1246383 (wd0s2 bn > 1461547; cn 362 tn 31 sn 10)wd0: status 58 error 40 > wd0s2f: hard error reading fsbn 1247051 of 1247024-1247151 (wd0s2 bn > 1462219; cn 362 tn 41 sn 52)wd0: status 59 error > 40 > wd0s2f: hard error reading fsbn 1247051 of 1247040-1247055 (wd0s2 bn > 1462219; cn 362 tn 41 sn 52)wd0: status 59 error > 40 Its dead Jim. Seriously tho, your hard drive is having hardware problems. This can be anything from grown bad sectors to a servo malfunction. Contact the drive manufacturer, they usually have some diagnostic software you can run to tell for sure (for instance, if its a western digital drive you can run WDDIAG which is available on their web site, and it'll give you all of the gritty details--they also have software to fix grown sector errors). -Brandon Gillespie