From owner-freebsd-questions Thu Jun 21 23:11:26 2001 Delivered-To: freebsd-questions@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 3CE2637B403 for ; Thu, 21 Jun 2001 23:11:22 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 326D06ACBC; Fri, 22 Jun 2001 15:41:19 +0930 (CST) Date: Fri, 22 Jun 2001 15:41:19 +0930 From: Greg Lehey To: "Paul A. Hoadley" Cc: freebsd-questions@freebsd.org Subject: Re: Does 'ad0: HARD READ ERROR' imply impending disk failure? Message-ID: <20010622154119.B25309@wantadilla.lemis.com> References: <20010622122059.S57186@wantadilla.lemis.com> <1201.10.0.0.3.993185274.squirrel@grover.logicsquad.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1201.10.0.0.3.993185274.squirrel@grover.logicsquad.net>; from paulh@logicsquad.net on Fri, Jun 22, 2001 at 02:17:54PM +0930 Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Friday, 22 June 2001 at 14:17:54 +0930, Paul A. Hoadley wrote: > > Greg Lehey wrote: > >> On Thursday, 21 June 2001 at 17:46:28 +0930, Paul A. Hoadley wrote: >> >>> Jun 21 16:35:42 grover /kernel: ad0: HARD READ ERROR blk# 13634000 >>> status=59 error=40 >>> Jun 21 16:35:46 grover /kernel: ad0: HARD READ ERROR blk# 13634000 >>> status=59 error=40 >> >> This message is pretty specific. It comes from the disk, not the IDE >> controller, so you can assume that it's really a disk problem. It's >> possible that a low-level format could recover something, though. > > Thanks for the answer. I'm going to bite the bullet and buy a new disk. > In an attempt to salavge the current one, would you recommend a low level > format over trying badsect(8)? Yes. A low-level format rewrites the entire disk, including the parts of the sector not accessible to the controller, such as the ID fields. I don't recognize the status code there, but it could be that that is what is defective. Of course, depending on the problem, you might find that the surface is still not readable, and in that case badsect(8) might help. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message