first step getting VAX 6000-400 booted ...

Geoff Roberts wrote: > Hmm, Unit 0 has an excellent chance of being a system disk, but

> was > initialised prior to being retired. What's the exact error msg

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.) 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.) > Tapes are probably sus. TK70's are the least reliable component of a

yack! > > I also have a TU81+ and VMS bootable tape on 9-track, maybe that's

> reliable? > > Very likely, do you have the companion card for the TU81+ (KLESI-B) to

> the Vax? > They TU81+ is not SDI, so it won't even plug in to the KDB50. If all

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 and try a couple of SDI accesses, try reading a TK and writing to a TU? > Not very familiar with Ultrix though I gather it's also possible to

> an ultrix box from a vms one, though I don't think it will do vice

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. 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 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 XBI D 1+ DWMBA/B (2107) 000A 2+ KLESI-B (0103) 0006 3+ KDB50 (010E) 142C 6+ DEBNI (0118) 0400 XBI E 1+ DWMBA/B (2107) 000A 3+ DMB32 (0109) 0004 5+ CIBCA-B (0108) 41C2 6+ TBK70 (410B) 0307 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 TAPE /XMI:E /BI:6 CSA1 ETH0 /XMI:D /BI:6 ET0 SHOW DSSI is not yet implemented GS> Now I have loaded the VMS 6.1 stand alone backup TK70 and go: 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. 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? $ 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: 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: 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. 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. thanks, -Gunther -- Gunther_Schadow-------------------------------http://aurora.rg.iupui.edu Regenstrief Institute for Health Care 1050 Wishard Blvd., Indianapolis IN 46202, Phone: (317) 630 7960 schadow(a)aurora.rg.iupui.edu------------------#include <usual/disclaimer>