problem with booting the system.

[R.L]

Hi, I'm facing a great problem. When I reboot my system, it gives me msg like "Exec failed: Cannot find /stand/vmunix or /vmunix". What cause this to happen and what is the solution for this?

Thanks!

[Vincent Stedema · Accepted solution]

Seems to me that you lost your kernel, or that the kernel wasn't moved into place during a reboot. You might want to try and boot from your old kernel (if you have one):

- interrupt the boot process
- type "bo pri"
- Interact with IPL? --> Y
- type "hpux -is /stand/vmunix.prev"

If you do have a backup kernel, this command will boot the system from it and take you to single user mode. Now you can build yourself a new kernel or copy /stand/vmunix.prev to /stand/vmunix.

Good luck.

[Marc Dijkstra]

Just to add to Vincents reply above, it could be that you have a pathing problem in the EEPROM, once you have interrupted the boot sequence, type in pa, this will tell you which is the primary boot device. Then type in sea ipl, this will tell you which disk has a bootable LIF. If they are not right, then reset the primary path with pa pri (device) and boot the machine.

Just a thought that might help...
MND

[Bruce Regittko_1]

Hi,

Vincent's steps will work if you have a backup kernel and it should be named /stand/vmunix.prev. However, you can view the contents of /stand first just to be sure. Issue

hpux ls

or

hpux ll

--Bruce

[R.L]

Vincent, I tried it. But it gave me msg "/stand/vmunix.prev: Cannot open or not executable". By the way, I'm interact with IPL now and cannot boot the system at all.

[Dan Hetzel]

Hi,

Did you try the 'sea ipl' that Mark suggested ?

It will take a while and then show you all disks with a bootable LIF.

Dan

[R.L]

Dan, I've tried "sea ipl" already. It gave me my primary path only.

[R.L]

Wondering if this is because I reduced the lv size of /stand before I do the reboot and it affect the kernel.

[Vincent Stedema]

RL,

If you indeed reduced your /stand lv, then the filesystem is probably corrupted.. Reducing an lv will in most cases corrupt the filesystem, unless (if i'm right) there are no datastructures in the PE's that were discarded or when you have OnLine JFS and Advanced JFS installed (not in this case, because /stand is a hfs filesystem).

Do you have an ignite recovery tape?

[Bruce Regittko_1]

Hi again,

If you have a recovery tape, boot from it and have it restore the system. If not, you will have to boot from the installation cdrom and install a base kernel to get your system booted.

What version of HP-UX are you running? 11.00 or 10.20?

--Bruce

[Peggy Fong]

hi
it may be too late to add my 2Cents worth, but you should also try booting to maintenance mode. at the ipl prompt type "hpux -lm" with no quotes. That is an ell not the #1. If this works then you can activate vg00 and redo the lvlnboot commands (which includes the starting location of stand and the size of stand). If this fails and you cannot boot to maintenance mode, then indeed stand got corrupted when you reduced it.

Good Luck.
Peggy

[Peggy Fong]

I forgot to add to previous post. If you can successfully boot to maintenance mode then do the following:
# vgchange -a y /dev/vg00
# lvrmboot -r /dev/vg00
# lvlnboot -b /dev/vg00/{boot_lvol} /dev/vg00
# lvlnboot -r /dev/vg00/{root_lvol} /dev/vg00
# lvlnboot -s /dev/vg00/{swap_lvol} /dev/vg00
# lvlnboot -d /dev/vg00{dump_lvol} /dev/vg00

# lvlnboot -v /dev/vg00

verify it's ok

# vgchange -a n /dev/vg00

Reboot the system - it should work if you could do all the above.

[R.L]

Hi Vincent, Marc, Bruce, Dan and Peggy.

The system has recovered.
Your help is highly appreciated.

Cheers,
R.L