I have an HP DL380 G8 with two arrays on the 410i controller (one is a mirrored 146G set and the other a 300G set.)
I am running the latest firmware. This is a production machine. Windows Server 2008 is installed on the 146G partition.
Because it is the only capable machine we have as a virtual host, I installed another set of drives, installed ESXi 5.5 hypervisor, and can easily choose to boot to either volume.
The intent is to virtualize the same Windows 2008 on this other drive set. I had a perfectly good VMware conversion running on the datastore (which I worked on quite a bit but thankfully didn't go live.) I needed to boot back into the actual Windows installation for a couple days and when I booted back to VMware I got "Bank6: Not a VMWare boot bank. No hypervisor found."
VMware's knowledgebase says to reformat!!! Arrrg!
So, I can recreate what I did, but why oh why did Microsoft mess up my VMware drive? What can I do to keep this from happening again if I need to boot back into the other volume? I can see the volumes in Windows (in fact, it assigned drive letters to the FAT partitions, which messed up my network drive mappings (oops, I didn't think of that.) Can anyone tell me what the heck happened and how to avoid it? (or even better - have a fix?) I'm proficient with Linux as well by the way. Thanks