Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!solaris.cc.vt.edu!uunet!fonorola!interlog.com!gold!daves From: daves@gold.interlog.com (David Shadoff) Newsgroups: comp.os.386bsd.bugs Subject: Re: FreeBSD, fd0d: hard error Date: 1 Sep 1994 17:41:47 GMT Organization: Interlog Internet Services -Voice (416) 975-2655 -Data 515-1414 Lines: 25 Message-ID: <3453os$sru@steel.interlog.com> References: <33j9hp$41l@sol.sun.csd.unb.ca> NNTP-Posting-Host: gold.interlog.com X-Newsreader: TIN [version 1.2 PL2] 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 : I get this trying to install FreeBSD 1.1.5.1 on a 486DX2 66 with : an ATI Ultra Pro (EISA) and BT747 SCSI adapter. The errors start coming : up anytime after the filesystem install script starts writing the : disklabels to the SCSI disk. It has actually made it through the procedure : once and only given these errors after the files start getting cpio'ed : to the new filesystems on the hard disk (Quantum SCSI2 540MB). The ST0 44 : is sometimes an ST0 40 and I have also received the occaisional timeout : error. The system does work under DOS, in case that matters any. I'm getting similar problems on FreeBSD 1.1 on an AHA1542B, using the same drive (Quantum LPS540). The errors show up as timeouts on sd0, and occasionally as an error something like: (AHA0:0:0 timeout). These happen a lot when doing any install, and they even happen when the system is just sitting there (demons running, no net traffic, nobody logged in, no swap). It's really bugging me, because the drive/controller combo works, if gen'd for DOS. daves@interlog.com