*BSD News Article 35556


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!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: 7 Sep 1994 11:42:26 GMT
Organization: University of New Brunswick
Lines: 57
Message-ID: <34k8v2$jbb@sol.sun.csd.unb.ca>
References: <33j9hp$41l@sol.sun.csd.unb.ca> <jmonroyCvozLK.5q9@netcom.com> <bakulCvpyuw.5nB@netcom.com> <34k55j$krm@kralizec.zeta.org.au>
NNTP-Posting-Host: angus.asg.unb.ca
X-Newsreader: TIN [version 1.2 PL2]

Bruce Evans (bde@kralizec.zeta.org.au) wrote:
: 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

I dont know if this addition will contribute, but the error seems to
most commonly occur during the newfs from 'install' on the filesystem 
floppy. When this error does start coming up, it screws up the floppy 
(question marks for permission flags, zero length files, etc...). Not 
to forget this is with a floppy that was totally fine before the 
install script started. (ls, cd, gzip </dev/rsd1d >/dev/null &
all worked fine).

I have since been performing the installation manually (not using the
install script) using three and four filesystem floppies at a
time (when one screws up, reboot with the next one and keep going). 
I found that after I had the hard disk labeled and formatted (newfs'ed) 
I could cp the cpio files to the hard disk and extract them that way 
with no problems. The only problem I encounted was the fact the /bin/sh
on the filesystem floppy would'nt allow me to execute anything from
the hard disk once I had booted from the hard disk. ie:

   # ls
   pid 4: uid 0: sh: exited on signal 10
   # df
   pid 5: uid 0: sh: exited on signal 10
   ...

So I copied the /bin/sh from the boot floppy (kcopy_bt.flp) and 
then everything was fine! I installed the binary dist via ftp 
and now have a running FreeBSD system.

I didnt seem to have any problems cp'ing. My problems were all with
running programs on the filesystem floppy. (disklabel, newfs and
even simple extended reads of the install script, instant clear screen
in response to a question). Anyway, I hope this helps in case
anyone else ever has this problem.

Oh yes, my configuration is:
  486DX2/66 EISA, 2 VLB slots, 16MB 
  EISA SCSI-II BT747c (Bus mastering, includes the floppy controller)
  EISA ATI Ultra Pro (Mach32)
  (Tried this with only these two cards, still the same problems.)
  1 3.5" floppy drive.

  Quantum LPS540s SCSI-II 540MB (id 0)
  Hitachi DK315 SCSI-II 1.3GB (id 1)

--------------------------------------------------------------------
Peter Howlett			Atlantic Systems Group
E-Mail: phowlett@ASG.unb.ca	Fredericton, N.B. Canada