topic Re: cannot create the new kernel... in Operating System - HP-UX

cannot create the new kernel...

Harry Chua — Thu, 10 Apr 2003 11:14:00 GMT

I'm trying install
patches "PHKL_23409","PHKL_26008" and
some others patches that required to
build the kernel on the 11.00 OS.

The error faced was:
==========================
NOTE: Building a new kernel based on
template file "/stand/system"
Generating module: krm...
Compiling /stand/build/conf.c...
Loading the kernel...
ld: Unsatisfied
symbol "lv_vg_is_active" in
file /usr/conf/lib/libprm.a[kern_fss.o]
1 errors.
*** Error exit code 1

Stop.
make failure.
ERROR: The
command "/usr/sbin/mk_kernel", which is
used to rebuild the kernel, has
failed. Because kernel-related
filesets were installed, this command
must be executed by "swinstall",
without failures, before the load can
continue. Check theabove output for
details about the failure.
NOTE: The Install Phase has
suspended. Check the above output for
reasons.

* Aborting the Install Phase.

Re: cannot create the new kernel...

melvyn burnard — Thu, 10 Apr 2003 11:21:56 GMT

You may want to read document UKRNBKBRC00011783
It appears as though a patch has not been intalled, or has been removed.
To be specific, are PHKL_28150 and PHKL_28152 or there newer revisions installed? or been removed?

Re: cannot create the new kernel...

Steven E. Protter — Thu, 10 Apr 2003 11:43:16 GMT

I got this errror once.

After reinstalling PHKL_18543.

You need to go to backups of your /stand/system file at the very least and try again.

If it was the patch above, you need to do this:

swverify \* take note of every single bad patch.

Get them, their dependencies and make a big patch depoot.

then swinstall -x autoreboot -x reinstall=true -s /location_of_patch.depot

make sure that PHKL_18543 is not part of any patch depot you create.

I hope its just a bad system file.

SEP

Re: cannot create the new kernel...

Michael Steele_2 — Thu, 10 Apr 2003 12:35:20 GMT

Gee I hope you haven't stumbled into someone else's mess. Please check the time stamps on /stand/vmunix and /stand/vmunix.prev. If they are the same then you've got problems.

If the same then check the /var/adm/sw/swagent.log and swinstall.log for previous failed swinstalls.

If PHKL_18543 then stop and get advice.