Latest Unity VSA won't boot

That is odd.

If it deploys correctly but then doesn't see the disks, sounds like possible configuration issues.

I would start with the UVSA Install guide:

http://www.emc.com/collateral/TechnicalDocument/docu69316.pdf

- Make sure all the install requirements are met.

- Make sure the deployment settings are correct (if the settings are not in line with the guide, the VM may not boot).

Did you see this part in the guide, for example:

"Using vSphere to modify the physical configuration of a UnityVSA VM (such as adding or removing network interfaces or modifying the VM's cache size) is not supported, except for adding virtual disks to store user data.

When you create the UnityVSA VM, three virtual disks (vmdks) are automatically created for the VM's system data. (These are always the virtual disks identified as 1-3.) Do not modify or delete these disks.

You must add at least one virtual disk for user data."

Actually, the deployment guide says to power the VM on first, before adding the user data VMDK's.  My host meets the minimum requirements, and I did not change any settings during the deployment.  The only non-default settings chosen was the IP address. 

It does see the disks.  I can go into the VMware BIOS and see them.  It just doesn't boot from them... 

I'm going to try downloading the OVA again.

Most likely the deployment failed which may be why it is not seeing boot sector on the vmdk. Any clue from the esx "Task&Events" information at the time of ova deployment?.

Redoing the ova deploy should help.

Maybe this here helps http://blog.mdschneider.me/unityvsa-part-1-html5-ftw/