System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Server rebooting after creating dump

SKR_1
Trusted Contributor

Server rebooting after creating dump

Hi All,

I am getting below error on 11.31 Itanium server. Please help to resolv this issue.

ktracer is off until requested.
Installing Socket Protocol families AF_INET and AF_INET6
64000/0xfa00 esvroot
Kernel EVM initialized
64000/0x0 mass_storage
64000/0x0/0x0 usb_ms_scsi
0 sba
0/0 lba
0/0/1/0 rmp3f01
0/0/1/1 rmp3f01
0/0/1/2 asio0
0/0/2/0 hcd
0/0/2/1 hcd
0/0/2/2 ehci
0/0/4/0 gvid_core
0/1 lba
0/2 lba
0/3 gh2p
0/3/0/0 PCItoPCI
0/3/0/0/0 pci_slot
0/4 gh2p
0/4/0/0 PCItoPCI
0/4/0/0/0 pci_slot
0/5 gh2p
0/5/0/0 PCItoPCI
0/5/0/0/0 pci_slot
120 processor
122 processor
250 pdh
250/0 ipmi
250/1 asio0
250/2 acpi_node
255/1 mass_storage
255/1/0 usb_ms_scsi
gio: Error configuring root device using EFI hw paths

System Console is on the Built-In Serial Interface
AF_INET socket/streams output daemon running, pid 28
afinet_prelink: module installed
Starting the STREAMS daemons-phase 1
Swap device table: (start & size given in 512-byte blocks)
entry 0 - auto-configured on root device; 0/0/2/0.1 usbcomposite
0/0/2/0.1.0 hid
0/0/2/0.1.1 hid
ignored - can't open device
WARNING: No swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
mountfs:opend
VFS_MOUNTROOT error information:
0:(hfs) 6
10:(dnlc_neg_fs) 251

Message buffer contents after system crash:

panic: VFS_MOUNTROOT: READ_ONLY: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????
Stack Trace:
IP Function Name
0xe000000002217160
0xe0000000018b0ec0
0xe000000002205360
End of Stack Trace

