Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!spool.mu.edu!sol.ctr.columbia.edu!newsxfer.itd.umich.edu!europa.eng.gtefsd.com!emory!swrinde!pipex!sunic!trane.uninett.no!eunet.no!nuug!EU.net!Germany.EU.net!netmbx.de!zrz.TU-Berlin.DE!zib-berlin.de!irz401!uriah!not-for-mail
From: j@uriah.sax.de (J Wunsch)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: FreeBSD, fd0d: hard error
Date: 11 Sep 1994 16:33:55 +0200
Organization: Private U**X site; member IN e.V.
Lines: 58
Message-ID: <34v4gjINNjj5@bonnie.sax.de>
References: <33j9hp$41l@sol.sun.csd.unb.ca> <jmonroyCvozLK.5q9@netcom.com>
NNTP-Posting-Host: bonnie.sax.de
jmonroy@netcom.com (Jesus Monroy Jr) writes:
>Peter Howlett (b6ps@jupiter.sun.csd.unb.ca) wrote:
>: fd0d: hard error reading fsbn 62 of 64-71
>: (ST0 44<abnrml,top_head> ST1 20<bad_crc> ST2<bad_crc> cyl 1 hd 1 sec 15
> To make this short, it is quite possible that one of
> the applications you ran decided that it could read
> more than 15 sectors on a track, which on a 1.2 meg
> diskette is not possible. [...]
Impossible. Attempting to read a non-existent sector would have caused
a `sector not found' error. (The index hole passed twice without being
able to find any sector ID field containing the requested sector
number.) Furthermore, sector 15 should really be on a 1.2 MB diskette,
since sector numbering starts at 1.
The above error is clearly a `bad CRC in sector ID field'. That is,
the sector ID of the requested sector has been found & read, but the
CRC check failed.
Btw., Jesus, your quotation of the manual has been a bit obsoletish;
the textual translation of the error message did already state what
`0x44' meant in ST0. Further, you forgot to quote the appropriate
parts for ST1 and ST2, which are far more important in our case.
===
Sorry guys, i've not been working very hard on FreeBSD 2.0 as some
people assumed, i've simply been on a two-week vacation. Thus, i
missed the original posting. In the followups, i found that there's a
mixture of two problems: one related to the floppy driver, and one
with the Adaptec (or: sd0) driver. I cannot speak for the latter, only
for the floppy stuff here.
[Btw., people having problems should first contact the `responsive
person' as known from the ROSTER.FreeBSD file. This way you'd have
known that i'm the one in question, and hopefully, my vacation script
would have sent you a message...]
Which floppy controllers are known to fail? What are the chips there?
Are these `enhanced' chips or simple NEC-765 clones?
The failure as i've seen the description is really a hardware failure,
not a driver failure. The FDC has seen a sector ID field but failed to
CRC check this ID field. The only software problem could be an
initialization failure (or some timing problem, e.g. too short of head
settlement time). If some of you experiencing the errors (sorry, *I*
don't) could try to help me here, i'd appreciate this. Does the
failure happen on any drive on that controller, or only with a
particular drive/controller combination? Please, contact me with
private email if you need further details (joerg_wunsch@uriah.sax.de).
--
cheers, J"org work: joerg_wunsch@tcd-dresden.de
private: joerg_wunsch@uriah.sax.de
Steinbach's Guideline for Systems Programming:
Never test for an error condition you don't know how to handle.