It started with lanscan....

[Allen DuBeau]

Hi all -
My first post :)

OS Level: 11.11
Server: V2250

Here is my problem:
lanscan doesn't work as well as dmesg.
So I as well as another admin rebuilt the Kernel and reboot...The same issue, lanscan and dmesg does not work.


echo "boot_string/s" | adb -k /stand/vmunix /dev/kmem


Warning, the kernel and core release versions don't match.

This may also be due to crashfile corruption.
Proceeding anyway.

boot_string:
boot_string:

Another tidbit this system was upgraded from 11.0 to 11.11 12/02 of last year...

Any help or suggestions will greatly appreaciated..

Allen :)

[Patrick Wallek]

I seriously doubt that the kernel will effect lanscan and dmesg.

What happens when you try to run lanscan and dmesg? What errors do you get? Does it coredump? A bit more information would be helpful.

[melvyn burnard]

well what error do you get?
what happens if you run lanscan -v ?
Is the system booting from the kernel file yu believe it is?
did you do a kmupdate after rebuilding hte kernel?

[Mark Greene_1]

Do this to see from where the system booted:

lvlnboot -v

and then using the boot disk info, run this:

lifls -Cl /dev/dsk/cXtXdX

and report back the output.

HTH
mark

[Massimo Bianchi · Accepted solution]

Hi,
first question: check with bdf, is /stand mounted ?

I ahd similar problem when my /stand was umounted for some mystical reason, taking with it many strage errors.

Massimo

[melvyn burnard]

Another question to ask, when did this start happening? When did htese commands last work without a problem?

[Allen DuBeau]

Mark -

Here is the info you requested:

Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t2d0 (0/0/1/1.2.0) -- Boot Disk
/dev/dsk/c2t2d0 (0/0/2/0.2.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c1t2d0
/dev/dsk/c2t2d0


lifls -Cl /dev/dsk/c1t2d0
volume ISL10 data size 7984 directory size 8 99/09/15 07:38:38
filename type start size implement created
===============================================================
ODE -12960 584 848 0 01/12/21 12:58:49
MAPFILE -12277 1432 128 0 01/12/21 12:58:49
SYSLIB -12280 1560 353 0 01/12/21 12:58:49
CONFIGDATA -12278 1920 234 0 01/12/21 12:58:49
SLMOD2 -12276 2160 141 0 01/12/21 12:58:49
SLDEV2 -12276 2304 135 0 01/12/21 12:58:49
SLDRV2 -12276 2440 205 0 01/12/21 12:58:49
SLSCSI2 -12276 2648 116 0 01/12/21 12:58:49
MAPPER2 -12279 2768 142 0 01/12/21 12:58:49
IOTEST2 -12279 2912 411 0 01/12/21 12:58:49
PERFVER2 -12279 3328 124 0 01/12/21 12:58:49
PVCU -12801 3456 64 0 01/12/21 12:58:49
SSINFO -12286 3520 2 0 01/12/21 12:58:49
ISL -12800 3528 306 0 00/11/08 20:49:59
AUTO -12289 3840 1 0 00/11/08 20:49:59
HPUX -12928 3848 848 0 00/11/08 20:50:00
LABEL BIN 4696 8 0 00/01/01 17:32:22

[Zeev Schultz]

Do
lifls -Cl /dev/dsk/c2t2d0
Check that all is there like its mirror disk.
Do
lifcp /dev/dsk/c2t2d0:AUTO -
lifcp /dev/dsk/c1t2d0:AUTO -
It should give out the hpux -... boot string.
Anyway,I'm trying to find a link btw this and lanscan/dmesg issues.I can guess that lanscan and/or dmesg can be related to terminal problems .Run hmm...cstm for example,
cstm>map.Do you get the prompt?
What ioscan -fnClan shows btw?

Regards and share points :)

Zeev

[Allen DuBeau]

Zeev -

Sorry for late response, ioscan works fine and so does cstm, here is the output from lifcp:

# lifcp /dev/dsk/c2t2d0:AUTO -
hpux -lq
#lifcp /dev/dsk/c1t2d0:AUTO -
hpux

[doug mielke]

Don't underestimate the power of Lanscan.
HP uses it for other functions, like finding devices.

Change permissions on it and you can watch as your system dies.

[Tim D Fulford]

If I'm reading this thread properly....

lvlnboot -v is only returning /stand (boot) You also need a swap, dump & root

I'm @home so double check with "man lnlnboot"

lvlnboot -d /dev/vg00/lvol2 # Dump
lvlnboot -r /dev/vgoo/lvol3 # Root
lvlnboot -s /dev/vg00/lvol2 # Swap
lvlnboot -b /dev/vg00/lvol1 # Root

then do
# lvlnboot -Rv
to make sure your new links stick & the output is correct...

Regards

Tim

[Allen DuBeau]

The last time the kernel was built and moved SAM was used, the previous time kmupdate was used, we beleive this issue started after the upgrade to ux-11.11. But we are not quite sure since lanscan is not used on a daily basis, as far as the kernel not having anything to do with it, beats me too..

Even though the box runs fine and we have not had any complaints from the user community we have been lucky so far. If all else fails I will most likely place a call to the support center. I am going to award the points, after I see what the support center says. Closest one with out going over wins :) ....

[Allen DuBeau]

Ok....

Here's the scoop..first I'm an ID10T, yes this is an actual technical term from my 2nd level support days.. Here is what the problem was:

Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 143360 88667 51447 63% /
/dev/vg00/lvol5 200376 53741 126597 30% /stand
/dev/vg00/lvol8 2097152 1546447 519916 75% /var
/dev/vg00/lvol7 1536000 1221996 294449 81% /usr

and it's a small over looked item.. most big problems are... So as you can see /stand is on lvol5 which is not correct (don't look at me I didn't do it...)

Sooooo..lvol1 is hanging around out there on vg00 minding it's own business until a reboot comes along, and loads the kernel from lvol1 instead of lvol5 (/stand). That's the reason for this error message:

Warning, the kernel and core release versions don't match. (Duh...Allen)

Back to breaking things....

[Massimo Bianchi]

Hi,
why don't you umount /dev/vg00/lvol5 and mount /dev/vg00/lvol1 ?


If you check, /stand is not used... so you can verify your thinking, and see if vmunix is still there :)

Massimo

[Allen DuBeau]

I mounted lvol1 on /mnt, vmunix is there..

Now what I need to do is copy /stand to /mnt change /etc/fstab and reboot.

[Massimo Bianchi]

Hi,
simply

umount /stand


and then

mount /dev/vg00/lvol1 /stand

you can :)

Massimo