From owner-freebsd-questions  Thu Aug  1 06:43:30 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id GAA15285
          for questions-outgoing; Thu, 1 Aug 1996 06:43:30 -0700 (PDT)
Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA15280
          for <questions@freebsd.org>; Thu, 1 Aug 1996 06:43:27 -0700 (PDT)
Received: (from amir@localhost) by prozac.neuron.net (8.7.5/8.6.12) id JAA04142 for questions@freebsd.org; Thu, 1 Aug 1996 09:53:53 -0400 (EDT)
From: "Amir Y. Rosenblatt" <amir@neuron.net>
Message-Id: <199608011353.JAA04142@prozac.neuron.net>
Subject: wd1s1f: hard error reading fsbn [2.1.0]
To: questions@freebsd.org
Date: Thu, 1 Aug 1996 09:53:53 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

For the past few nights, whenever the 2:00 am automatic job runs, I get
swamped with disk errors like the following:

Aug  1 02:11:24 wax /kernel: wd1s1f: hard error reading fsbn 630755 of
630752-630767 (wd1s1 bn 835555; cn 828 tn 14 sn 49)wd1: status
59<seekdone,drq,err> error 40<uncorr>

Yesterday morning I fsck'ed the disk but it was to no avail since the same
thing happened again today.  Any suggestions?

	-Amir