cancel
Showing results for 
Search instead for 
Did you mean: 

System panic after hpvmstop

Tim Medford
Valued Contributor

System panic after hpvmstop

I've just completed setting up a new HP Integrity virtual machine. Everything was working great, read through the manuals and had installed the O/S and presented DVD, Network and other storage devices.

I had done multiple hpvmstop and hpvmstart commands with no problems. But the last time I did an hpvmstop the VM will no longer start. The only difference is that now I have HPUX installed on the VM. I wondered how that works, am I supposed to do a shutdown within the VM before doing an hpvmstop?

Anyway, I cannot get the o/s to load at all inside the VM now. I cannot even get into single user mode, it just keeps crashing. Any suggestions?

Here's the output from the Console log:

Booting kernel...

Disabling 8259s

Memory Class Setup
-------------------------------------------------------------------------
Class Physmem Lockmem Swapmem
-------------------------------------------------------------------------
System : 4087 MB 4087 MB 4087 MB
Kernel : 4087 MB 4087 MB 4087 MB
User : 3116 MB 2713 MB 2724 MB
-------------------------------------------------------------------------

Loaded ACPI revision 2.0 tables.
NOTICE: cachefs_link(): File system was registered at index 4.
NOTICE: nfs3_link(): File system was registered at index 7.
NOTICE: mod_fs_reg: Cannot retrieve configured loading phase from KRS for module
: cifs. Setting to load at INIT

Boot device's HP-UX HW path is: 0/0/4/0.1.0
iether0: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/0/0
iether1: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/1/0
iether2: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/2/0

System Console is on the Built-In Serial Interface
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 8388608
Starting the STREAMS daemons-phase 1
vxfs: WARNING: msgcnt 1 mesg 096: V-2-96: vx_setfsflags - /dev/root file system
fullfsck flag set - vx_ierror
vxfs: WARNING: msgcnt 2 mesg 017: V-2-17: vx_dirlook - / file system inode 2340
marked bad incore
?vxfs msgcnt 2 offset 0x00000000 0 0 0 0
?vxfs msgcnt 2 offset 0x00000010 0 0 0 0
?vxfs msgcnt 2 offset 0x00000020 0 0 0 0
?vxfs msgcnt 2 offset 0x00000030 0 59fd58e2 0 0
?vxfs msgcnt 2 offset 0x00000040 0 0 0 0
?vxfs msgcnt 2 offset 0x00000050 0 0 0 0
?vxfs msgcnt 2 offset 0x00000070 0 0 0 0
?vxfs msgcnt 2 offset 0x00000080 0 0 0 0
?vxfs msgcnt 2 offset 0x00000090 0 0 0 0
?vxfs msgcnt 2 offset 0x000000a0 0 0 0 0
?vxfs msgcnt 2 offset 0x000000b0 0 0 0 0
?vxfs msgcnt 2 offset 0x000000c0 0 0 0 0
?vxfs msgcnt 2 offset 0x000000d0 0 0
The device file /dev/rroot does not exist or is not correct.
Automatic checks of the root file system not performed.
vxfs: WARNING: msgcnt 3 mesg 096: V-2-96: vx_setfsflags - /dev/root file system
fullfsck flag set - vx_ierror
Calling function e000000000ed7460 for Shutdown State 8 type 0x2

Stored message buffer up to panic:
Found adjacent data tr. Growing size. 0x3467000 -> 0x7467000.
Pinned PDK malloc pool: base: 0xe000000100b99000 size=119196K
Loaded ACPI revision 2.0 tables.
MMIO on this platform supports Write Coalescing.

MFS is defined: base= 0xe000000100b99000 size= 1960 KB


Unpinned PDK malloc pool: base: 0xe000000108000000 size=98304K
NOTICE: cachefs_link(): File system was registered at index 4.
NOTICE: nfs3_link(): File system was registered at index 7.
NOTICE: mod_fs_reg: Cannot retrieve configured loading phase from KRS for module
: cifs. Setting to load at INIT

