Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!pipex!sunic!trane.uninett.no!news.eunet.no!nuug!news.eunet.fi!funic!sauna.cs.hut.fi!cs.hut.fi!hsu
From: hsu@cs.hut.fi (Heikki Suonsivu)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: [NetBSD 0.9] File system corruptions
Date: 15 Sep 1993 13:37:33 GMT
Organization: Helsinki University of Technology, Finland
Lines: 27
Distribution: inet
Message-ID: <HSU.93Sep15163731@laphroaig.cs.hut.fi>
References: <MARK_WEAVER.93Sep14041323@excelsior.cs.brown.edu> <CDCMwx.6DJ@veda.is>
NNTP-Posting-Host: laphroaig.cs.hut.fi
In-reply-to: adam@veda.is's message of 14 Sep 93 14:57:54 GMT
In article <CDCMwx.6DJ@veda.is> adam@veda.is (Adam David) writes:
applies to NetBSD also). The wd driver is either not stable enough or
Long time ago (ancient 386bsd 0.1 age) I saw a message about the wd driver,
which was fixed somewhere in Norway. I don't know if it ever got in to
NetBSD.
I tried install 386bsd 0.0 and 0.1, but both tries failed because of the
faulty wd driver.
We just booted NetBSD up on MFM disks, but haven't yet mapped out all the
bad blocks. They were marked bad when the disk was hard formatted, but
apparently NetBSD ignores dos bad track table?
The driver also seems to read all blocks from a track even if it has got
one bad sector. With correctly working hardware this is not so serious
problem, but with buggy controllers like wd1006, which fails to send the
sector interrupt when it sees a bad block on multi-sector transfer, it is
nasty (dies with disk light on). Currently we are using wd1003 clone
instead, but 1006 would get us more speed out of that MFM junk we have
around :-)
-
Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND,
hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN
/G=Heikki/S=Suonsivu/O=hut/OU=cs/PRMD=Inet/ADMD=Fumail/C=FI