vpar boot fails

[fizan]

Hi Experts:

I have created a new V-par form a running V-par & issued vparstatus new vpar it's fine.

2. Next i booted the new v-par with the ignite tape taken from the running v-par.

3. To see the booting mode, when i logged into the GSP it shows the following:

MP MAIN MENU:

CO: Consoles
VFP: Virtual Front Panel
CM: Command Menu
CL: Console Logs
SL: Show Event Logs
FW: Firmware Update
HE: Help
X: Exit Connection

[rp7440_1] MP> co

Partitions available:

# Name
--- ----
0) Partition 0
Q) Quit

Please select partition number: 0


Connecting to OS Console: Partition 0

(Use to return to main menu.)


- - - - - - - - - - Prior Console Output - - - - - - - - - -

If this is the case, you will need to either change the terminal type
set in the firmware via GSP (if your GSP firmware version supports
this feature), or change your terminal emulation to match the
firmware. In either case you will need to restart if your terminal and
the firmware terminal type do not match.
Press the 'b' key if you want to reboot now.
Recovery tape created from system: dptest1 on Fri Apr 15 12:54:14 2011



(Press any key to continue.)

- - - - - - - - - - - - Live Console - - - - - - - - - - - -

============= It gets hunged after this========

then normal ctrl-A dosent works, if i gove ctrl-B it comes back to main menu::

Model:: rp7440.
OS: 11.23

Thanks

[fizan]

vparstatus -p hptest3 -v

[Virtual Partition Details]
Name: hptest3
State: Load
OS Version: Unknown
Attributes: Dynamic,Autoboot,Nosearch
Kernel Path: /stand/vmunix
Boot Opts:



# vparstatus -p hptest3 -v
[Virtual Partition Details]
Name: hptest3
State: Boot
OS Version: B.11.23
Attributes: Dynamic,Autoboot,Nosearch
Kernel Path: /stand/vmunix
Boot Opts:

After this no symbol of OS login::

[Torsten. · Accepted solution]

The complete message is likely


NOTE:
The console firmware terminal type is currently set to "hp". If you
are using any other type of terminal you will see "garbage" on the
screen following this message.
If this is the case, you will need to either change the terminal type
set in the firmware via GSP (if your GSP firmware version supports
this feature), or change your terminal emulation to match the
firmware. In either case you will need to restart if your terminal and
the firmware terminal type do not match.
Press the 'b' key if you want to reboot now.





What terminal emulator do you use?

[fizan]

Tortsen::In one of the running V-par on the n-par i checked the term::

# echo $TERM
xterm

[Torsten.]

But what you are using on your PC (or whatever your client is)?

[Abid Iqbal]

Hi,
What about booting from DVD media HP-UX?
Give it a try.

[fizan]

Tortsen : am using a laptop, in that i check in the hyperterminal its auto detect it says.

In the GSP now if i press b it will reboot the new v-par alone or the entire N-par0?

@ Iqbal: I have only tape option to get it done, previous running 2 v-pars are create from tape image only.

Thanks

[fizan]

# vparstatus |grep hptest3
hptest3 Boot Dyn,Auto,Nsr /stand/vmunix
hptest3 2/ 4 2 6 128 128
hptest3 0/ 0 4096 0/ 0 0

================================

Still its in the boot phase only for past 1 hrs, whether it will take time to boot up, but as far as its not a normal behaviour,

How to come out of this error & boot up ?? the OS

[Torsten.]

I always had problems with hyperterminal, so I usually use putty.


hyperterminal may produce problems with various settings.

[fizan]

Tortsen i aslo use putty only now & always to login to the Unix machines...