From owner-freebsd-questions Thu Nov 23 3:57:27 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.thpoon.com (cr103675-a.bloor1.on.wave.home.com [24.114.152.71]) by hub.freebsd.org (Postfix) with SMTP id DBF1537B4CF for ; Thu, 23 Nov 2000 03:57:24 -0800 (PST) Received: (qmail 3393 invoked from network); 23 Nov 2000 11:57:24 -0000 Received: from unknown (HELO tea.thpoon.com) (mail@192.168.1.2) by cr103675-a.bloor1.on.wave.home.com with SMTP; 23 Nov 2000 11:57:24 -0000 Received: from antipode by tea.thpoon.com with local (Exim 3.12 #1 (Debian)) id 13yv0F-0007gy-00 for ; Thu, 23 Nov 2000 06:57:23 -0500 To: freebsd-questions@FreeBSD.ORG Subject: hard drive problems From: Arcady Genkin X-Face: 0=A/O5-+sE[Tf%X>rYr?Y5LD4,:^'jaJ!4jC&UR*ZrrK2>^`g22Qeb]!:d;}2YJ|Hq"LHdF OX`jWX|AT-WVFQ(TPhFVak)0nt$aEdlOq=1~D,:\z5QlVOrZ2(H,mKg=Xr|'VlHA="r Organization: thpoon.com Mail-Copies-To: never Date: 23 Nov 2000 06:57:23 -0500 Message-ID: <87pujmlx3w.fsf@tea.thpoon.com> Lines: 43 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way to non-destructively diagnose if a certain block on a hard drive is bad? I keep getting these had read errors for certain blocks. Since the block numbers are repeating repeatedly, it makes me suspect that the disk is at fault. Also, where can I read what the `status' ad `error' values tell me? Nov 1 ad2: HARD READ ERROR blk# 25423887 Nov 1 ad2: HARD READ ERROR blk# 25423887 status=59 error=40 Nov 1 ad2: HARD READ ERROR blk# 25423887 status=59 error=40 Nov 1 ad2: HARD READ ERROR blk# 25426943 status=59 error=40 Nov 1 ad2: HARD READ ERROR blk# 25427071 status=59 error=40 Nov 1 ad2: HARD READ ERROR blk# 25426943 status=59 error=40 Nov 1 ad2: HARD READ ERROR blk# 25427071 status=59 error=40 Nov 1 ad2: HARD READ ERROR blk# 25426943 status=59 error=40 Nov 1 ad2: HARD READ ERROR blk# 25416623 status=59 error=40 Nov 1 ad2: HARD READ ERROR blk# 25416623 status=59 error=40 Nov 1 ad2: HARD READ ERROR blk# 25418671 Nov 1 ad2: HARD READ ERROR blk# 25418687 status=59 error=40 Nov 1 ad2: HARD READ ERROR blk# 25418687 status=59 error=40 Nov 1 ad2: HARD READ ERROR blk# 25418687 status=59 error=40 Nov 1 ad2: HARD READ ERROR blk# 25418671 Nov 1 ad2: HARD READ ERROR blk# 25418687 status=59 error=40 Nov 1 ad2: HARD READ ERROR blk# 25418687 status=59 error=40 Nov 1 ad2: HARD READ ERROR blk# 25418687 status=59 error=40 Nov 4 ad2: HARD READ ERROR blk# 25677679 status=59 error=40 Nov 11 ad2: HARD READ ERROR blk# 25677679 status=59 error=40 Nov 18 ad2: HARD READ ERROR blk# 25677679 status=59 error=40 Nov 23 ad2: HARD READ ERROR blk# 25418671 Nov 23 ad2: HARD READ ERROR blk# 25418687 status=59 error=40 Nov 23 ad2: HARD READ ERROR blk# 25418687 status=59 error=40 Nov 23 ad2: HARD READ ERROR blk# 25418687 status=59 error=40 FWIW, the harddrive is an IBM Deskstar 13G. The motherboard is an HX chipset-based. I'm running 4.2-S. I have been using the harddrive for FreeBSD since Nov 1. When I put it in, I dedicated it all to one slice, and checked for free blocks. Nevertheless, the very first day I started getting these kernel messages. Many thanks, -- Arcady Genkin Don't read everything you believe. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message