*BSD News Article 35555


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!warrane.connect.com.au!kralizec.zeta.org.au!not-for-mail
From: bde@kralizec.zeta.org.au (Bruce Evans)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: FreeBSD, fd0d: hard error
Date: 7 Sep 1994 20:37:39 +1000
Organization: Kralizec Dialup Unix Sydney - +61-2-837-1183, v.32bis v.42bis
Lines: 33
Message-ID: <34k55j$krm@kralizec.zeta.org.au>
References: <33j9hp$41l@sol.sun.csd.unb.ca> <jmonroyCvozLK.5q9@netcom.com> <bakulCvpyuw.5nB@netcom.com>
NNTP-Posting-Host: kralizec.zeta.org.au

In article <bakulCvpyuw.5nB@netcom.com>, Bakul Shah <bakul@netcom.com> wrote:
>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
>
>>	ST0	is the register -- STATUS REGISTER 0
>>	44	is the  hex value 0x44

>High nibble == 4 says abnormal termination (it is 8 for an
>invalid command).  Bit 2 indicates the head number (the not ready
>bit is bit D3).  The error message correctly decodes ST0 bits.

Yes, it looks like a normal floppy media error.  However, then fsbn 62
outside the range 64-71 does not inspire confidence in the relevance
of the error message.  The version of the fd driver just before 1.1.5
came out printed completely bogus fsbn's in error messages but I think
that was fixed.

>One possibility is the value in the GPL byte of the read/write
>command is incorrect.  I don't have FreeBSD sources anymore but a
>cursory glance at fd.c of NetBSD reveals this value to be on the
>high side for atleast the 1.2MB floppy type.  In general the gap1
>value should be lower for higher number of sectors/track.  The
>gap1 values used in FreeBSD fd driver should be compared against
>what Linux and dos do and corrected if necessary.

gap1 is 0x1B for 1.2M and 1.44M.  This is normal.  I think there's
a write timing bug somewhere else.  Writes sometimes appear to
succeed, but the disk becomes unreadable.
-- 
Bruce Evans  bde@kralizec.zeta.org.au