Operating System - HP-UX
1748233 Members
3326 Online
108759 Solutions
New Discussion юеВ

System won't boot after kernel parameter change

 
SOLVED
Go to solution
Kuekuatsheu
Advisor

System won't boot after kernel parameter change

I changed the kernel parameter maxfiles and maxfiles_lim to 409600. When I try to reboot the server, it won't boot anymore. Do you have any idea on how to recover my vpar?

Thanks.
20 REPLIES 20
sujit kumar singh
Honored Contributor
Solution

Re: System won't boot after kernel parameter change

hi

yiu can try boooting the alternate kernel that is /stand/vmunix.old

from the MON prompt try the following


MON>vparload -p -b


the alternate kernel name may be /stand/vmunix.old


If you had another Boot Disk in the VPAR which you might have detached during this kernel change, you can put in that disk which has the old kernel and try from the MON prompt

MON>vparload -p -B


Regards
Sujit


Regards
Sujit
Kuekuatsheu
Advisor

Re: System won't boot after kernel parameter change

Tried it. System still won't boot. Even when I use vmunix.prev

Any other ideas?

Thanks.
sujit kumar singh
Honored Contributor

Re: System won't boot after kernel parameter change

What is the Error that you are getting trying to boot from the alternate Kernel and what is the error that is for booting the Old kernel?

can you please post the errors in both the cases please?


Regards
Sujit

Kuekuatsheu
Advisor

Re: System won't boot after kernel parameter change

Error is the same as booting from the old and new kernels. Shown below:

WARNING: Could not allocate page table structures in

interleaved memory.
WARNING: For better performance, it is recommended that you

re-configure
WARNING: the machine to have more interleaved meError:vPar

shmem r/o private for type 4 is not yet ready.Try later
Error:vPar shmem r/o private for type 4 is not yet ready.Try

later

Stored message buffer up to panic:
Found adjacent data tr. Growing size. 0x3179000 ->

0x7179000.
Pinned PDK malloc pool: base: 0xe000000100e87000 size=116196K
Loaded ACPI revision 2.0 tables.
MMIO on this platform supports Write Coalescing.

MFS is defined: base= 0xe000000100e87000 size= 5696 KB


WARNING: Could not allocate page table structures in

interleaved memory.
WARNING: For better performance, it is recommended that you

re-configure

System Panic:
WARNING: the machine to have more interleaved memory.
panic: Could not find a good physical range for unpinned space
Stack Trace:
IP Function Name
0xe000000000e64e90 unpinned_pdk_malloc_phys_mem_alloc+0x3c0
0xe000000000e65de0 unpinned_pdk_malloc_init+0x6d0
0xe0000000017dee50 DoCalllist+0x3a0
End of Stack Trace

linkstamp: Fri Jan 30 12:11:41 EAT 2009
_release_version: @(#) $Revision: vmunix: B11.23_LR

FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $
Error:vPar shmem r/o private for type 4 is not yet ready.Try

later
Error:vPar shmem r/o private for type 4 is not yet ready.Try

later

*** 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: Your system crashed before I/O and dump configuration

was complete.
This system does not support a crash dump under these

circumstances.
Contact your HP support representative for assistance.
Initializing IO Devices ...
LBA Cell 00 (10/11): Occupied PCI-X 133MHz
Scan PCI:
Rope Slot Seg Bus Dev Fun Card


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

======
10 02 0x00 0xa9 0x01 0x00 PCI Bridge

(0x01a7,0x1014)
10 02 0x00 0xaa 0x04 0x00 SCSI Adapter

(0x0030,0x1000)
10 02 0x00 0xaa 0x04 0x01 SCSI Adapter

(0x0030,0x1000)
10 02 0x00 0xaa 0x06 0x00 Ethernet

(0x1079,0x8086)
10 02 0x00 0xaa 0x06 0x01 Ethernet

(0x1079,0x8086)
LBA Cell 00 (04/05): Occupied PCI-X 266MHz
Scan PCI:
Rope Slot Seg Bus Dev Fun Card


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

======
04 06 0x00 0x54 0x01 0x00 Fibre Channel

(0x2422,0x1077)
04 06 0x00 0x54 0x01 0x01 Fibre Channel

(0x2422,0x1077)
LBA Cell 01 (14/15): Occupied PCI-X 133MHz
Scan PCI:
Rope Slot Seg Bus Dev Fun Card


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

======
14 04 0x01 0xe3 0x01 0x00 Ethernet

(0x1079,0x8086)
14 04 0x01 0xe3 0x01 0x01 Ethernet

(0x1079,0x8086)
LBA Cell 01 (02/03): Occupied PCI-X 133MHz
Scan PCI:
Rope Slot Seg Bus Dev Fun Card


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

======
02 07 0x01 0x38 0x01 0x00 Fibre Channel

(0x2422,0x1077)
02 07 0x01 0x38 0x01 0x01 Fibre Channel

(0x2422,0x1077)
Complete

[MON]
vPar "ANALYTICS" failed to load the kernel due to:

non-bootable boot media; incorrect vPars software installed;

or incorrect boot media EFI path in vPars database.
Try using "vparload -p ANALYTICS -E 0" to load the vPar.
Error loading "ANALYTICS". Shutting down "ANALYTICS"...
[MON] ANALYTICS has halted.

We already tried vparload -p ANALYTICS -E 0, still doesn't work.

Don Morris_1
Honored Contributor

Re: System won't boot after kernel parameter change

First, halt the vPar (should halt itself eventually, you might have to do a vparreset from another vPar, though).

Then try one of the following:

1) vparload -p -b /stand/backup/vmunix