0 cec_gen
0/0 gh2p
0/0/0/0 iether
0/0/1/0 iether
0/0/2/0 iether
0/0/3/0 legacyio
0/0/3/0/1 asio0
Initializing the Ultra320 SCSI Controller at 0/0/4/0. Controller firmware versio
n is 00.00.00.00
0/0/4/0 mpt
0/1 gh2p
0/2 gh2p
0/3 gh2p
0/4 gh2p
0/5 gh2p
0/6 gh2p
0/7 gh2p
120 processor
Standard input
250 pdh
250/0 ipmi
250/1 acpi_node
0/0/4/0.0 tgt
0/0/4/0.0.0 sdisk
0/0/4/0.1 tgt
0/0/4/0.1.0 sdisk
0/0/4/0.2 tgt
0/0/4/0.15 tgt
0/0/4/0.15.0 sctl
Boot device's HP-UX HW path is: 0/0/4/0.1.0
iether0: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/0/0
iether1: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/1/0
iether2: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/2/0

System Console is on the Built-In Serial Interface
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 8388608
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 31, minor is 0x1000; start = 826228, s
Boot device's HP-UX HW path is: 0/0/4/0.1.0
iether0: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/0/0
iether1: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/1/0
iether2: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/2/0

System Console is on the Built-In Serial Interface
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 8388608
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 31, minor is 0x1000; start = 826228, s
ize = 4194300
Starting the STREAMS daemons-phase 1
vxfs: WARNING: msgcnt 1 mesg 096: V-2-96: vx_setfsflags - /dev/root file system
fullfsck flag set - vx_ierror
vxfs: WARNING: msgcnt 2 mesg 017: V-2-17: vx_dirlook - / file system inode 2340
marked bad incore
?vxfs msgcnt 2 offset 0x00000000 0 0 0 0
?vxfs msgcnt 2 offset 0x00000010 0 0 0 0
?vxfs msgcnt 2 offset 0x00000020 0 0 0 0
?vxfs msgcnt 2 offset 0x00000030 0 59fd58e2 0 0
?vxfs msgcnt 2 offset 0x00000040 0 0 0 0
?vxfs msgcnt 2 offset 0x00000050 0 0 0 0
?vxfs msgcnt 2 offset 0x00000060 0 11 0 0
?vxfs msgcnt 2 offset 0x00000070 0 0 0 0
?vxfs msgcnt 2 offset 0x00000080 0 0 0 0
?vxfs msgcnt 2 offset 0x00000090 0 0 0 0
?vxfs msgcnt 2 offset 0x000000a0 0 0 0 0
?vxfs msgcnt 2 offset 0x000000b0 0 0 0 0
?vxfs msgcnt 2 offset 0x000000c0 0 0 0 0
?vxfs msgcnt 2 offset 0x000000d0 0 0
vxfs: WARNING: msgcnt 3 mesg 096: V-2-96: vx_setfsflags - /dev/root file system
fullfsck flag set - vx_ierror
System Panic:

panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????
Stack Trace:
IP Function Name
0xe000000000d71e00 vfs_mountroot+0x1d0
0xe000000000fe5f20 im_preinitrc+0x300
0xe00000000141e3b0 DoCalllist+0x3a0
End of Stack Trace

linkstamp: Thu May 10 11:09:24 EDT 2007
_release_version: @(#) $Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29
22:35:38 PDT 2003 $

sync'ing disks (0 buffers to flush): (0 buffers to flush):
0 buffers not flushed
0 buffers still dirty

*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to dump physical memory to disk, for use
*** in debugging the crash.

*** Cannot dump with compression because there are too few processors
2 REPLIES
Torsten.
Acclaimed Contributor

Re: System panic after hpvmstop

Hi,

the man page says
"HP recommends stopping
virtual machines using their native operating system commands."

Did you use the "-h" switch?
I guess even the "-g" will do a "reboot -h" only (not sure).
Now it looks like the root filesystem is damaged. If you cannot go to single user mode (probably not), consider to re-create or restore the backup.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Rockets
Occasional Visitor

Re: System panic after hpvmstop

use the following procedure to recover the unbootable VM:

assumption: you have another working VM on the same VM host. let's say, it's called 'goodvm'.

1. stop the unbootable vm.

2. stop the 'goodvm' on teh same vmhost.

3. remove the root disk from the bad vm.

4. add the same disk to the goodvm.

5. start the goodvm, import the new disk into a separate VG, calling it 'tmpvg'

activate the tmpvg on the goodvm, and fsck all the filesystems. for example:

fsck -y /dev/impvg/lvol3  -- this would be the /root of the badvm.

fsck -y /dev/tmpvg/lvol1 -- this would be the /stand of the boot disk of badvm.

... fsck remaining lvol on teh imported vg.

6. export the tmpvg from goodvm.

7. shutdown goodvm.

8. remove the disk from goodvm, add it back to the badvm.

9. start badvm. it should now boot up! :)

10. cheers!