vpar boot failure - efi problem?

[DGXUNIXADMINS]

I believe we have caused our EFI signature on a SAN attached boot drive to change and become out of sync with the vpdb. When we try to boot the vpar, we now get the following error:

HP-UX Boot Loader for IPF -- Revision 2.029

Could not open file /stand/vmunix to check for a directory
Could not open /stand/vmunix

loading failed
HpuxLoader start failed -9223372036854775805

followed by this error:

vPar "vpar01" failed to load the kernel due to: non-bootable boot media; incorrect vPars software installed; or incorrect boot media EFI path in vPars database.

This was working fine. Any thoughts?

Thanks.

[DGXUNIXADMINS]

Also note, I am able to see the disk device at the nPar level and was able to vgimport the s2 volume without issue. I also verified the efi information on the disk (idisk -p /dev/rdsk/c#t#d# ) and it was OK. I also re-copied the vpdb to /stand on the disk (which didn't help).

[Mridul Shrivastava · Accepted solution]

Go to BFI boot manager and delete this entry and add this again like a fresh boot device.

This should resolve the issue.. I have seen similar cases in past which gets resolved after doing this.

[Mridul Shrivastava]

Go to EFI boot manager and delete this entry and add this again like a fresh boot device.

This should resolve the issue.. I have seen similar cases in past which gets resolved after doing this.

[Torsten.]

You cannot interact with EFI in a vPar environment. All you can do is to check the boot settings with the vPar commands (vparstatus, vparmodify).

[likid0]

But are you able to boot that partition in npar mode ?

if you get thar vpar to boot as an npar with no problems, then we can start looking at vpar related issues

[DGXUNIXADMINS]

The device is not bootable as an nPar or vPar. When I attempt to boot the device and get to the HPUX bootloader, I interupt the boot process, run an ls, and can't see /stand like I can on the other partitions (which is why I get the error about missing /stand/vmunix).

[likid0]

Then it looks you have a problem, with your boot label and its pointing to another place, or there is a problem with the stand filesystem, you can try and boot in lvm manteinance mode, activate vg00, fsck the fs, and finally do a lvlnboot -R vg00, and check whith a lvlnboot -v vg00 that, boot,root and swap are pointing to the correct HDW paths.