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!uwm.edu!math.ohio-state.edu!howland.reston.ans.net!pipex!uunet!Germany.EU.net!netmbx.de!zib-berlin.de!gmdtub!ats From: ats@first.gmd.de (Andreas Schulz) Newsgroups: comp.os.386bsd.questions Subject: Re: [FreeBSD 1.1.5.1] bad block scanning Message-ID: <5722@bigfoot.first.gmd.de> Date: 16 Oct 94 19:06:06 GMT References: <37pm7q$gf6@eplet.apana.org.au> Sender: news@bigfoot.first.gmd.de Organization: GMD-FIRST Lines: 31 In article <37pm7q$gf6@eplet.apana.org.au>, Graham Menhennitt <gfm@werple.apana.org.au> wrote: >I have just installed FreeBSD 1.1.5.1 successfully. I have a 1.3 Gb Conner >SCSI drive connected to a Adaptec 1542B controller. > > DIRECTORY CORRUPTED I=165237 OWNER=bin MODE=40755 > SIZE=512 MTIME=JuL 4 10:29 1994 > DIR=? Thanks for that report. Now i know i am not alone. The drive is perfect, you don't have a bad block on it. There is only a no go between the high-end conners and FreeBSD in the moment. I have seen exactly the same error as you are describing with a Conner CFP1060S drive. You can check it under DOS and would not get any error. I have mine now in a SUN with a fast 10 Mb adapter and have not seen an error with it. The error can be either the FreeBSD driver or the disk firmware, i have not found out which i can blame. The only idea i have in the moment is trying to get the write requests down to smaller values. That the drives firmware is simply choking on too large blocks. Do you have a chance to get FreeBSD 1.1 into your hands and try that out ? 1.1 doesn't have written large blocks in one chunk to the disk, so maybe this works. I am also interested in anything you find out about this error. -- ATS ( ats@first.gmd.de or ats@cs.tu-berlin.de ) Andreas Schulz GMD-FIRST 12489 Berlin-Adlershof Rudower Chaussee 5 Gebaeude 13.7 Tel: +49-30-6392-1856 Germany/Europe