Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Operating System - Tru64 Unix
cancel
Showing results for 
Search instead for 
Did you mean: 

tru64 bootdev problems

victory_1
Advisor

tru64 bootdev problems

P00 test>>>show boot*
boot_dev dkb100.1.0.3.0
boot_file
boot_osflags A
boot_reset ON
bootdef_dev dkb100.1.0.3.0
booted_dev
booted_file
booted_osflags
P00 test>>>sh dev
polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1 SCSI Bus ID 7
dka500.5.0.1.1 DKA500 RRD45 1645
polling floppy0 (FLOPPY) PCEB - XBUS hose 0
dva0.0.0.1000.0 DVA0 RX23
polling isp0 (QLogic ISP10X0) slot 3, bus 0 PCI, hose 0 SCSI Bus ID 7
dkb100.1.0.3.0 DKB100 RZ29B 0016
dkb200.2.0.3.0 DKB200 RZ29B 0016
dkb300.3.0.3.0 DKB300 RZ29B 0016
dkb400.4.0.3.0 DKB400 RZ29B 0016
dkb500.5.0.3.0 DKB500 RZ29B 0016
dkb600.6.0.3.0 DKB600 RZ29B 0016
polling kgpsa0 (KGPSA-C) slot 5, bus 0 PCI, hose 0 kgpsaa0.0.0.5.0 - Nvram read failed.

kgpsaa0.0.0.5.0 PGA0 WWN 2000-0000-c92f-2950
polling tulip0 (DECchip 21140-AA) slot 3, bus 0 PCI, hose 1
ewa0.0.0.3.1 00-00-F8-04-F5-B9 FastFD (Full Duplex)
polling tulip1 (DECchip 21140-AA) slot 4, bus 0 PCI, hose 1
ewb0.0.0.4.1 00-00-F8-06-08-43 FastFD (Full Duplex)

This is the output of sh dev and show boot*

When I do a set ewa0_protocols bootp
it says nvironment variable ewa0_protocols created

Then I give show boot* and it should show me

boot_dev as ewa0 but it is not changing.

Anyway to change this to boot through ewa0.

Thanks
11 REPLIES
Venkatesh BL
Honored Contributor

Re: tru64 bootdev problems

Are you saying that you are not to use 'set boot_dev ewa0'?

What about '>>> b ewa0' does that do a network boot?
victory_1
Advisor

Re: tru64 bootdev problems

P00 test>>>show boot*
boot_dev dkb100.1.0.3.0
boot_file
boot_osflags A
boot_reset ON
bootdef_dev dkb100.1.0.3.0
booted_dev dkb100.1.0.3.0
booted_file
booted_osflags A

When I do set boot_dev ewa0 it gives me this
message:
P00 test>>>set boot_dev ewa0
boot_dev protected from attempted operation

Yes I am able to boot through network and i have attached the same in a txt file

Thanks
Ivan Ferreira
Honored Contributor

Re: tru64 bootdev problems

Post the output of

>> show ew*
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Mark Poeschl_2
Honored Contributor

Re: tru64 bootdev problems

What exactly are you trying to accomplish? If you want to change the default boot device to ewa0 use:

>>> set bootdef_dev ewa0

If you want to do a one-time boot from ewa0 use:

>>> boot ewa0 -fl

Why would you expect changing the 'ewa0_protocol' (Note: no 's' at the end) variable to have any effect on the 'boot*' variables?

victory_1
Advisor

Re: tru64 bootdev problems

I am configuring one machine as the RIS server and one more machine as client.

Here are also some inputs on the client from the prompt like sh device , show boot* .

After adding the client to the RIS server I go to the client and give at the # prompt

# shutdown â h now and it takes me to the >>> prompt

I do the following commands to boot from the network



>>> init

>>> set ewa0_protocols bootp

>>> boot ewa0



After I boot through ewa0 I get the errors which I have attached in the txt file bootlogtru-cd-dev2.txt



P00 tru-cd-dev2>>>sh device

polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1 ø SCSI Bus ID 7

dka500.5.0.1.1 DKA500 RRD45 1645

polling floppy0 (FLOPPY) PCEB - XBUS hose 0

dva0.0.0.1000.0 DVA0 RX23

polling isp0 (QLogic ISP10X0) slot 3, bus 0 PCI, hose 0 SCSI Bus ID 7

dkb100.1.0.3.0 DKB100 RZ29B 0016

dkb200.2.0.3.0 DKB200 RZ29B 0016

dkb300.3.0.3.0 DKB300 RZ29B 0016

dkb400.4.0.3.0 DKB400 RZ29B 0016

dkb500.5.0.3.0 DKB500 RZ29B 0016

dkb600.6.0.3.0 DKB600 RZ29B 0016

polling kgpsa0 (KGPSA-C) slot 5, bus 0 PCI, hose 0 kgpsaa0.0.0.5.0 - Nvram read failed.



kgpsaa0.0.0.5.0 PGA0 WWN 2000-0000-c92f-2950

polling tulip0 (DECchip 21140-AA) slot 3, bus 0 PCI, hose 1

ewa0.0.0.3.1 00-00-F8-04-F5-B9 FastFD (Full Duplex)

polling tulip1 (DECchip 21140-AA) slot 4, bus 0 PCI, hose 1

ewb0.0.0.4.1 00-00-F8-06-08-43 FastFD (Full Duplex)



P00 tru-cd-dev2>>>sh boot*

boot_dev dkb100.1.0.3.0

boot_file

boot_osflags

boot_reset ON

bootdef_dev dkb100.1.0.3.0

booted_dev dkb100.1.0.3.0

booted_file

booted_osflags
Aaron Biver_2
Frequent Advisor

Re: tru64 bootdev problems


The point at which the boot is failing indicates a failure of the remote client to send a [second] bootp request to the host. This is to get datafiles necessary for the boot.

If you set the SRM variable boot_osflags to "ba" on the client, it should print a few more messages here that might indicate the source of the problem.

Also, I suggest you run the BOOTP server with debug flags. If you are using joind, try running i in foreground mode with debug flags, such as:

joind -d5 -f

(not sure about the debug level, so experiment)
Mark Poeschl_2
Honored Contributor

Re: tru64 bootdev problems

Also, the correct variable name is "ewa0_protocol" not "ewa0_protocols"

That's why you're getting that "environment variable ewa0_protocols created" message.
victory_1
Advisor

Re: tru64 bootdev problems

Hello all

I have tried all options as replied to me.

But no luck. Well this is a simple thing I am trying but do not understand why it should be so difficult.Any ideas and commnents please
help

Regards
Aaron Biver_2
Frequent Advisor

Re: tru64 bootdev problems

Hi victory,

By the way, booting over the network is not a simple thing.

You said "no luck"...

...but the joind options I suggested were not given to resolve the problem, but to get additional information about the network activity. This is important because you are having a network problem - most likley in the configuration of the server software.

Would you please post the joind debug messages, if any, that occurred at the time the clinet tried to boot?


victory_1
Advisor

Re: tru64 bootdev problems

Hello all

This issue has been resolved , the problem was with the kernel and patches .

HP recommended to install

T64V51BB26AS0005-20050502 patch kit and also

put 51BPK5_genvmunix kernel.

Thanks

Venkatesh BL
Honored Contributor

Re: tru64 bootdev problems

Hmm...little strange. Not sure how an OS patch could solve a problem on the '>>>' prompt...anyways, all is well that ends well!