Cannot form DSA0:

[FOX MULDER_2]

Hi,
I am having a problem with a VMS server running on V6.2,the details are as follows :
When the system is booting in a single disk DKB0 its working fine.
When booting in sysboot and enabling shadowing of system disk :
>>>b -fl 0,30001 DKB0
sysboot>set SHADOW_SYS_DISK 1
sysboot>cont
the server crashes giving a dump :

BUGCHECK ****

** Code=000003C4: SSRVEXCEPT, Unexpected system service exception

** Crash CPU: 00 Primary CPU: 00 Active CPUs: 00000001

** Current Process = STACONFIG

** Image Name = STACONFIG.EXE

**** Writing dump to HBVS member with unit number of 0

**** Starting Memory Dump...

..............

**** Global page table not in memory - no global pages dumped

**** Memory Dump complete - not all processes saved


Can anyone please let me know how to solve the problem ?

Thanks

[Duncan Morris]

Hi,

do you have all the available 6.2 patches installed?

In particular, do you have ALP_CLUSI installed?

Duncan

[FOX MULDER_2]

Hi,
Thanks for the prompt reply.

The update patches are not installed,but it was working fine for ~ 2 years.
A few days back it was crashed and I am unable to add system disk shadow member.
I have a plan to install the patches but other than that is there any way to recover it.

"In particular, do you have ALP_CLUSI installed?"
What is ALP_CLUSI ?

Thnaks

[Karl Rohwedder]

How are the other shadowing parameters set, esp. SHADOWING, SHADOW_SYS_UNIT..?

regards Kalle

[Wim Van den Wyngaert]

Did the same thing in VMS 7.3 (not fully patched, no shadow license) and got a bugcheck too. But with process/exe sysinit.

And it started looping on "accessing system disk via original boot path".

Idem when I put shadowing on 1 too.

I normally change the params before the boot.

Wim

[FOX MULDER_2]

Hi,
The other params are;

Shadowing = 2
Shadow_sys_unit = 0 !as it is DSA0.

This is not a problem with license since,there are other disks also which are shadowed and are working fine.

Thanks

[Duncan Morris]

So, the system disk was part of a shadow set before the crash.

Have you tried booting from the "other" member of the shadowset? There may be a problem in the consistency of the shadowset itself.

Duncan

[Wim Van den Wyngaert]

Is your allocation class non-0 ?
(sysgen show alloc)

Wim (had tested with shadowing = 2, and also with license : same reaction)

[Wim Van den Wyngaert]

Out of doc : "You must use a nonzero allocation class for each physical device in the shadow set.".

VMS could tell you that in a nicer way ...

Wim

[FOX MULDER_2]

Hi,
Thanks to all for replying.
The system disk was shadowed before the crash.

Alloclus is set to 1.

Also,have tried booting from the other member also,same result.

Also,have restored image from tape,same result.
Hardware : no alerts or indication found.

Can anyone tell me where to find the description of the file staconfig.exe ?