Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!spool.mu.edu!torn!news.unb.ca!angus!phowlett From: phowlett@angus.ASG.unb.ca (Peter Howlett) Newsgroups: comp.os.386bsd.bugs Subject: Re: FreeBSD, fd0d: hard error Date: 3 Sep 1994 16:42:22 GMT Organization: University of New Brunswick Lines: 25 Message-ID: <34a91e$h2f@sol.sun.csd.unb.ca> References: <33j9hp$41l@sol.sun.csd.unb.ca> <3453os$sru@steel.interlog.com> <3486q6$dr6@pdq.coe.montana.edu> NNTP-Posting-Host: angus.asg.unb.ca X-Newsreader: TIN [version 1.2 PL2] Nate Williams (nate@bsd.coe.montana.edu) wrote: : In article <3453os$sru@steel.interlog.com>, : David Shadoff <daves@gold.interlog.com> wrote: : >Peter Howlett (b6ps@jupiter.sun.csd.unb.ca) wrote: : >: Howdy, : > : >: 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 : These are floppy errors. I suppose you mean that these are errors that are generated by the floppy device driver. These are NOT however, errors with the floppy disks themselves. I find it a little hard to believe that every floppy I've tried for the past week and a half (Sony's, 3M's and generics) are all bad. Then theres the fact that other operating systems dont seem to have any problems reading and writing to them. I not saying that there is anything wrong with FreeBSD, I really dont know what the problem is except to say that the floppies are OK. -------------------------------------------------------------------- Peter Howlett Atlantic Systems Group E-Mail: phowlett@ASG.unb.ca Fredericton, N.B. Canada