----- Original Message -----
From: "ajp166" <ajp166_at_bellatlantic.net>
To: <classiccmp_at_classiccmp.org>
Sent: Thursday, October 25, 2001 8:27 AM
Subject: Re: first step getting VAX 6000-400 booted ...
> OK, the default boot device (a SET option) is either dead
> or not found.
>
> Allison
Yup. I missed the original of his response to my questions so I'll go thru
it now.
> -----Original Message-----
> From: Gunther Schadow <gunther_at_aurora.regenstrief.org>
> To: classiccmp_at_classiccmp.org <classiccmp_at_classiccmp.org>
> Date: Wednesday, October 24, 2001 12:19 PM
> Subject: Re: first step getting VAX 6000-400 booted ...
> >I don't have the console dump on that, but the only error message
> >I recollect was:
> >
> >?3 Device I/O Error (or something very similar.)
Ok, it's not talking to whatever the boot device is supposed to be.
> >Would that be the appropriate response on an RA90 drive with
> >wiped-out media? My drive completed all tests, including the
> >spun-down and the spun-up tests (the latter includes disk
> >access tests.)
Seems to be at a physical level. Something is not working.
I don't think I've used a TK70 to do anything since I got the machines.
About the only thing it's useful for is for CPU EEPROM settings.
> >> Very likely, do you have the companion card for the TU81+ (KLESI-B) to
Ok saw that in the list. Tick in the box, so your TU81 should work.
> >Instructions on how to write an Ultrix tape from VMS would
> >be cool. I'm sure I can get VMS up. What is the least
> >amount of knowledge that I need to get a VMS system up
> >in single user mode
We'll cross that one when we get there, we need to sort this IO problem out
first.
You will need to do a conversational boot from disk if you don't have the
system password, (assuming it's
got an OS on the drive.)
One other possibility, the RA9x displays all 0's if the drive number is
unconfigured. Set it to 1 (the how to is in the
manual Antonio sent me, and I think I saw you in the CC) and boot from DU1
and see if that works.
The boot command should look like this
>>> SET BOOT CONV /R5:1 /XMI:D /BI:3 DU1
(You need the key in the UPDATE position for this)
Then you can try and boot the machine from the disk.
>>> BOOT CONV
http://eisner.decus.org/vms/faq.htm is the VMS FAQ, strongly recommend
getting this.
MGMT5 details conversational boot and the procedure for lost passwords.
Quote as follows.
1.. Halt the system. Exactly how this is done depends on the specific
system model: Depending on the model, this can involve pressing the HALT
button, entering CTRL/P on the console, or pressing the BREAK key on the
console.
2.. At the >>> console prompt, use a console command to boot into the
SYSBOOT> utility. (SYSBOOT allows conversational changes to system
parameters.) The syntax for the conversational bootstrap varies by system
model - this typically involves specifying a flag of 1, for example:
VAX:
B/1
B/R5:1
_at_GENBOO
Alpha:
b -flags 0,1
If your system has a non-zero system root (such as root SYSE, shown here),
you will have to use a console command such as the following:
VAX:
B/E0000001
B/R5:E0000001
_at_<console media procedure name varies widely>
Alpha:
b -flags e,1
If your system has a hardware password (various systems support a password
that prevents unauthorized access to the console), you will need to know
theis password and will need to enter it using the LOGIN command at the
console. If you get an Inv Cmd error trying to perform a conversational
bootstrap, and you do not have the hardware console password for the console
LOGIN command, you are stuck - you will need to call for hardware service in
order to reset the hardware console password. The syntax used for the
console password mechanism varies.
3.. Once at the SYSBOOT> prompt, request that OpenVMS read the system
startup commands directly from the system console, that the window system
(if any) not be started, and that OpenVMS not record these parameter changes
for subsequent system reboots:
SET/STARTUP OPA0:
SET WINDOW_SYSTEM 0
SET WRITESYSPARAMS 0
CONTINUE
4.. At the $ prompt, the system will now be accepting startup commands
directly from the console. Type the following two DCL commands:
SPAWN
_at_SYS$SYSTEM:STARTUP
The result of these two commands will be the normal system startup, but
you will be left logged in on the console, running under a privileged
username. Without the use of the SPAWN command, you would be logged out when
the startup completes.
If necessary, you can skip the invocation of the system startup
temporarily, and perform tasks such as registering license PAKs or various
other "single-user" maintenance operations.
5.. Use the following commands to reset the SYSTEM password:
SET DEFAULT SYS$SYSTEM: ! or wherever SYSUAF.DAT resides
RUN SYS$SYSTEM:AUTHORIZE
MODIFY SYSTEM /PASSWORD=newpassword
EXIT
6.. These steps will change the SYSTEM password to the specified new
newpassword password value. Reboot the system normally - the SYSTEM password
should now be set to the value you specified in Step 5. Some people will
suggest a method using the UAFALTERNATE SYSGEN parameter. This approach is
not always reliable and is not recommended, as there can easily be an
alternate user authorization file configured on the system. For further
information on emergency startup and shutdown, as well as for the official
OpenVMS documentation on how to change the SYSTEM password from the console
in an emergency, please see the OpenVMS System Manager's Manual in the
OpenVMS documentation set.
You can also use the conversational bootstrap technique shown above (the
steps through Step 3) to alter various system parameters. At the SYSBOOT>
prompt, you can enter new parameters values:
SHOW MAXPROCESSCNT
SET . 64
CONTINUE
The "." is a shorthand notation used for the last parameter examined.
> >It definitely is as the source code says. I'll use my FreeBSD
> >laptop as the boot host. Monitoring with tcpdump is a good way
> >of debugging network booting.
Yup. That'll work if we have to.
> >Attached below you'll find annotated console dumps from my
> >yesterday's attempts (thanks to xterm :-)
> >
> >My comments are lines starting with "GS>"
> >
> >GS> I have swapped in another TK70 drive (one that may be less worn)
> >GS> and now I turn on the machine:
> >
> >#123456789 0123456789 0123456789 01234567#
> >
> >F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE #
> > A A . A M M M M P P P P P P
> >TYP
> > o o . + + + + + + + + + + +
> >STF
> > . . . . . . . . E E E E E B
> >BPD
> > . . . . . . . . + + + + + +
> >ETF
> > . . . . . . . . E E E E E B
> >BPD
> >
> >
> >. . . . . . . . . + . . + + + . XBI D
> >+
> >. . . . . . . . . + + . + . + . XBI E
> >+
> >
> > . . . . A4 A3 A2 A1 . . . . . .
> >ILV
> > . . . . 128 128 128 128 . . . . . . 512
> >Mb
> >
> >ROM0 = V4.00 ROM1 = V4.00 EEPROM = 2.03/4.02 SN = AG94408887
> >
> >
> >>>> SHOW ALL
> > Type Rev
> > 1+ KA64A (8082) 000D
> > 2+ KA64A (8082) 000D
> > 3+ KA64A (8082) 000D
> > 4+ KA64A (8082) 000D
> > 5+ KA64A (8082) 000D
> > 6+ KA64A (8082) 000D
> > 7+ MS65A (4001) 0084
> > 8+ MS65A (4001) 0084
> > 9+ MS65A (4001) 0084
> > A+ MS65A (4001) 0084
> > B+ KDM70 (0C22) 2811
> > D+ DWMBA/A (2001) 0002
> > E+ DWMBA/A (2001) 0002
Ok, so it's a 6 CPU system and 4 x 128Mb MS65A's. Nice.
> > XBI D
> > 1+ DWMBA/B (2107) 000A
> > 2+ KLESI-B (0103) 0006
> > 3+ KDB50 (010E) 142C
> > 6+ DEBNI (0118) 0400
KLESI for the TU81+, KDB50 for the SDI drives, Ethernet
> > XBI E
> > 1+ DWMBA/B (2107) 000A
> > 3+ DMB32 (0109) 0004
> > 5+ CIBCA-B (0108) 41C2
> > 6+ TBK70 (410B) 0307
DMB32 8 x Serial for terms. Plus a couple of strange parallel ports on a
single 50(?) pin d connector that I have never
found anything compatible with. Someone suggested it was a "Data Products"
Parallel port x 2, whatever that is.
Antonio or Allison, either of you know what you can use with it?
CIBCA-B for speaking to HSC's or other CI equipped Vaxen. If you don't have
a HSC, pull the cards, as some of your error msgs that are confusing the
issue are coming from there. LEave the cab kit in in case you want to put
them back later if you get something that speaks CI. (Caveat: If you do you
MUST have a Star Coupler as well)
Controller for the TK70
> > Current Primary: 1
> > /NOENABLED-
> > /NOVECTOR_ENABLED-
> > /NOPRIMARY-
> >F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE #
> > . . . . A4 A3 A2 A1 . . . . . .
> >ILV
> > . . . . 128 128 128 128 . . . . . . 512
> >Mb
> > /INTERLEAVE:DEFAULT
> > /SCOPE /SPEED: 9600 /BREAK
> > English
> > XMI:D BI:6 08-00-2B-34-A5-CA
> > DEFAULT /XMI:E /BI:6 CSA1
Default boot is from the TK70
> > TAPE /XMI:E /BI:6 CSA1
Tape boot is from the TK70
> > ETH0 /XMI:D /BI:6 ET0
ETH boot is from the Ethernet.
None of these will attempt a boot from the KLESI or the KDB50
> >SHOW DSSI is not yet implemented
> >
> >GS> Now I have loaded the VMS 6.1 stand alone backup TK70 and go:
> >
> >>>> BOOT /XMI:E /BI:6 CSA1
> >Initializing system.
> >
> >#123456789 0123456789 0123456789 01234567#
> >
> >F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE #
> > A A . A M M M M P P P P P P
> >TYP
> > o o . + + + + + + + + + + +
> >STF
> > . . . . . . . . E E E E E B
> >BPD
> > . . . . . . . . + + + + + +
> >ETF
> > . . . . . . . . E E E E E B
> >BPD
> >
> >
> >. . . . . . . . . + . . + + + . XBI D
> >+
> >. . . . . . . . . + + . + . + . XBI E
> >+
> >
> > . . . . A4 A3 A2 A1 . . . . . .
> >ILV
> > . . . . 128 128 128 128 . . . . . . 512
> >Mb
> >
> >ROM0 = V4.00 ROM1 = V4.00 EEPROM = 2.03/4.02 SN = AG94408887
> >
> >
> >Loading system software.
> >
> > OpenVMS VAX Version V6.1 Major version id = 1 Minor version id =
> >0c
> >PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 23-OCT-2001
> >
> >Configuring devices . . .
> >
> >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280
> >
> >%PAA0, Port is Reinitializing ( 49 Retries Left). Check the Error Log.
> >
> >GS> oops, what is %PAA0? Something is bad, but what?
> >GS> as you might expect, it gives above error message for each
> >GS> retry 48, 47, 46, ... will not show those here. But there
> >GS> is also other stuff, as if I'm already running multi-tasked.
This is coming from the CIBCA because it's not terminated. Pull the CIBCA
cards out or it will annoy you to death.
> >Now configuring HSC, RF, and MSCP-served devices . . .
> >
> >GS> and on with the %PAA0 reinitializations down to 24
> >
> >%PAA0, Port is Reinitializing ( 24 Retries Left). Check the Error Log.
> >
> >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280
> >
> >Please check the names of the devices which have been configured,
> >to make sure that ALL remote devices which you intend to use have
> >been configured.
> >
> >If any device does not show up, please take action now to make it
> >available.
> >
> >GS> in a hurry I power up the RA90 hooked to the KDB50 and
> >spin it up
> >
> >Available device MUC6: device type TK70
> >%PAA0, Port is Reinitializing ( 23 Retries Left). Check the Error Log.
> >
> >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280
> >
> >GS> ...
> >
> >%PAA0, Port is Reinitializing ( 9 Retries Left). Check the Error Log.
> >
> >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280
> >
> >
> >Enter "YES" when all needed devices are available:
> >%PAA0, Port is Reinitializing ( 8 Retries Left). Check the Error Log.
> >
> >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280
> >
> >
> >Enter "YES" when all needed devices are available:
> >%PAA0, Port is Reinitializing ( 7 Retries Left). Check the Error Log.
> >
> >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280
> >
> >
> >Enter "YES" when all needed devices are available:
> >%PAA0, Port is Reinitializing ( 6 Retries Left). Check the Error Log.
> >
> >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280
> >
> >
> >Enter "YES" when all needed devices are available:
> >%PAA0, Port is Reinitializing ( 5 Retries Left). Check the Error Log.
> >
> >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280
> >
> >
> >Enter "YES" when all needed devices are available:
> >%PAA0, Port is Reinitializing ( 4 Retries Left). Check the Error Log.
> >
> >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280
> >
> >
> >Enter "YES" when all needed devices are available:
> >%PAA0, Port is Reinitializing ( 3 Retries Left). Check the Error Log.
> >
> >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280
> >
> >
> >Enter "YES" when all needed devices are available:
> >%PAA0, Port is Reinitializing ( 2 Retries Left). Check the Error Log.
> >
> >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280
> >
> >
> >Enter "YES" when all needed devices are available:
> >%PAA0, Port is Reinitializing ( 1 Retries Left). Check the Error Log.
> >
> >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280
> >
> >
> >Enter "YES" when all needed devices are available:
> >%PAA0, Port is Reinitializing ( 0 Retries Left). Check the Error Log.
> >
> >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280
> >
> >
> >Enter "YES" when all needed devices are available:
> >%PAA0, Port is going Offline.
> >
> >
> >Enter "YES" when all needed devices are available: yes
> >%BACKUP-I-IDENT, Stand-alone BACKUP V6.1; the date is 23-OCT-2001
> >00:03:52.13
> >$
> >
> >GS> yea! a prompt! we made it. But what's next?
This would be where you enter backup commands, SA backup is purely that,
it's a self booting backup.
Ok, couple of things are clear.
1) Lose the CI stuff for now.
2) It's not seeing any other devices (it should give you a list of things it
sees apart from the boot device)
ie TU81 or (importantly) the RA9x drive(s) so you need to check
connectivity, device function etc.
I think you may have a bad cable or something.
> >$ help
> >%CLI-W-IVVERB, unrecognized command verb - check validity and spelling
> > \HELP\
> >
> >GS> ah I give up, I want to see Ultrix up, may be that new
> >GS> drive did it? Hit the reset button, system initializes
> >GS> same as above, swap in the Ultrix TK and go:
> >
> >>>> BOOT /XMI:E /BI:6 CSA1
> >Initializing system.
> >
> >#123456789 0123456789 0123456789 01234567#
> >
> >F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE #
> > A A . A M M M M P P P P P P
> >TYP
> > o o . + + + + + + + + + + +
> >STF
> > . . . . . . . . E E E E E B
> >BPD
> > . . . . . . . . + + + + + +
> >ETF
> > . . . . . . . . E E E E E B
> >BPD
> >
> >
> >. . . . . . . . . + . . + + + . XBI D
> >+
> >. . . . . . . . . + + . + . + . XBI E
> >+
> >
> >
> > . . . . A4 A3 A2 A1 . . . . . .
> >ILV
> > . . . . 128 128 128 128 . . . . . . 512
> >Mb
> >
> >ROM0 = V4.00 ROM1 = V4.00 EEPROM = 2.03/4.02 SN = AG94408887
> >
> >
> >Loading system software.
> >%BOOT-F-Insufficient memory for CI
> >?06 Halt instruction executed in kernel mode.
> > PC = 0000040Fc
> > SAVPSL = 041F0600
> > ISP = 00000200
> >
> >Bootstrap failed due to previous error.
> >>>>
> >
> >
> >GS> this is that CI problem. Now I turn off machine again and
> >GS> remove CI cards. I do have HSC90s to go with it and I definitely
> >GS> want to run CI, but for now I'll start easy. So, power up
> >GS> again. Wait for one initialization again, then:
> >
> >>>> BOOT /XMI:E /BI:6 CSA1
> >Initializing system.
> >
> >#123456789 0123456789 0123456789 01234567#
> >
> >F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE #
> > A A . A M M M M P P P P P P
> >TYP
> > o o . + + + + + + + + + + +
> >STF
> > . . . . . . . . E E E E E B
> >BPD
> > . . . . . . . . + + + + + +
> >ETF
> > . . . . . . . . E E E E E B
> >BPD
> >
> >
> >. . . . . . . . . + . . + . + . XBI D
> >+
> >. . . . . . . . . + . . + + + . XBI E
> >+
> >
> > . . . . A4 A3 A2 A1 . . . . . .
> >ILV
> > . . . . 128 128 128 128 . . . . . . 512
> >Mb
> >
> >ROM0 = V4.00 ROM1 = V4.00 EEPROM = 2.03/4.02 SN = AG94408887
> >
> >
> >Loading system software.
> >
> >?06 Halt instruction executed in kernel mode.
> > PC = 00280200c
> > SAVPSL = 041F0600
> > ISP = 00280000
> >
> >Bootstrap failed due to previous error.
> >>>>
> >
> >GS> here ends my console dump.
I have a suspicion that Ultrix doesn't support more than 4 CPU's (nor do VMS
versions prior to 6.??1??2 - I forget)
Either that or the ultrix tape is iffy.
> >If it weren't for the many heavy items I still have to
> >shuffle, disassemble, lift and reassemble, I could go mad
> >about the Ultrix folks who have neglected to put
> >some explanatory printf into the boot code before
> >the halt call. It could be so much easier if we knew what
> >the problem is.
Indeed. I've located what appears to be a full set of Ultrix books in one
of the sheds at home, I'll see if I can find the appropriate stuff tonight.
In the meantime you need to find out why the SA Backup can't see your RA9x
drives. Once you solve that, you can try booting from DUA0: on the KDB50
and see what if anything is on there, but at the moment it doesn't seem to
see the device.
Leave the CI stuff (make sure you pull BOTH cards) out for now, or connect
it to a star coupler so it stops bitching at you.
Hope this helps
Geoff Roberts
Computer Systems Manager
Saint Mark's College
Port Pirie, South Australia
geoffrob_at_stmarks.pp.catholic.edu.au
ICQ 1970476
Received on Wed Oct 24 2001 - 20:33:02 BST