Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!samsung!munnari.oz.au!bruce!monu1!monu6!out117w
From: out117w@monu6.cc.monash.edu.au (y    ng)
Newsgroups: comp.sys.apollo
Subject: Re: null physical volume label : beware in invol !
Summary: invol in 400t with SR10.2
Message-ID: <1990Nov30.170410.8812@monu6.cc.monash.edu.au>
Date: 30 Nov 90 17:04:10 GMT
References: <9011281730.AA04136@meto.UMD.EDU> <2185@tuvie.UUCP>
Organization: Caulfield Campus, Monash University, Melb., Australia.
Lines: 18

In article <2185@tuvie.UUCP>, chytil@vlsivie.tuwien.ac.at (Chytil Georg) writes:
> I've just tried to invol our new 400t's SCSI-Disk w6:0 and after choosing
> option 1 (formating virgin physical volume) pressed <RETURN> twice, be it
> by accident or through a tossing (word?) keyboard.
> 
> Be warned ! While this may happen quite easy it's a proper way to make Your
> disk unrecognisable to invol, salvol, mtvol and so on : 'invalid physical
> volume label','unable to read badspot list' ... 
> 
We had similar experience when involing an external 660mb storage module 
connected to the  SCSI port on the 400t running SR10.2. We contacted the
local hp response centre and they could not figure out why and suggested
that we need sr10.3 to support this new drive. Unfortunately 10.3 is not
yet available in Australia so we decided to investigate further.
After hours of experimenting with the invol we finally found the way to get 
out of this mess. If you initialise the bad spot list to null you can 
then proceed as usual. I presume SCSI drive manages its bad spot list internally?
As far as the host computer is concerned the drive is bad spot free ??