Search the VMware Knowledge Base (KB)
View by Article ID

Upgrading to ESX Server 3 Version 3.5 When the Root Partition Is Nearly Full Might Cause Incomplete System Configuration (1003311)

  • 10 Ratings


When you upgrade to ESX Server 3 version 3.5, the system configuration might be incomplete. In some cases, the upgrade might appear to be successful, but networking will not work. The log files (for example, /var/log/vmware/esxcfg-boot.log) might contain error messages such as No space left on device and No such file or directory. This issue is caused by insufficient temporary disk space. A typical upgrade from ESX Server 3.0.x to ESX Server 3.5 requires over 100MB of temporary space.


You can restore network capability to the service console by running the esxcfg-vswitch and esxcfg-vswif commands. These commands allow you to perform remote maintenance--for example, copying out vm-support files. After you clean out or expand the root partition, VMware recommends that you perform a clean upgrade.

In general, VMware recommends that you back up the root partition before you perform an upgrade. If space is insufficient, check for and remove excess files in directories that tend to accumulate files, such as /tmp and /var/log. Also, consider installing ESX Server on a larger partition.

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.


  • 10 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? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 10 Ratings