An idea comes to mind:
Will it be possible detach the drive from the 3000; attach to a PC qith
an SCSI controller, and use its BIOS to low level format the drive.
Also this will check for bad spots.
later, you can put it on the 3000 as a brand new disk.
Regards,
-- Andres j. Ogayar
-- I.T. Department
-- Raytheon Microelectronics Espaņa (Malaga, Spain)
-- +34.95.224.92.27
Doug Werth
<doug@BEECHGLE Para: [log in to unmask]
N.COM> cc:
Enviado por: Asunto: Re: Scratchvol Problem
HP-3000
Systems
Discussion
<HP3000-L@RAVE
N.UTC.EDU>
17/10/2001
03:29
Por favor,
responda a
Doug Werth
John,
Do you have a system with Mirror/iX on it? Perhaps you could temporarily
install the disk on that system so that you can use SUSPENDMIRRVOL followed
by SCRATCHVOL.
What I have done in this situation before is to blow away the volume label
on the disk and then reboot. If you have the diagnostic password from HP
you
can use the SCSI disk diagnostics to perform a write then read test to the
first several sectors on the disk. This will write random data over top of
the volume label. A second option is to use the DSEC command in DEBUG to
write binary zeroes to the volume label area. When you reboot the system
will see the unrecognized volume label rather than a disk that is part of a
Mirror/iX pair and allow you to scratch it.
Both of these options are extremely dangerous and should be exercised with
great care as you could easily ruin the wrong disk.
HTH.
Doug.
Doug Werth Beechglen Development Inc.
[log in to unmask] Cincinnati, Ohio
----- Original Message -----
From: "John Clogg" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, October 16, 2001 7:39 PM
Subject: Scratchvol Problem
> We have an old, forgotten 927 that I am trying to resurrect as our
> crash-and-burn platform and for general playing around. It had a dead
disc
> drive, but that was no problem, because have several old, retired
clunkers
> on the shelf. I replaced the bad drive (which was in the system volume
> set), did an install, and am now trying to use VOLUTIL to rebuild the
volume
> set.
>
> The problem is that this drive was formerly a member of a mirrored volume
> set that had the same volume set name as a volume set on this machine.
The
> status shown by DSTAT is "PENDING-MD", and the following message is being
> sent to the console periodically: "MIRRORED PARTNER MISSING FOR LDEV #4".
I
> did a VSCLOSE on the volume set (this isn't really a member of that set,
but
> has the same volume set name). All of the "real" members of that set are
> now in a "loner" state, while the "new" disc is still in the "PENDING-MD"
> state. Volutil will not allow me to do a SCRATCHVOL on this device,
because
> it's not a loner. We do not have Mirrored Disc/iX on this machine. It
is
> on MPE/iX release 6.0. Any suggestions?
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
