From owner-freebsd-questions Mon Aug 13 8:15:12 2001 Delivered-To: freebsd-questions@freebsd.org Received: from morpheus.mind.net (morpheus.mind.net [206.101.72.12]) by hub.freebsd.org (Postfix) with ESMTP id 3FEC537B407 for ; Mon, 13 Aug 2001 08:15:08 -0700 (PDT) (envelope-from jfox@morpheus.mind.net) Received: (from jfox@localhost) by morpheus.mind.net (8.11.3/8.11.3) id f7DFF0Z10600; Mon, 13 Aug 2001 08:15:00 -0700 (PDT) (envelope-from jfox) Date: Mon, 13 Aug 2001 08:15:00 -0700 From: John Fox To: freebsd-questions@freebsd.org Cc: fleisher@mind.net Subject: Hard read errors Message-ID: <20010813081459.A10559@mind.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i 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 Hello, Listers, I found this in the dmesg buffer on one of my servers: ad0: HARD READ ERROR blk# 3866393 status=59 error=10 ad0: HARD READ ERROR blk# 1518358 status=59 error=10 ad0: HARD READ ERROR blk# 1039006 status=59 error=10 ad0: HARD READ ERROR blk# 2050608 status=59 error=10 ad0: HARD READ ERROR blk# 3527216 status=59 error=10 ad0: HARD READ ERROR blk# 1892586 status=59 error=10 ad0: HARD READ ERROR blk# 2413168 status=59 error=10 A few questions: 1) Where can I find textual equivalents of the "status" and "error" codes? 2) How can I determine which slice these errors are coming from? (Does this question even make sense?) 3) Should I run fsck on each slice of ad0? Any other utility I should run? 4) What general advice can those of you with greater experience give me pertaining to this matter? Thanks, John -- John Fox System Administrator, InfoStructure, Ashland OR USA --------------------------------------------------------- "What is loved endures. And Babylon 5 ... Babylon 5 endures." --Delenn, "Rising Stars", Babylon 5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message