VPAR Won't reboot by itself - but will boot by vparload at MON

[cuppajo]

This new vpar on a dome was cloned from another like vpar. I have been able to boot it up, set up the vpar, all seems fine, but it won't come back up on it's own when I enter "shutdown -r 0". The setboot, lvlnboot, and vparefiutil settings all seem to be in agreement on the path of the boot drive, and autoboot is on. When it tries to come up after the reboot command, it says this on the console, right after initializing the cells:

*********************************************

Rebooting (vparname)...press any key within 10 seconds to stop boot (sits here for a minute or two)

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

Try using "vparload -p (vparname) -E 0" to load the vPar.

Error loading "(vparname)". Shutting down "(vparname)"...

[MON] (vparname) has halted.

**********************************************


Then it sends me to the MON prompt. At the MON, I enter "vparload -p (vpar name)" and it comes up fine. No -E or other switches needed. I have tried delting vparefiutil and updating it a few times, and verified that it is updating to the correct boot disk partition information.

This is an 11.31 server, by the way.

Ideas?

[SUDHAKAR_18]

Can you please provide #vparstatus output from any other running vpar ?