Kernel Corrupted

[Rajesh R_2]

Hai,

I tried to apply the Hardware patch HWE1100_B.11.00.0403.3.depot on my HP_UX 11.00 server. It did not complete and also the kernel got corrupted.

Now when I give the command:
netstat -nr

It gives
:no namelist

Please can anyone help me to recover the kernel back.

Regards
Rajesh

[MarkSyder]

You should always take an ignite backup before installing a patch such as this. If you took one, restore from it. If not ... you've just learned a valuable lesson! And I'm sure someone else will be able to help.

Mark Syder (like the drink but spelt different)

[KVK]

Hi

Always perform a Ignite backup before the installation .
You have to revert back your OS with ignite backup only

Does the system mirrored ?

[Bill Hassell]

Before applying a lot of patches, make sure your swinstall (the SD suite of programs) is up to date. There are a number of hangs that can occur without the latest SD cumulative patches. However, all is not lost. There should be a second, backup copy of vmunix in /stand called vmunix.prev and this should work as a kernel (depending on how old this backup copy might be). Or a better choice is to restore /stand/vmunix from your latest backup tape.

Now the ":no namelist" message indicates that the current kernel in memory does not match /stand/vmunix and the above scenario to restore the old version of vmunix should help. The downside is that if the patch installation failed partway through, the system may be in an unstable condition. That means that some libraries may have been changed already, others not, some commands and drivers updated and some not. This may mean that your system, while running now, may not be able to reboot. You'll definitely need a previously recorded Ignite/UX backup tape. Lacking that, make an fbackup tape of all the directories in vg00, get a set of config information from these commands:

lvlnboot -v
bdf
cat /etc/fstab
vgdisplay -v vg00

and at a time when extended downtime is available, try a reboot.

[Kent Ostby]

Rajesh --

This is generally the type of error that you would see if you regenned the kernel but had not rebooted the machine since then.

Have you doone a reboot since the regen ?

The problem is that its trying to find a namelist in the kernel but the "current" kernel (in memory) doesn't match the next bootable kernel.

[Rajesh R_2]

I rebooted the machine. It came up without any problem. But when i give commands like netstat etc. it is not working. Also I rebooted with the old kernel vmunix.prev, but still the commands netstat etc are not working.

[Robert-Jan Goossens]

Can you check the state of the installed filesets ?

# swlist -l fileset -a state -a patch_state

[Rajesh R_2]

Robert,

The output of the command
# swlist -l fileset -a state -a patch_state

shows some patches are superseded.

Thanks & Regards
Rajesh

[Mahesh Kumar Malik]

Hi Rajesh

It is a good practice to make backup of kernel e.g. vmunix.bak before applying any patch because system will create backup as vmunix.prev while regenerating the kernel. In the event of serious problem, you can be back to work with vmunix.bak and re-analyse the issues

Regards
Mahesh