| Author |
Installation on AS600: Crash while configuring I/O board |
ItsMeOnly
Member
Posts: 30
Joined: 13.02.07 |
| Posted on February 27 2007 18:26 |
|
|
Well, tried to install OpenVMS on my... khmmm... resurrected AlphaStation (see my post on comp.sys.dec), but PKQDRIVER bails out:
[code:1:9f9d412ecf]PKQDRIVER-W- PKB0, Port Shutdown due to numerous or serious ctrlr errors.[/code:1:9f9d412ecf]
Then there's BUGCHECK with the message[code:1:9f9d412ecf]INCONSTATE, Inconsistent I/O database[/code:1:9f9d412ecf]
Grepped in groups that it might be because VMS is issuing commands the I/O
controller doesn't understand. What can I do?
Rambo |
    |
| Author |
|
HobbyistOne
Super Administrator
Posts: 126
Location: Plano, TX
Joined: 20.02.08 |
| Posted on February 27 2007 23:22 |
|
|
|
Sounds like it's an unsupported controller. What does a SHOW DEVICE provide for the details for your controllers? |
|
|
| Author |
|
ItsMeOnly
Member
Posts: 30
Joined: 13.02.07 |
| Posted on February 28 2007 09:55 |
|
|
[quote:831b907bb8="HobbyistOne"]Sounds like it's an unsupported controller. What does a SHOW DEVICE provide for the details for your controllers?[/quote:831b907bb8]
[code:1:831b907bb8]DKB0.0.0.1002.0 DKB0 RZ1CC-BA 883F
DKB500.5.0.1002.0 DKB500 RRD45 1645
[... snip CPU and EWA-C]
PKA0.7.0.1001.0 PKA0 SCSI Bus ID 7 5.57
PKA0.7.0.1002.0 PKB0 SCSI Bus ID 7 5.57[/code:1:831b907bb8]
There you go- there was also a Symbios Logic SE SCSI card, but it's now removed and the thing doesn't change anything. |
|
|
| Author |
|
HobbyistOne
Super Administrator
Posts: 126
Location: Plano, TX
Joined: 20.02.08 |
| Posted on February 28 2007 10:07 |
|
|
What's connected to PKB0? Is it properly terminated?
SCSI requires a termination at both ends of the bus, though typically, the controller provides the termination of that end of the bus. With a BA35X, there is a terminator block inside the case (which can be moved to provide a split bus, or removed for an unterminated bus for chaining to other devices. |
|
|
| Author |
|
ItsMeOnly
Member
Posts: 30
Joined: 13.02.07 |
| Posted on February 28 2007 14:44 |
|
|
Big update
-----------------------------------------------------------------------------------------
The good news is that after switching cables (PKB to PKA), the VMS installation ran smoothly. My question is now: how will the system react on drastic hardware downgrade (EV5->EV4, AS600->DEC2000/300). |
|
|
| Author |
|
imiller
Administrator
Posts: 277
Location: UK
Joined: 24.02.06 |
| Posted on March 08 2007 06:04 |
|
|
|
you can take an image backup of that system and run it on a older system and often it can be fine. |
|
|
| Author |
Downgrades are okay |
HobbyistOne
Super Administrator
Posts: 126
Location: Plano, TX
Joined: 20.02.08 |
| Posted on March 08 2007 08:46 |
|
|
|
OpenVMS is famously backward compatible. If your new hardware is running OpenVMS, the same disk image will run on older hardware, too. The only likely gotchas are going to be disk device naming, but logicals can take care of that! |
|
|
| Author |
Re: Downgrades are okay |
ItsMeOnly
Member
Posts: 30
Joined: 13.02.07 |
| Posted on March 13 2007 16:55 |
|
|
[quote 1d85574e8="HobbyistOne"]OpenVMS is famously backward compatible. If your new hardware is running OpenVMS, the same disk image will run on older hardware, too. The only likely gotchas are going to be disk device naming, but logicals can take care of that![/quote1d85574e8]
Turns out Jensen is an exception again 
Got VMS running on an 2 Gig WD disk, installed filesets, and removed the thing after reboot, before AUTOGEN- after putting it into Jensen GETDATA runs ok, but GENPARAMS stage bails out with a nasty error about "inproperly handled condition" (hard to see- scrolls too fast). |
|
|
| Author |
|
HobbyistOne
Super Administrator
Posts: 126
Location: Plano, TX
Joined: 20.02.08 |
| Posted on March 13 2007 22:52 |
|
|
That's probably one of the tools for gathering feedback and such. If you can, catch the output of AUTOGEN with:
$ @SYS$UPDATE:AUTOGEN <start> <end> /OUTPUT=AUTOGEN.LOG
That should log the output of the failure, and hopefully track it down. Hopefully, it's just a bug in the feedback stuff, and you can avoid that with ading "NOFEEDBACK" as a third arguement to AUTOGEN |
|
|
| Author |
|
ItsMeOnly
Member
Posts: 30
Joined: 13.02.07 |
| Posted on March 14 2007 05:08 |
|
|
[quote:ff7b317ac0="HobbyistOne"]That's probably one of the tools for gathering feedback and such. If you can, catch the output of AUTOGEN with:
$ @SYS$UPDATE:AUTOGEN <start> <end> /OUTPUT=AUTOGEN.LOG
That should log the output of the failure, and hopefully track it down. Hopefully, it's just a bug in the feedback stuff, and you can avoid that with ading "NOFEEDBACK" as a third arguement to AUTOGEN[/quote:ff7b317ac0]
You'll unfortunately have to tell me how to do that , I'm getting "process logged out" message and stats- but no prompt  |
|
|
| Author |
|
imiller
Administrator
Posts: 277
Location: UK
Joined: 24.02.06 |
| Posted on March 14 2007 07:05 |
|
|
try
$ @SYS$UPDATE:AUTOGEN GETDATA TESTFILES NOFEEDBACK |
|
|