linkstamp: Wed Apr 07 16:27:55 EST 2010
_release_version: @(#) $Revision: vmunix: B.11.31_LR FLAVOR=perf
Calling function e0000000019b2b00 for Shutdown State 1 type 0x2
i 0 pfn 0x1 pages 0x9f
i 1 pfn 0x100 pages 0x3dc2c
i 2 pfn 0x3e198 pages 0x390
i 3 pfn 0x3fc00 pages 0x148
i 4 pfn 0x3fd4c pages 0xa
i 5 pfn 0x3fd7e pages 0x6
i 6 pfn 0x3fde6 pages 0x6
i 7 pfn 0x100000 pages 0x500000
i 8 pfn 0x10040000 pages 0xbf1fe
i 9 pfn 0x100ff200 pages 0xe00
*** Not enough CPUS for a compressed dump ***

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

ERROR: No dump space is configured. Physical memory will not be dumped.
ERROR: Configured dump space is insufficient to hold dump metadata.
Physical memory will not be dumped.
8 REPLIES
Torsten.
Acclaimed Contributor

Re: Server rebooting after creating dump

Any changes made recently?

I would suggest to boot into LVM maintenance mode and export/import vg00.

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!   
SKR_1
Trusted Contributor

Re: Server rebooting after creating dump

Hi Torsten,

I have just installed two patches on system which dont need any reboot. Also i have changed two kernal parameters.

maxfiles-lim
ncsize

ncsize need the reboot of server, so i rebooted the server and now server is not coming up.
Dennis Handly
Acclaimed Contributor

Re: Server rebooting after creating dump

>have changed two kernel parameters: maxfiles_lim

How big was it and what is it now?
SKR_1
Trusted Contributor

Re: Server rebooting after creating dump

Before maxfiles_lim 16384
New Value set maxfiles_lim 63488
Torsten.
Acclaimed Contributor

Re: Server rebooting after creating dump

So I would try to boot the backup kernel now.

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!   
SKR_1
Trusted Contributor

Re: Server rebooting after creating dump

Even i am not able to boot machine in single user mode. I have not worked on LVM maintenace mode. Please advise.

====================Error========

Launching /stand/vmunix
SIZE: Text:45742K + Data:6504K + BSS:30408K = Total:82655K
Console is on Serial Device - via PCDP
Booting kernel...


Stored message buffer up to system crash:

MFS is defined: base= 0xe00000010240f000 size= 1068 KB
krs_find_files: The config.krs file was not found.
krs_find_files: The config.krs.lkg file was not found.
Found adjacent data tr. Growing size. 0x1bf1000 -> 0x5bf1000.
Loaded ACPI revision 2.0 tables.
MMIO on this platform supports Write Coalescing.
krs_find_files: The config.krs file was not found.
krs_find_files: The config.krs.lkg file was not found.
kc_init: Error getting number of static modules in KRS. Could not initialize static modules list


MCA recovery subsystem disabled, not supported on this platform.
Using /stand/ext_ioconfig

Memory Class Setup
-------------------------------------------------------------------------
Class Physmem Lockmem Swapmem
-------------------------------------------------------------------------
System : 23345 MB 23345 MB 23345 MB
Kernel : 23345 MB 23345 MB 23345 MB
User : 22019 MB 19521 MB 19597 MB
-------------------------------------------------------------------------

ktracer is off until requested.
Installing Socket Protocol families AF_INET and AF_INET6
64000/0xfa00 esvroot
Kernel EVM initialized
64000/0x0 mass_storage
64000/0x0/0x0 usb_ms_scsi
0 sba
0/0 lba
0/0/1/0 rmp3f01
0/0/1/1 rmp3f01
0/0/1/2 asio0
0/0/2/0 hcd
0/0/2/1 hcd
0/0/2/2 ehci
0/0/4/0 gvid_core
0/1 lba
0/2 lba
0/3 gh2p
0/3/0/0 PCItoPCI
0/3/0/0/0 pci_slot
0/4 gh2p
0/4/0/0 PCItoPCI
0/4/0/0/0 pci_slot
0/5 gh2p
0/5/0/0 PCItoPCI
0/5/0/0/0 pci_slot
120 processor
122 processor
250 pdh
250/0 ipmi
250/1 asio0
250/2 acpi_node
255/1 mass_storage
255/1/0 usb_ms_scsi
gio: Error configuring root device using EFI hw paths

System Console is on the Built-In Serial Interface
AF_INET socket/streams output daemon running, pid 28
afinet_prelink: module installed
Starting the STREAMS daemons-phase 1
Swap device table: (start & size given in 512-byte blocks)
entry 0 - auto-configured on root device; 0/0/2/0.1 usbcomposite
0/0/2/0.1.0 hid
0/0/2/0.1.1 hid
ignored - can't open device
WARNING: No swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
mountfs:opend
VFS_MOUNTROOT error information:
0:(hfs) 6
10:(dnlc_neg_fs) 251

Message buffer contents after system crash:

panic: VFS_MOUNTROOT: READ_ONLY: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????
Stack Trace:
IP Function Name
0xe000000002217160
0xe0000000018b0ec0
0xe000000002205360
End of Stack Trace

linkstamp: Wed Apr 07 16:27:55 EST 2010
_release_version: @(#) $Revision: vmunix: B.11.31_LR FLAVOR=perf
Calling function e0000000019b2b00 for Shutdown State 1 type 0x2
i 0 pfn 0x1 pages 0x9f
i 1 pfn 0x100 pages 0x3dc2c
i 2 pfn 0x3e198 pages 0x390
i 3 pfn 0x3fc00 pages 0x148
i 4 pfn 0x3fd4c pages 0xa
i 5 pfn 0x3fd7e pages 0x6
i 6 pfn 0x3fde6 pages 0x6
i 7 pfn 0x100000 pages 0x500000
i 8 pfn 0x10040000 pages 0xbf1fe
i 9 pfn 0x100ff200 pages 0xe00
*** Not enough CPUS for a compressed dump ***

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

ERROR: No dump space is configured. Physical memory will not be dumped.
ERROR: Configured dump space is insufficient to hold dump metadata.
Physical memory will not be dumped.
Kapil Jha
Honored Contributor

Re: Server rebooting after creating dump

Check the alternate kernel from
HPUX>ll

and try to boot the alternate kernel

HPUX>boot vmunix.prev â lm


BR,
Kapil+
I am in this small bowl, I wane see the real world......
SoorajCleris
Honored Contributor

Re: Server rebooting after creating dump

Hi ,

Try to boot in lvm maintenance mode.

boot vmunix -lm will go to lvmmaitenance mode, If your kernal are OK.

Just try to fix lvlnboot.
Most probably, it is not able to find the swap, dump and all it says.

May be a problem with disk also.

Just try to boot in LM and check if every thing is there.

Regards,
Sooraj
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity" - Dennis Ritchie