Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

Changing MBR in a Scripted Upgrade Produces an Anaconda Exception

Details

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.

Solution

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.

Keywords

relnotes

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   
Actions
  • KB Article: 7926780
  • Updated: Aug 14, 2009
  • Products:
    VMware ESX
  • Product Versions:
    VMware ESX 3.0.x