From owner-freebsd-questions@FreeBSD.ORG  Mon Jun 14 11:24:04 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D97B216A4CE
	for <questions@freebsd.org>; Mon, 14 Jun 2004 11:24:04 +0000 (GMT)
Received: from filter.Access4Less.net (filter.access4less.net [64.63.192.245])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 755AB43D54
	for <questions@freebsd.org>; Mon, 14 Jun 2004 11:24:04 +0000 (GMT)
	(envelope-from kaging@access4less.net)
Received: from access4less.net (unverified [10.24.3.21]) 
	by filter.Access4Less.net (Joe 1) with ESMTP id 65305892 
	for <questions@freebsd.org>; Mon, 14 Jun 2004 07:23:33 -0400
Sender: kaging@access4less.net
From: "Kevin Greenidge" <kaging@access4less.net>
To: questions@freebsd.org
X-Mailer: Quality Web Email  http://access4less.net
Date: Mon, 14 Jun 2004 05:26:03 -0500
Priority: normal
Message-id: <40cd7d3b.3d3.1281.1399945043@access4less.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Authenticated-User: kaging@access4less.net Domain filter.Access4Less.net
Subject: Hard Drive going bad? (hard error reading fsbn)
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: kaging@access4less.net
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2004 11:24:05 -0000

I started seeing the error messages in my logs. When I
googled the error some seem to think it may be a hardware
issue and some seem to think it's o/s specific. Trying to
see what's the general opinon. Running 4.9 


Jun 13 00:30:26 santacruz /kernel: ad0s1h: hard error
reading fsbn 197442991 of 26369632-26369887 (ad0s1 bn
197442991; cn 12290 tn 65 sn 46) status=59 error=40
Jun 13 00:30:37 santacruz /kernel: ad0s1h: hard error
reading fsbn 197443023 of 26369664-26369887 (ad0s1 bn
197443023; cn 12290 tn 66 sn 15) status=59 error=40
Jun 13 00:30:42 santacruz /kernel: ad0s1h: hard error
reading fsbn 197443055 of 26369696-26369887 (ad0s1 bn
197443055; cn 12290 tn 66 sn 47) status=59 error=40
Jun 13 00:30:53 santacruz /kernel: ad0s1h: hard error
reading fsbn 197443087 of 26369728-26369887 (ad0s1 bn
197443087; cn 12290 tn 67 sn 16) status=59 error=40
Jun 13 00:30:53 santacruz /kernel: ad0s1h: hard error
reading fsbn 197443119 of 26369760-26369887 (ad0s1 bn
197443119; cn 12290 tn 67 sn 48) status=59 error=40
Jun 13 00:30:53 santacruz /kernel: ad0s1h: hard error
reading fsbn 197443151 of 26369792-26369887 (ad0s1 bn
197443151; cn 12290 tn 68 sn 17) status=59 error=40
Jun 13 00:30:53 santacruz /kernel: ad0s1h: hard error
reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn
197443151; cn 12290 tn 68 sn 17) status=59 error=40
Jun 13 00:30:53 santacruz /kernel: ad0s1h: hard error
reading fsbn 197443151 of 26369792-26369823 (ad0s1 bn
197443151; cn 12290 tn 68 sn 17) status=59 error=40