Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!darwin.sura.net!gatech!asuvax!ennews!enuxha.eas.asu.edu!berry
From: berry@enuxha.eas.asu.edu (Joel R. Berry)
Subject: [386bsd]WD Patches from patchkit cause problems with bootup.
Message-ID: <1992Oct15.000131.2114@ennews.eas.asu.edu>
Keywords: ESDI WD 386BSD
Sender: news@ennews.eas.asu.edu (USENET News System)
Organization: Arizona State University
Date: Thu, 15 Oct 1992 00:01:31 GMT
Lines: 21
BSDr's,
I have installed the patch kit ( beta ) and all works well except
when I add the on that tells the wd driver to return errors when it
finds one on the disk. My disk is an Micropolis 330M esdi drive. The
problem happens upon running fsck. It fails when checking. The blocks
that were bad are placed into the bad144 table, but I guess that fsck
is not reading that or something. How should I go about having
fsck know about my errors but not dying from them. Fsck stops with
a read error on the bad spots. What should I do about it. For now
I have just removed that patch and have gone on from there, but I would
like to be able to install it for completion reasons.
Sorry if this is a repost, but I did not receive any replies from
the previous post so I think that it did not make it off campus. Also,
our news reader has been doing some wierd things, so please respond
via mail if possible. Thanks for any info.
joel berry
--
-----------------------------------------------------------
Joel Berry | berry@enuxha.eas.asu.edu
-----------------------------------------------------------