[Info-vax] Host-Based InfoServer error
JBloggs
JBloggs at acme.com
Thu Dec 3 15:01:16 EST 2009
On Wed, 2 Dec 2009 19:25:05 -0800 (PST), RobertsonEricW
<robertsonericw at netzero.net> wrote:
>On Dec 2, 1:12 am, JBloggs <JBlo... at acme.com> wrote:
>> On Tue, 1 Dec 2009 07:16:37 -0800 (PST), RobertsonEricW
>>
>> <robertsoner... at netzero.net> wrote:
>> >$ LD CONNECT DISK_USERS:[usr.robertson.OpenVMS84FT]I64E84.ISO LDA100:
>> >$ MOUNT/SYSTEM/NOWRITE LDA100: I64084
>> >%MOUNT-I-MOUNTED, I64084 mounted on _SRVR1$LDA100:
>> >$ dir LDA100:[000000]
>> > ...etc..
>> >Total of 272 files.
>> >$ RUN SYS$SYSTEM:ESS$INFOSERVER
>> >InfoServer> CREATE SERVICE I64084 LDA100:
>> >%SYSTEM-F-DEVINACT, device inactive
>>
>> First guess: try a service name not equal to the disk label.
>>
>> (i think you're getting snake-bit by the disk logical created by
>> $MOUNT)
>
>Thanks JBloggs. Unfortunately, choosing a different service name gives
>the same error message as before.
the service name issue, was something I got bit by long ago.
here are notes (verbatim), I made the last time around
I don't see that you're doing anything fundamentally different.
(i adopted a cargo-cult belief inre the startup order of
the various last/lad/infoserver startups. below, is what
worked for me ...)
Cloning the I64 8.3 dvd install disk:
the *.bck from the *.bck-gz needs:
$ set file/attrib=(rfm:fix,rat:none,lrl:32256,mrs:32256)
$ ld connect/log DKA100:[000000]$$$I64SA.SYS LDA65:
$ init/.../GPT LDA65: I64
$ set boot /blocksize=512 /I64 LDA65:
$ mcr sys$setboot -s -f LDA65:
$ back/image/noinit/...
Similar for I64 sys$update:STABACKIT.com
but note that WLKSYSDSK needs to be changed to 1 (write-locked)
SYSGEN> USE LDA65:[SYSE.SYSEXE]IA64VMSSYS.PAR
SYSGEN> SHOW WLKSYSDSK
Parameter Name Current Default Min. Max.
Unit Dynamic
-------------- ------- ------- ------- -------
---- -------
WLKSYSDSK 0 0 0 1
Boolean
SYSGEN> SET WLKSYSDSK 1
SYSGEN> WRITE LDA65:[SYSE.SYSEXE]IA64VMSSYS.PAR
1. $ mount/system/noassist/foreign -
....LDA65: I64SA I64SA ! s/a needs write access
2. $ edit sys$startup:ess$last_startup.dat
......a. comment all_controllers = ON
......b. add DEVICE = (EIB) ! or EWA, etc
3. $ subm/noprint/user=SYSTEM/log=sys$manager-
....sys$startup:ess$last_startup.com
4. $ subm/noprint/user=SYSTEM/log=sys$manager-
....sys$startup:ess$lad_startup.com
5. $ subm/noprint/user=SYSTEM/log=sys$manager-
..../param=("DISK") sys$startup:ess$startup.com
6. $ mcr ess$infoserver create service IA64SA LDA65:
7. $ mcr ess$ladcp show service
....Interrogating network for Disk services, please wait...
....Disk services offered by node XX -
....(LAD V3.1, Address: 08-00-2B-86-86-3E)
.... Current Writes
....Service: Device: Rating: Connects: Allowed?:
....I64083 OpenVMS 65472 1 No
and. then,. the network booting is another can of worms ...
...
Please select a boot option
OpenVMS 8.3, DKA0, flags: 0,0
OpenVMS 8.3, DKA100, flags: e,0 PKA0.1
EFI Shell [Built-in]
NIC2
NIC1, 10/100
Boot Option Maintenance Menu
System Configuration Menu
Use ^ and v to change option(s). Use Enter to select an option
Loading.: NIC1, 10/100
Running LoadFile()
CLIENT MAC ADDR: 00 30 6E 39 E6 FE
CLIENT IP: 10.0.0.2 MASK: 255.0.0.0 DHCP IP: 0.240.0.0
Running LoadFile()
Starting: NIC1, 10/100
Loading file: TCPIP$TFTP_ROOT:[V83SA]IPB.EXE from IP 10. 0. 0. 1
%IPB-I-SUCCESS, HP OpenVMS IPB version V8.3 successfully loaded.
%EIA-I-BOOTDRIVER, Starting auto-negotiation
%EIA-I-BOOTDRIVER, Link partner not auto-negotiation capable, used
parallel detection
%EIA-I-BOOTDRIVER, Auto-negotiation selected 100BaseTX HDX
Network Initial System Load Function
Version 1.2
FUNCTION FUNCTION
ID
1 - Display Menu
2 - Help
3 - Choose Service
4 - Select Options
5 - Stop
Enter a function ID value: 3
OPTION OPTION
ID
1 - Find Services
2 - Enter known Service Name
Enter an Option ID value: 1
Working
Servers found:: 1
Services offered by node XX, Address: 08-00-2B-86-86-3E
# 1 IA64SA
Enter a Service Number: 1
HP OpenVMS Industry Standard 64 Operating System, Version V8.3
© Copyright 1976-2007 Hewlett-Packard Development Company, L.P.
%EIA-I-BOOTDRIVER, Starting auto-negotiation
%EIA-I-BOOTDRIVER, Link partner not auto-negotiation capable, used
parallel detection
%EIA-I-BOOTDRIVER, Auto-negotiation selected 100BaseTX HDX
%EIA0, Auto-negotiation mode assumed set by console
%EIA0, Auto-negotiation started, advertising 100BaseTX Full Duplex,
Flow Control
%SMP-I-CPUTRN, CPU #01 has joined the active set.
%EIA0, Link partner not auto-negotiation capable, using parallel
detection
%EIA0, Half Duplex 100BaseTX connection selected, TX flow control
%SYSINIT-E- error reading TDF file, status = 00000910
%SYSINIT-I- run SYS$MANAGER:UTC$TIME_SETUP.COM to set time
differential factor
More information about the Info-vax
mailing list