[vmunix.prev is more of an 11.11-ism. For v2 and later, you specify the backup/alternate kernel configuration -- the default auto backup is "backup" so this is likely to be there for your pre-tunable changes].

2) vparload -p -o \"maxfiles=2048 maxfiles_lim=4096\"

That may only work on a v3 kernel -- I don't remember for sure when boot-string tunable settings was done

3) Add more interleave to the vPar until it boots. What the problem is here is that you've increased this tunable -- and kernel data structures which use it and are allocated relatively early in boot grew accordingly. The problem is that early boot memory is a very scarce resource (there's a bootstrapping going on -- a little known good memory is used to get things built to bring in some more memory... then that memory is used to discover the rest of the system and bring the rest of the memory in, after which things work pretty normally from the allocator's point of view. Unpinned PDK memory is that second bit [Pinned is the original known good if you're wondering]). What you've indirectly asked the system to build is just too much for the memory known/available at this intermediate stage (which is usually just Interleave [or on a system with only CLM, the CLM which is addressed from low ranges].)

Personally, I'd go option (1) and then re-tune the system.
Kuekuatsheu
Advisor

Re: System won't boot after kernel parameter change

Tried options 1 and 2 to no avail. How do I add more interleaves? Maybe that will work. Thanks.
Don Morris_1
Honored Contributor

Re: System won't boot after kernel parameter change

What happened with (1)? Was there no backup configuration on your machine [you could try last_install as well... but it would be nice to get some data on what your output is here].

Oh -- and one other thing to try:

vparload -p -o -tm

I had to dig around to find Failsafe mode -- but that should bring up the kernel with your tunable settings ignored and the Failsafe values instead. Try that before adding memory as described below. (And if that doesn't work, show what did happen -- getting the options recognized by vparload sometimes seems to involve getting the command to realize what goes with -o and what doesn't... so it may be that we just need to get a "" around the -tm or something.

You add memory to a vPar using vparmodify. Since this is v2, the vPar will have to be stopped (which shouldn't be an issue).

vparmodify -p -a mem::

Where vpar is the target vPar and size is the amount in Mb you want to add [since you don't specify a Cell, that is ILM in the command]. The size needs to be a multiple of the granule size defined for your vPar environment.

vparstatus -A in another vPar will show you available resources (granule size and how much ILM is left).
Kuekuatsheu
Advisor

Re: System won't boot after kernel parameter change

Thanks. Succeeded in booting in failsafe mode. The OS advised us to removed the saved with the kconfig -d command but when we issued it, the OS returned that the command was not found. How do we reset the kernel parameters to the old values in failsafe mode. Please advise. Thanks again!

OWEN
Don Morris_1
Honored Contributor

Re: System won't boot after kernel parameter change

Ok... failsafe comes up in Single user mode.

So you'll want to "mount /usr" first [as kconfig lives in /usr/sbin/kconfig].

Then I'd do just "kconfig" first -- to see which configurations you _do_ have. Look for one such as "GOOD" or "backup" or anything other than your current one. Then kconfig -n and reboot.

Your system should come up in _that_ configuration -- at which point you can do: kctune -c maxfiles= maxfiles_lim=
which will reset the tunables to the default for that configuration. Then kconfig -n and reboot... and you should be back to normal. Alternately, you could try a lower setting than 409600 but higher than the defaults -- but at this point I'd be more focused on getting your system back.

After you mount /usr -- you could try just kctune directly... but my v3 system in Failsafe has a long message about configuration changes not likely to be written to disk in failsafe mode, so I'd assume v2 is the same here. Safer to reboot to an alternate configuration (non-Failsafe) and make the changes there.