Jim, I can understand your frustration.  We added 16 F/W SCSI 2GB drives
and 2  5GB disc arrays to private volume sets.  When the drives were
installed, the system reported them as UNKNOWN.  All we did was do a NEWVOL
for the arrays.  We did NEWMIRROVOL for the SCSI drives and mirrored them.
The system then asked if wanted to initialize them, we replied yes.  Then
we used the Bradmark product to do a ManageSet process to spread files
across the entire volume sets evenly.

Now I have errors on one the arrays, and HP can NOT tell which mech is bad
drive.  We use RAID Zero.  Striping the data across 5 drives.  One of them
being a parity drive.  We have trouble restoring data and get the following
error message.

Anyone out there, know what I can do or tell HP to run so that they can
figure out which of the 5 mechs is bad???  Here's the error.  I've had the
CE working on this since Monday night.

 Bad SYSTEM LOGICAL Sector number 0x66ABA0 on ldev 623 (io_status=FFD30071)
 Filename of bad file:/M4261/INC2/FLX1EE04

Thanks!!
Juan Criel w/Hewitt


_____________________________________________________________
*in reply to Therm_O_Link_Inc's memo of  08/21/97 12:18:23 PM
To:       HP3000-L @ RAVEN.UTC.EDU
cc:
From:     [log in to unmask]
Date:     08/21/97 01:18:23 PM AST
Subject:  918: The Saga Continues....




Well, here it is, on the afternoon of the third day since we lost
two disk drives and we are still limping along with only two out of
three drives functional.

The SE came out today to install a replacement 2GB drive in the HASS
enclosure.  No problem, right?  HAH!  After installing the drive and
rebooting, it mounted okay, but showed up in DSTAT in UNKNOWN status.
VOLUTIL's SCRATCHVOL and INITVOL wouldn't work on it.  I asked about
doing a FORMATVOL and the SE said, "Yeah, Let's try that".  After a
few minutes of FORMATVOL, he said, "Break out of it and let's try
some diagnostics".  Well, after aborting the FORMATVOL, the drive
was gone!  Didn't show up in DSTAT, MAPPER couldn't see it, nothing!

After another half hour of messing around, the SE decided to bring
another mech out at a later (unspecified) time.  I hope he uses
this time to find out how to install a SCSI drive.

So, before he gets back here and really messes things up, does anyone
know the proper procedure to get a drive recognized when it's in
UNKNOWN status?  Thanks.

Jim Phillips                            Manager of Information Systems
E-Mail: [log in to unmask]      Therm-O-Link, Inc.
Phone: (330) 527-2124                   P. O. Box 285
  Fax: (330) 527-2123                   Garrettsville, Ohio  44231

Sent by Therm_O_Link_Inc







_____________________________________________________________