Error booting 11v1 after patching with QPK

[cartman_2]

Hi,

We have a rp8420, after patching with the 2009 QPK patch bundles:

GOLDAPPS11i B.11.11.0912.483 Applications Patches for HP-UX 11i v1, December 2009
GOLDBASE11i B.11.11.0912.483 Base Patches for HP-UX 11i v1, December 2009
HWEnable11i B.11.11.0612.458 Hardware Enablement Patches for HP-UX 11i v1, December 2006

And the installation worked ok, no errors in the swagent.log . After finishing the install, the server rebooted and got to the stage:

VxVM reconfiguration recovery ....................................... OK
Mount file systems .................................................. OK
Virtual Partitions Initialization ................................... OK
Update kernel and loadable modules .................................. BOOT

it got to this point and the rebooted, I booted 3 times in a row with the same result, the kernel was getting rebuilt all the time and after that the server rebooted.

After that I booted from vmunix.prev, and the server booted ok.

cheking the rc.log and rc.log.old, both had the same output:

Virtual Partitions Initialization
Output from "/sbin/rc1.d/S105vparinit start":
----------------------------
/sbin/rc1.d/S105vparinit[126]: 444 Memory fault(coredump)
Building a new kernel based on template file "/stand/system"
WARNING: No such device, tunable, or cdio cell.
Ignoring the following line.
cell
Generating module: krm...
Compiling /stand/build/conf.c...
Loading the kernel...
Generating kernel symbol table...

Kernel update request is scheduled.

Default kernel /stand/vmunix will be updated by
newly built kernel /stand/build/vmunix_test
at next system shutdown or startup time.

NOTE: /stand/vmunix now relocatable ... rebooting.

Update kernel and loadable modules
Output from "/sbin/rc1.d/S110kmbuild start":
----------------------------
* The current kernel function set directory at
"/stand/dlkm" has been moved to
"/stand/dlkm.vmunix.prev".
* The current kernel at "/stand/vmunix" has been moved
to "/stand/vmunix.prev".
* The newly built kernel has been moved to "/stand/vmunix".
* The newly built kernel function set directory has been moved
to "/stand/dlkm".
EXIT CODE: 3 - Default kernel is updated. Rebooting system...


The exit code is ok, the next time it should boot with out building the kernel again

looks like it's getting mixed up with the vpar kernel rebuild and the proper patch rebuild. by the way this server isn't a vpar now, so vparinit could be disabled if needed?.

I think the kmbuild looks for a .update_ux in /stand and if it exists it recompiles, could it that the file didn't get deleted?

has someome seen this behaviour before?

thnx

[Shibin_2]

What is at line no. 126 of /sbin/rc1.d/S105vparinit ?

I am not expert to talk about vPar. But, if you are not configured any vPar, try to disable it and boot.

[cartman_2]

yes I will disable the vparinit, and remove the vpar software, buy I have to be sure that is the cause of the system rebooting in a loop rebuilding the kernel

[cartman_2]

To give the thread a ping, and also add another question, how does the kernel know it has to recompile the kernel when booting?, is there a way to trick it so it doesn't compile the kernel on boot, just in case it gets into a loop like it happened today ?

[likid0 · Accepted solution]

On your last question..

you can check in the /sbin/rc1.d/S110kmbuild script it has in the main:

'start'|'stop')

#
# Update kernel and modules
#
if [ -f $UPDATE_UX_FILE ]; then
update_kernel $1

and the update ux file as you say is:

# Flags
UPDATE_UX_FILE=$STAND/.update_ux


if the file exists te script calls the update_kernel function that uses the kmcpux,

kmcpux also checks the .update_file

First if the file doesn't exist:
root@unknown:/> ls -la /stand/.update_ux
/stand/.update_ux not found
root@unknown:/> kmcpux -v
root@unknown:/> echo $?
2

It outputs with 2 that means SKIP, don't compile.

If I create the file it tries to update the kernel
root@unknown:/> touch /stand/.update_ux
root@unknown:/> kmcpux -v
/sbin/kmcpux[3]: test: Specify a parameter with this command.
ERROR: Cannot find the newly built kernel function set directory
"/dlkm.".

After that it deletes the file:
root@unknown:/> ls -la /stand/.update_ux
/stand/.update_ux not found

So your case seems strange, rebooting in loop.

[likid0]

Hi, it's strange your case, because taking a look at the kmcpux shell script code, it allways does and rm of the file:

#
# Set source kernel path
#
get_source_kernel_path()
{
# If there is not update flag, do nothing.
if [ ! -f $STAND/$UPDATE_UX ]; then
return $NOP
............................
.............................

# Request accepted
# Erase the flag file here, since if an error is detected further
# operations, this script should not be called again w/o trouble
# shooting.
#
rm $STAND/$UPDATE_UX

return $SUCCESS
}

[likid0]

I tested on a server, launching the vparinit mk_kernel commands, and I found that it creates the .update_ux file. So to fix your problem you should:

Boot in single user/maintainance mode
delete de vparinit script in rc1
and Boot the server again.

It should start with no problem, and you server patched

[cartman_2]

It worked as Daniel Described