Date: Sun, 14 Feb 1999 13:17:06 -0500 (EST) From: "Russell D. Murphy" <rdmurphy@vt.edu> To: questions@FreeBSD.ORG Subject: File system still dirty Message-ID: <14023.4748.174556.313007@neale.econ.vt.edu>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14023.4748.174556.313007>