Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!RICHTER.MIT.EDU!krowitz
From: krowitz@RICHTER.MIT.EDU (David Krowitz)
Newsgroups: comp.sys.apollo
Subject: Re: null physical volume label : beware in invol !
Message-ID: <9012031520.AA29601@richter.mit.edu>
Date: 3 Dec 90 15:20:47 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 24

I believe you are correct. All the SCSI drives I have encountered
so far manage their own bad spot lists internally. As far as the CPU
was concerned (this is on own DN2500's), the drives are error-free.

If you wish to check this, you can use the FBS (find-bad-spots) program
located in your appropiate sau (stand-alone-utilities) directory (ie.
/sau9/fbs for a DN2500, /sau8/fbs for a DN3000, /sau7/fbs for a DN
3500/4000/4500). This program will read and write all blocks on the
disk with several data patterns looking for errors and will add any
bad-spots it finds to the bad block list. Be forwarned: FBS takes
several hours to run, and since it runs from the MD your machine will
be down for the entire period. There is also a version of FBS in the
/systest/ssr_util directory which will execute with your machine up
and running, checking a disk that has not been mounted. I haven't used
this on-line version, so I can't say whether or not it's any faster
than the off-line version.


 -- David Krowitz

krowitz@richter.mit.edu   (18.83.0.109)
krowitz%richter.mit.edu@eddie.mit.edu
krowitz%richter.mit.edu@mitvma.bitnet
(in order of decreasing preference)