Subject: | |
From: | |
Reply To: | |
Date: | Sun, 25 Jul 1999 12:28:27 +0200 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Bob Comeau wrote:
>
> The NEWVOL command seemed to work until it got to where it
> tried to mount the new volume, then it choked with an
> error about an UNKNOWN Volume and :
> *Error: Subsys 163, Info: -10.
Do you remember the exact NEWVOL command that you used ?
I am asking because there is a reported problem (5003325415)
when the permanent and transient values of your NEWVOL command
do not add up to >= 101%. i.e. if you tried a
volutil> newvol mpexl_system_volume_set:member4 4 75 25
this could be the cause of your problem (unless you are on
MPE/iX 6.0, where the above SR is fixed).
If your problem does not fit the above scenario, then it maybe
the disk did not 'survive' the 'move'.
> Volume name: State: Ldev: Type: Path:
> ----------- ----- ---- ---- ----
>
> MEMBER1 MASTER 1 433330 52.6.0
> MEMBER2 MEMBER 2 433232 52.5.0
> MEMBER3 MEMBER 3 433234 52.4.0
> MEMBER4 (VOLUME NOT AVAILABLE)
>
I am afraid you will have to do an INSTALL to correct this; although
no data is on that volume, some OS data structure (called the Volume
Set Information Table - VSIT) is in jeopardy now, which will cause
a problem for the transaction manager (XM) to work correctly for the
MPEXL_SYSTEM_VOLUME_SET.
Hope this helps,
Goetz.
|
|
|