Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!uunet!math.fu-berlin.de!fub!einoed!bitcave!jdb
From: jdb@bitcave.in-berlin.de (Joern D. Busch)
Subject: Re: wd1 bad144 woes & workaround (& another idea)
Message-ID: <1992Aug13.001403.10404@bitcave.in-berlin.de>
Organization: BitCave BBS, Berlin, FRG
References: <16auimINNal@disaster.Germany.EU.net>
Date: Thu, 13 Aug 1992 00:14:03 GMT
Lines: 43
bs@Germany.EU.net (Bernard Steiner) writes:
>swapon: wd1b: device not configured and mount complained in a very similar
>fashion.
I'm not really sure about the necessity of this, but does your config
file include something like:
config "386bsd" root on wd0 swap on wd0 and wd1
About bad144 in general, a few days ago I asked here about it, at that
point missing the dd trick. The very first mail I received mentioned
that trick, so after low-level formatting the drive, letting the con-
troller mark the bad sectors, installing an appropriate disklabel and
initialising bad144 wd0 0, I dd-searched all bad sectors and marked
them with bad144 -a, and in fact all the right hd/cyl combinations
(not 100% sure about the sects) got marked (as reported by bad144 wd0),
but -- it still wrote to these sectors.
By then I received a few more mails, mostly telling me that bad144 is
broken and I should use the controller's alternate sector option. I'm
doing that now, and it works just fine.
But -- another person (sorry, forgot the name, but thanks!) phoned me
and told me he got bad144 working by _not_ letting the controller mark
the bad tracks. This way the dd trick doesn't work, but you can just
mark all sectors of a known to be bad hd/cyl combination as bad. You
loose quite some disk space, especially if you not have a MFM (17sec)
drive, but if you're controller doesn't do alternate sectors I guess
it's the only way to go.
So it might be interesting but enerving to try the following: low-level
format, controller-mark bad sectors, dd-find bad sectors, bad144-mark
them while writing them down, low-level format again, _not_ let the
controller mark the bad sectors, bad144 the previously noted sectors.
After a precious weekend of reinstalling I'm a bit tired of this, so if
anybody tries this please let me and/or this newsgroup know.
cheers,
Joern.
--
Joern D. Busch, Postfach 210401, 1000 Berlin 21, FRG, (+49 30) 3931111
jdb@bitcave.in-berlin.de ..!mcsun!unido!fub!einoed!bitcave!jdb ..which reality?