Cannot boot /stand/vmunix

[Rob Saunders]

I've (cold) installed 11i on an L-class and subsequently built it as part of a cluster. All was working well (on both sides of the cluster) until I rebooted the standby node. I ran cmhaltnode prior to rebooting the system to suspend the MCSG functions on that node, however the system gets no further than the ISL prompt with the message: "disk(0/0/2/0/0.2.0.0.0.0.0)/stand/vmunix cannot open or has no execute permission"

Running a recovery shell, with chroot_lvmdisk ... etc... I can access /stand, vmunix both exists and has 755 permissions.

Trying to boot from the alternate yields exactly the same result.

I have moved previous versions of the kernel into position all with the same effects.

Any ideas??!(I'd rather not have to reinstall the whole system again if possible as I can see the LVs from the recovery shell.)

[Tim D Fulford]

Did you try /stand/vmunix.prev?

Tim

[Martin Johnson]

Have you verified the boot path is correct?

HTH
Marty

[Tim D Fulford]

Some thoughts here...
1 - When you mirrored up the root disks did you do "lvlnboot -R" to recover links?
2 - If the answer to 1 is no try at isl> prompt "hpux -lq -lm" (no quorum & LVM maintainance mode).
3 - what do you get from the PDC level when you do "sea ipl"? Does it detect the boot disks.
4 - Try booting without external disks attached!

If all fails, If the L is part of a cluster, and the other machines 11i (should be, if it is a cluster), Ignite-UX is pritty quick.

Tim

[Martha Mueller]

Is the root filesystem trying to mount as read-only? Check /etc/fstab.

I also heard a story while I was attending a Sun class. They had found that if a # (comment) was the first character in the fstab file, and on a line by itself, it exhibited the same symptoms you describe...simply failed to boot.

[Bill McNAMARA_1]

what is the output of
lvlnboot -v

incorrect config of this is most likely your problem...

Later,
Bill

[Rob Saunders]

Thanks for all responses folks, I've checked out the various suggestions, but all to no avail. I ended up resolving this one with an Ignite tape.

This is my first experience with 11i on L's - So far I'm not impressed... I tried the reboot on the second node in the cluster and this behaved in exactly the same way. (At least I'm consistent in building them :-) ) Now, where did I put that tape ?