SAN BOOT from OpenVMS

[Robert Jacobs]

I tried to install the OS from the distribution and still got the bugcheck.

On boot it indicates a valid boot block etc... but then breaks.

perhaps I need to patch the OS with some eco that with work with the Storage I am working with or perhaps a higher version of the OS?

Robert

[Volker Halle]

Robert,

the immediate INCONSTATE bugcheck when booting from a FC SAN device is most typically caused by a mismatch in the naming of the boot device between OpenVMS and the console. This applies, if the crash is in SYS$DKDRIVER and R0 will be 908 and R5 will contain a DGA device UCB.

Please make sure, that you use the following commands to set up the boot device:

>>> wwidmgr -show wwid
>>> wwidmgr -quickset -udid n

where n is your unit number of the boot device, i.e. the IDENTIFIER given to that device on the HSG80 (or EVA). Do NOT use '-item n'

Volker.

[Volker Halle]

Robert,


P00>>>wwidmgr -quickset -item 45 -unit 777


This command is wrong and the actual cause of your INCONSTATE bugcheck. You were talking about DGA12, so I assume, that the IDENTIFIER of your boot disk is set to 12, so you should have used the following command:

>>> wwidmgr -quickset -udid 12

Then everything would have worked flawlessy...

Clear the existing WWIDMGR variables with >>> WWIDMGR -CLEAR ALL and then use the above command to configure your boot device path.

Volker.

[Robert Jacobs]

I am going to use another disk for this effort and use the following commands



>>> WWIDMGR -CLEAR ALL


>>> wwidmgr -quickset -udid 4


The $1$dga12 or 12 unit was just an example

I will keep you posted

Robert J.

[Robert Jacobs]

I did the following

P00>>>WWIDMGR -CLEAR ALL >>>wwidmgr -quickset -udid 2

This worked fine!


I did another restore of the system disk to the $1$dga2 device and things looked good until the following

EIA0, FastFD mode set by console
%EIA0, Full Duplex 100BaseTX connection selected
%EIA0, Link state change: UP
%SYSINIT-I- waiting to form or join an OpenVMS Cluster
%CNXMAN, Sending VMScluster membership request to system GS160B
%CNXMAN, Now a VMScluster member -- system GS160A
%SYSINIT-E- error locking system device, retrying..., status = 00000840
%SYSINIT-E- error locking system device, retrying..., status = 00000840
%SYSINIT-E- error locking system device, retrying..., status = 00000840

.
.
.
SYSINIT-E- error taking out lock on system disk, status = 00000840

**** OpenVMS (TM) Alpha Operating System V7.3-2 - BUGCHECK ****
dismissing I/O Device Interrupt Number 38, not delivered to CPU 1
waiting for poll to complete pgb0.0.0.1.2
.Poll done

** Bugcheck code = 0000036C: PROCGONE, Process not in system
** Crash CPU: 00 Primary CPU: 00 Active CPUs: 00000033
** Current Process = SYSINIT
** Current PSB ID = 00000001
** Image Name = SYSINIT.EXE

**** Starting compressed selective memory dump at 26-OCT-2005 10:27...
..................................................
...Complete ****

SYSTEM SHUTDOWN COMPLETE


Fun stuff huh?

Any thoughts on this before I try an use H.P. support

Robert J.

[Volker Halle · Accepted solution]

Robert,

there seems to be another node in this cluster (GS160B). It does seem to have the system disk $1$DGA2: allocated, from which you are trying to boot:

%X840 = %SYSTEM-W-DEVALLOC

Maybe you did the COPY ot that disk from the other node and forgot to $ DISM or/and $DEALLOC that disk.

Yeah, it's fun diagnosing crashes with minimum information ;-)

Volker.

[Robert Jacobs]

Hi Volker

Thank you so much for your help


I was a bit ahead of myself again and did forget to dismount and look for some basic gotchas I did need to boot min and edit the startup file and comment out some mount commands. I did notice that even after starting TCP/IP services and on a mount mismatch label of a disk I was not able to telnet or ssh into the system. I did need to boot min and as indicated comment out some mounts.

I guess even after 25+ years with VMS I still am just playing around compared to you folks that are very strong on internals etc...

Thanks again

Robert J.