The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Changing MBR in a Scripted Upgrade Produces an Anaconda Exception (7926780)
If you change the location of the master boot record (MBR) in the kickstart file for a scripted upgrade from ESX Server 2.x or 3.0 to ESX Server 3.0.1 or higher, the scripted installation fails with an anaconda exception before it completes.
When upgrading from ESX Server 2.x or 3.0 to ESX Server 3.0.1 or higher, do not select a new location for the MBR. Keep the location you used when you installed ESX Server 2.x or 3.0.
In ESX Server 3.0.2, the installer is enhanced to select the location where the MBR was previously installed in ESX Server 2.x, 3.0, or 3.0.1.
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.