Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!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: <9011301348.AA23296@richter.mit.edu>
Date: 30 Nov 90 13:48:44 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 19

Try using INVOL's option 7 to recreate a bad-block list. I don't have
any HP 9000's, but if the FBS program is included (find-bad-spot) and
if the version is similar to the latest versions on the SAU7/SAU8/SAU9
machines, then  FBS can rebuild the bad-block list as it tests the
disk drive. Earlier versions of FBS just typed out the numbers of the
bad blocks on the console -- scrolling most of them off the top of the
screen -:(, the newer version I've used is *much* nicer! Be forwarned,
FBS takes *forever*! (after all, it has to write and re-read each block
on the disk with several different data patterns) On my 155 MB DN4000
it runs for 2 to 3 hours per pass, and the time is dependent on the
disk transfer rate and the size of the disk, not on the speed of the CPU.


 -- 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)