From owner-freebsd-questions  Sun Feb 14 10:14:48 1999
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA20810
          for freebsd-questions-outgoing; Sun, 14 Feb 1999 10:14:48 -0800 (PST)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from neale.econ.vt.edu (neale.econ.vt.edu [128.173.173.159])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20805
          for <questions@FreeBSD.org>; Sun, 14 Feb 1999 10:14:46 -0800 (PST)
          (envelope-from rdmurphy@neale.econ.vt.edu)
Received: (from rdmurphy@localhost)
	by neale.econ.vt.edu (8.8.8/8.8.8) id NAA01515;
	Sun, 14 Feb 1999 13:17:06 -0500 (EST)
	(envelope-from rdmurphy)
From: "Russell D. Murphy" <rdmurphy@vt.edu>
Date: Sun, 14 Feb 1999 13:17:06 -0500 (EST)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="AqqpxvV/SJ"
Content-Transfer-Encoding: 7bit
To: questions@FreeBSD.ORG
Subject: File system still dirty
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14023.4748.174556.313007@neale.econ.vt.edu>
Reply-To: rdmurphy@vt.edu
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I have a bit of a problem with my laptop.  I recently upgraded to
3.0-stable (and made world Friday).  (Possible red herring:  I've
noticed a couple of times since I moved from 2.2.8 to 3.0-S that
shutdown -p would leave the machine complaining upon reboot that / was 
not clean.)

Today, the machine complains (while running fsck manually, since the
auto boot failed):

wd0s2a: hard error reading fsbn 65734 of 65712-65823 (wd0s2 bn 65734;
  cn 8 tn 19 sn 25) (status 59<rdy,seekdone,drq,err> error 40<uncorr>)

CANNOT READ: BLK 65712
CONTINUE? [yn]

If I say yes, it gives another hard error message:

wd0s2a: hard error reading fsbn 65734 (wd0s2 bn 65734; 
  cn 8 tn 19 sn 25) (status 59<rdy seekdone,drq,err> error 40<uncorr>)
THE FOLLOWING DISK SECTORSD COULD NOT BE READ: 65734,

And, "FILE SYSTEM STILL DIRTY".

Is this a dying hard drive?  Is the 2.2.8-->3.0 transition merely a
coincidence?  What can I do to resurrect this thing?

By the way, in my attempt to let fsck fix things for me, I seem to
have deleted all the device files for my other partitions (other than
/).  I assume I can recreate them without trouble(?) - (if the disk is 
completely lost. . .).

Thanks for your help.

Russ Murphy

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message