Internal error: The kernel discovery tool used by SAM failed.

[Steve Longenecker]

I was working through the HP-UX 11.0 pre-upgrade checklist this morning and encountered the following error message in sam while attempting to access any option in the "Disks and File Systems" or "Kernel Configuration" menus:

Internal error: The kernel discovery tool used by SAM failed.
Kernel changes cannot be made by SAM. The standard error output of
the command is shown below:

getkinfo: Syntax error in system file.
Incorrect driver/subsystem statement(s): sctl, sdisk, stape

Each driver/subsystem shown above is not valid for one of the
following reasons: The driver (including any aliases) is not
recognized; there is no support for this driver in the kernel
libraries; the driver is not supported; one or more dependency
drivers for this driver are missing, not supported, or not included
in the kernel libraries.

Be sure all kernel libraries from HP-UX product filesets are
installed, and that the driver/subsystem names shown above are valid.
Refer to the SAM logfile for more information.

getkinfo: Unable to read the kernel file "/stand/vmunix".

I haven't made any server configuration changes, installed software or patches, since this last worked. As far as I can tell, the system file is OK, and mk_kernel creates a good kernel with the above referenced drivers.

Any idea what might be causing the error message, and more importantly, whether this will cause problems during the 11.0 upgrade? Installing 11.0 from scratch is NOT an option.

[Peggy Fong]

Hi
My guess is that since mk_kernel works successfully that you probably need SAM patches. You're not using SAM for your upgrade and if mk_kernel works then you probably would not have problems with your upgrade. Fixing the problem would of course give more confidence prior to moving on.

My 2cents
Peg

[Peggy Fong]

Steve
I also found a thread that has some suggestions that might help (so maybe you don't need any patches). Try this thread:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0xb902a24d9abcd4118fef0090279cd0f9,00.html

[Steve Longenecker]

Peggy,

The thread looked promising, but did not help because the drivers listed in error message are required on my system. BTW, what search string did you use to find this thread? I tried several searches before submitting my request, but didn't get any hits.

Thanks...

[Bill McNAMARA_1]

I had this problem just today cause by an ignite install of a system from a different systems make_recovery tape. my fix way to extract the kernel system file edit out in my case an fddi driver (no fddi on the ignite rescued system), then recompile the kernel with mk_kernel -o /stand/vmunix -s /stand/build/system

Good luck... and make network based ignite images.

Later,
Bill

[Steve Longenecker]

That's what adds to the confusion and frustration... :-)
Confusion: The drivers in this system (K-570) have not changed since the box was fielded in 1998. getkinfo has worked reliably after I installed the last patch bundle (September 2000) in December.
Frustration: I have ignite images, but management will not permit a system outage before the scheduled 11.0 upgrade.

[Peggy Fong]

Steve
You would ask what search string I used. I can't remember but I did something like

getkinfo: Syntax error

Then I selected "exact phrase"
You should see several examples of this error in the community forums (and you can also check the technical knowledge database.

You know, doing a sys_prep to get a new system file from the running kernel and using that file in the location that SAM uses might help.

Anyhow, check out the other threads you will get with that search string. Then try your other error - getkinfo: unable to read
again check "exact phrase"

I'll check back later or if I find anything else I'll post again.

Good Luck.
Peg

[Steve Longenecker]

Peg,

It turns out that /var/sam/boot.config is missing, though why is a mystery. Extracting a new system file and building a new kernel did not cure the getkinfo error message, though restoring a copy of /var/sam/boot.config from tape at least stops SAM from running getkinfo and generating the error messages.

Thanks again,

Steve

[Peggy Fong]

I'm glad you found the problem. boot.config was mentioned in some of threads using that search string I gave you. It seemed like one even had a way to re-create the file without needing to restore it. In any case, glad the problem is solved!
Peg