Operating System - OpenVMS
1829116 Members
2524 Online
109986 Solutions
New Discussion

Re: ES80+MSA1000 Bugcheck

 
Enemy
Advisor

ES80+MSA1000 Bugcheck

ES80 Model 4 connected thru SAN Switch 8/EL bugcheks with message "Inconsistency I/O Data base" while booting from MSA1000. Botting same OS from local SCSI works fine. VMS 7.3-2+Patches.
8 REPLIES 8
Willem Grooters
Honored Contributor

Re: ES80+MSA1000 Bugcheck

Just a few hints - not a solution. I'm not a storage guy ;-)

I remember getting this error after ^P on a running system, changing or removing a faulty disk and continue from the console prompt.
This leads me to the following thoughts:
I've seen remarks in this forum that a device might be named differently from what SRM sais by the firmware on the storage controller once the path to the disk has been established. Knowing that boot will hassle around with the system disk (mount, disconnect, mount...) I can imagine that the firmware (either ES80 or MSA1000) will introduce this problem, if the said disk-name changes occur during boot.

There have been some issues on MSA1000 and boot, search the fora on MSA1000. You'll find some VMS and MSA1000 firmare ECO's as well that address this storage device.

HTH

Willem
Willem Grooters
OpenVMS Developer & System Manager
Wim Van den Wyngaert
Honored Contributor

Re: ES80+MSA1000 Bugcheck

Uwe Zessin
Honored Contributor

Re: ES80+MSA1000 Bugcheck

Good hints - make sure that the connections on the MSA have the OpenVMS profile set.
.
Volker Halle
Honored Contributor

Re: ES80+MSA1000 Bugcheck

For an INCONSTATE crash, you first need to figure out which driver/execlet this bugcheck happened in. SDA> CLUE CRASH will tell you. The reference to the other article is misleading, as it is related to SYS$PKQDRIVER.

One of the popular reasons for INCONSTATE bugchecks when booting from fibre channel, is that the Unit Identifier (nn) does not match the console device name (DGcnn). Make sure you've used WWIDMGR -QUICKSET -UDID nn
The above applies, if the crash is in SYS$DKDRIVER and shows R0=00000908

Volker.
Enemy
Advisor

Re: ES80+MSA1000 Bugcheck

MSA has OpenVMS profile
In SRM disk shown as dga17899. In VMS and MSA CLI as $1$dga1. How change SRM device name? Is it possible at all?

wwidmgr -quikset -item 1
Volker Halle
Honored Contributor

Re: ES80+MSA1000 Bugcheck

Yeah, that's the problem:

>>> WWIDMGR -clear all
>>> WWIDMGR -show WWID
>>> WWIDMGR -quickset -udid 1

The console DGA device (DGA1) name must match the Identifier and the device name as seen by OpenVMS ($1$DGA1)

Volker.
Cass Witkowski
Trusted Contributor

Re: ES80+MSA1000 Bugcheck

Sometimes after running WWIDMGR you can see extraneous DGA devices at the >>>SHOW DEVICE command. Make sure you do an INIT after using WWIDMGR to see what you really have.

Cass
Uwe Zessin
Honored Contributor

Re: ES80+MSA1000 Bugcheck

That is normal - they disappear after the INITIALIZE. And after you have run WWIDMGR, you have to INITIALIZE anyway before you can boot. Same if you shutdown and want to run WWIDMGR.
.