cannot find /stand/vmunix. Please help

[Peter Klausner_1]

Hi,

i have an A Class Server with 4 Disks. Running hpux 11.00.

I am using an pvg strict mirroring.

My /etc/lvmpvg looks like this

PVG orginal
/dev/dsk/c4t14d0
/dev/dsk/c4t12d0
PVG mirror
/dev/dsk/c0t10d0
/dev/dsk/c0t8d0


Yesterday i replace the primary boot disk /dev/dsk/c4t14d0. The seconday boot disk is /dev/dsk/c0t10d0
I get the system running again. I am using onlinediag. After the replacement of the primary boot disk i made an

mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p LABEL /dev/rdsk/c4t14d0.

So i restored the lif files from onlinediag

I boot the system 2 times and everything was working fine.

Today i made an lvlnboot -R. After setting up this command i reboot the system and I got the following error:

Exec failed: cannot find /stand/vmunix.

ISL> hpux ll /stand shows no kernels.

Please help !!!


Thanks in advance

[John Palmer]

Peter,

Does this occur when you boot from both the primary and mirror root disks?

It sounds as though lvlnboot has corrupted the Boot Data Reserved Area such that the system loader can't properly locate the /stand filesystem.

I have had this problem before. You need to get a system running so that you can run lvlnboot to reset your vg00 settings. This either means booting from a recovery CD or installing a version of HP-UX onto a spare disk.

Regards,
oh

[Peter Klausner_1]

Hi John,

what can I do? If i boot from CD there is the possibilty to use an recovery shell does this help me? I have no experience with the recovery shell.

Thanks

Peter

[John Palmer]

Peter,

Do you have a Recovery CD (it's labelled hp-ux 11.0 install/update/recovery)?

If so, load it and boot from it. Select the Recovery Shell from the menu. It's ages since I had to do this... I'll try to find the instructions...

Looks like you will have experience of running it by the time we've finished. ;??)

[John Palmer · Accepted solution]

Peter,

Extract from KB article...

This document details how to access your LVM Root Volume Group from
the Install/Support Media at 11.00.

1. Boot from the Install/Support Media.
Boot from the path of the CD media and do NOT interact with ISL.
You will get a menu with the following options:

Install HP-UX
Run a recovery shell
Advanced Options


2. Select "Run a Recovery Shell" from the menu.

3. Enter x from the SUPPORT MEDIA MAIN MENU, to exit to the shell.

4. Type chroot_lvmdisk. Something similar to the following will be
displayed:

Enter the hardware path associated with the '/'(ROOT) file system
(example: 7.6.9.37 )

5. Type to accept the example (default) as your root file
system hardware path; otherwise, enter the hardware path for the
root file system hardware you wish to specify in its place.

6. If you type , the following will be displayed:

Is 7.6.9.37 the hardware path of the root/boot disk?[y|n|q]-

7. Enter y, and something similar to the following will be displayed:
If your disk IS an LVM disk, you will see the following:

/sbin/fs/hfs/fsck -c 0 -y /dev/rdsk/c2t1d0s2lvm

** /dev/rdsk/c2t1d0s2lvm
** Last Mounted as /
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
6256 files, 0 icont, 1494 used, 1563824 free (928 frags, 195362 blocks)

/sbin/fs/hfs/mount /dev/dsk/c2t1d0s2lvm /ROOT
/sbin/fs/hfs/mount /dev/dsk/c2t1d0s1lvm /ROOT/stand

loading /usr/sbin/chroot
x ./usr/sbin/chroot 123456 bytes 96 blocks

Enter 'cd /ROOT; chroot /ROOT /sbin/sh' at the shell prompt to chroot
to the customer's /(root) disk.

(NOTE: If this command fails with a "bad superblock.."
message, your boot disk may not be an LVM disk.
If so, try: fsck /dev/rdsk/c2t1d0 (use your special file!)
If you see fsck messages akin to those above, you are making
progress and your disk is NOT an LVM disk.)

8. Enter cd ROOT; chroot /ROOT /sbin/sh at the shell prompt.

9. Enter vgchange -a y /dev/vg00.

This will "activate" vg00, so that you can get to your swap area, /usr,
etc.

Mount /usr.

10. Enter vgdisplay -v at the prompt.

The logical volumes within the disk corresponding to the various
components (/stand, swap, /, /home, /opt, /tmp, /usr, /var) are listed.

-------------------------------
At this point you should be able to run lvlnboot to repair your BDRA with the following:

Remove lvlnboot definitions and recreate (lvrmboot and then
lvlnboot). Fix the lvlnboot by doing:

lvrmboot -r /dev/vg00
lvlnboot -b /dev/vg00/lvol1
lvlnboot -r /dev/vg00/lvol3
lvlnboot -s /dev/vg00/lvol2
lvlnboot -R /dev/vg00

Then run lvlnboot -v to check that all looks OK, reboot and all should be well.

Good luck,
John