Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!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:40:22 +0200
Organization: Private U**X site; member IN e.V.
Lines: 17
Message-ID: <34v4smINNjl7@bonnie.sax.de>
References: <33j9hp$41l@sol.sun.csd.unb.ca> <jmonroyCvozLK.5q9@netcom.com> <bakulCvpyuw.5nB@netcom.com> <jmonroyCvqswn.Ktn@netcom.com>
NNTP-Posting-Host: bonnie.sax.de
jmonroy@netcom.com (Jesus Monroy Jr) writes:
>: Sectors are numbered 1 through 15 and the error message reports
>: sec 15, which is a valid sector number.
>:
> Yes, but the number 15 is the last correctly used
> by the FDC, which is my comment.
Nope. Sector 15 has been the one causing the CRC failure. To be correct,
the ID field of sector 15 (that's why ST1 *and* ST2 have the `bad_crc'
bit set).
--
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.