topic Re: Cannot form DSA0: in Operating System - OpenVMS

Cannot form DSA0:

FOX MULDER_2 — Tue, 08 May 2007 04:57:34 GMT

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

Re: Cannot form DSA0:

Duncan Morris — Tue, 08 May 2007 05:34:50 GMT

Hi,

do you have all the available 6.2 patches installed?

In particular, do you have ALP_CLUSI installed?

Duncan

Re: Cannot form DSA0:

FOX MULDER_2 — Tue, 08 May 2007 05:40:45 GMT

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

Re: Cannot form DSA0:

Karl Rohwedder — Tue, 08 May 2007 05:47:01 GMT

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

regards Kalle

Re: Cannot form DSA0:

Wim Van den Wyngaert — Tue, 08 May 2007 05:59:35 GMT

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

Re: Cannot form DSA0:

FOX MULDER_2 — Tue, 08 May 2007 06:04:32 GMT

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

Re: Cannot form DSA0:

Duncan Morris — Tue, 08 May 2007 06:28:04 GMT

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

Re: Cannot form DSA0:

Wim Van den Wyngaert — Tue, 08 May 2007 06:30:14 GMT

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

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

Re: Cannot form DSA0:

Wim Van den Wyngaert — Tue, 08 May 2007 06:39:41 GMT

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

Re: Cannot form DSA0:

FOX MULDER_2 — Tue, 08 May 2007 06:52:06 GMT

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 ?

Re: Cannot form DSA0:

Wim Van den Wyngaert — Tue, 08 May 2007 07:12:56 GMT

Staconfig is used to determine the system disk connection.

000003C4 means "no such disk quorum file". Could the file be corrupt ? Is it present ? But then why is it only checked when using shadowing.

Wim

Re: Cannot form DSA0:

Volker Halle — Tue, 08 May 2007 07:19:57 GMT

Fox,

STACONFIG.EXE is an OpenVMS program run early during boot/startup to configure the device IO database. This program has incurrect a system service exception in kernel mode and caused the system to crash. Let's see, if we can obtain some more information from the system dump.

Once you system has written the dump, boot without using a shadowed system disk and look at the CLUE file (CLUE$COLLECT:CLUE$node_ddmmyy.LIS). It should be generated from the system dump automatically during boot.

Please post the CLUE file as a text attachment.

Volker.

Re: Cannot form DSA0:

Volker Halle — Tue, 08 May 2007 07:23:49 GMT

Wim,

000003C4 is the bugcheck code for SSRVEXCEPT !

ANAL/SYS
SDA> SHOW BUG 3C4

Volker.

Re: Cannot form DSA0:

FOX MULDER_2 — Tue, 08 May 2007 08:09:19 GMT

Hi,
The dump file is not getting updated.

$ dir sysdump.dmp/date=(c,m)

Directory SYS$SYSROOT:[SYSEXE]

SYSDUMP.DMP;3 14-DEC-1996 16:29:13.79 23-NOV-1997 12:04:06.89

Total of 1 file

So,I think it is dumpede into the pagefile.

While I issued the command :
SDA> Sh crash

System information
------------------
Version of system: OpenVMS (TM) Alpha Operating System, Version V6.2

System Version Major ID/Minor ID: 3/0

System type: AlphaServer 2100 4/275

Primary CPU ID: 00

Bitmask of CPUs active/available: 00000001/00000001

CPU 00 database address: 80B10000

Is there any other way,to get the dump?

thanks

Re: Cannot form DSA0:

Wim Van den Wyngaert — Tue, 08 May 2007 08:42:27 GMT

"If SYSGEN system check is enabled, the first MOUNT of a system disk will crash the system." (patch 6.2 that you might not have)

(SYSGEN SHOW SYSTEM must be 0)

Wim

Re: Cannot form DSA0:

Volker Halle — Tue, 08 May 2007 08:42:40 GMT

Fox,

the dump is getting written to DKB0 as indicated by:

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

The dumpfile modification date is NEVER updated by writing the dump. Writing the dump happens without any file system operations, the memory pages get just dumped into the blocks representing the dumpfile.

Is there a recent CLUE file (CLUE$COLLECT:CLUE$node_ddmmyy_hhmm.LIS) ?

What does $ ANAL/CRASH SYS$SYSTEM report ?

Volker.

Re: Cannot form DSA0:

FOX MULDER_2 — Tue, 08 May 2007 11:55:40 GMT

Hi,

OpenVMS (TM) Alpha System dump analyzer

%SDA-E-DUMPEMPTY, dump file contains no valid dump

This is the output when
ana/crash sys$system
is given.

Thnaks

Re: Cannot form DSA0:

Robert Brooks_1 — Tue, 08 May 2007 13:09:04 GMT

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 ...

--

Starting with V8.3, one gets a SHDWREQALLOC bugcheck with the following text . . .

Allocation class is required for shadow set members.

-- Rob

Re: Cannot form DSA0:

Martin Hughes — Tue, 08 May 2007 21:37:50 GMT

Do you have the latest shadowing patch for 6.2?. See
http://ftp.support.compaq.com.au/pub/ecoinfo/ecoinfo/a62.htm

Re: Cannot form DSA0:

Nigel Wright_1 — Wed, 09 May 2007 02:04:28 GMT

Is this system disk - when it was formed before as a shadow - mounted on another node in the cluster? If it was, is it still mounted now? What do the other nodes think is the state of this shadow disk?

Nigel.