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...

[Torsten.]

Does it work now with putty?

[fizan]

By default i use that only from old days.

FYI: Still showing the same by loggin in by putty also.

Can we try a vparreset newvpar ??

[fizan]

@ this point the MP itself hangs can i go for a MP reset ???

MP:CM> XD ??

will work out atlest to switch between other v-pars ??

Thanks

[fizan]

This time i given a vparload from the MON> now it says ::

MON> vparload -p hptest3 -B TAPE
[MON] Booting hptest3...
[MON] Console client set to hptest3

[MON] hptest3 loaded
load_statsym_vmunix: cannot open kernel.
WARNING: load_statsym: Could not open kernel symbol table
The system is fine, but the Dynamically Loadable Kernel Modules
feature will be disabled. If the kernel has been stripped of
symbols, rebuild or restore the kernel and reboot to enable
Dynamically Loadable Kernel Modules.
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: cachefs_link(): File system was registered at index 4.
NOTICE: nfs3_link(): File system was registered at index 7.

Host is virtual System Console slave
iether0: INITIALIZING HP AB290-60001 PCI/PCI-X 1000Base-T 2-port U320 SCSI/2-port 1000B-T Combo Adapter at hardware path 0/0/1/1/0/6/0
iether1: INITIALIZING HP AB290-60001 PCI/PCI-X 1000Base-T 2-port U320 SCSI/2-port 1000B-T Combo Adapter at hardware path 0/0/1/1/0/6/1
Swap device table: (start & size given in 512-byte blocks)
entry 0 - auto-configured on root device; ignored - no room
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
Starting the STREAMS daemons-phase 1
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: B11.23_LR FLAVOR=perf Fri Mar 19 15:24:05 PST 2004 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 4063232 Kbytes, lockable: 2818452 Kbytes, available: 3593560 Kbytes


System Console is virtual
* Preparing to execute init...

System Console is virtual

System Console is virtual
======= 04/19/11 06:36:29 EDT HP-UX Installation Initialization.
@(#)Ignite-UX Revision C.7.8.201
@(#)ignite/launch (opt) Revision:
/branches/IUX_RA0903/ignite/src@76987 Last Modified: 2009-02-05
15:45:55 -0700 (Thu, 05 Feb 2009)
* Configuring RAM filesystems...
* Scanning system for IO devices...
* Boot device is: 0/0/1/1/0/4/1.1.0
* Setting keyboard language.
NOTE:
The console firmware terminal type is currently set to "vt100". 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.
Recovery tape created from system: dptest1 on Fri Apr 15 12:54:14 2011


(Press any key to continue.)
=====How to get out of here===============

[Torsten.]

Is this image created from another vPar?

[fizan]

Yes the image is freshly created from running V-par on last friday ::

Recovery tape created from system: dptest1 on Fri Apr 15 12:54:14 2011

It shows that able to read the tape content but console is not getting::

[Abid Iqbal]

Hi,
Modify the new vapr as under
# vparmodify â p -a io::TAPE
And try booting from tape.