Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2635
  • Last Modified:

vmware esxi 4.0 to 4.1 update error - no space left on device

disclaimer - I realize I'm not following the vmware guide, but several people indicate this method should work.

i've transfered the upgrade 4.0 to 4.1 zip file to my esxi 4.0 datastore, then tried running the esxupdate command on it.  I get the following:

/vmfs/volumes # esxupdate --bundle=/vmfs/volumes/datastore1/upgrade-from-ESXi4.0-to-4.1.0-                                           0.0.260247-release.zip check
Encountered error FileIOError:
The error data is:
   Filename    - None
   Message     - I/O Error (28) on file : [Errno 28] No space left on device
   Errno       - 10
   Description - Unable to create, write or read a file as expected.
close failed: [Errno 28] No space left on device
/vmfs/volumes # cd /

a df -h shows the following
~ # df -h
Filesystem                Size      Used Available Use% Mounted on
visorfs                 215.9M    190.7M     25.2M  88% /
vmfs3                   831.3G    214.5G    616.7G  26% /vmfs/volumes/4b06a69b-40c5b230-3803-001517af2f89
vfat                    249.7M      4.0k    249.7M   0% /vmfs/volumes/bab1ed7a-4a23e078-152c-4e5b336b93cd
vfat                    249.7M     59.3M    190.4M  24% /vmfs/volumes/96cf367a-a6349a90-d8e7-bf20ad127c94
vfat                      4.0G         0      4.0G   0% /vmfs/volumes/4b06a686-6b8379ea-18b5-001517af2f89
vfat                    285.9M    230.2M     55.7M  81% /vmfs/volumes/efd8efe3-03bc1cbf-15e0-080efd9e7379


I'm sure it's complaining about the visorfs partition (which seems to be a ramdisk, from my googling), but I don't know how or why it's using that.

Help?
0
snowdog_2112
Asked:
snowdog_2112
  • 4
  • 3
1 Solution
 
PenguinNCommented:
It looks like one of these two form the problem
vfat                      4.0G         0      4.0G   0% /vmfs/volumes/4b06a686-6b8379ea-18b5-001517af2f89
vfat                    249.7M      4.0k    249.7M   0% /vmfs/volumes/bab1ed7a-4a23e078-152c-4e5b336b93cd

You SHould also checkout whats in there.
0
 
snowdog_2112Author Commented:
I've seen other posts, however, that talk about the visorfs and not being able to expand the update.

Those other 2 vfat entries would be user-configured (i.e., I created them), right?
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
snowdog_2112Author Commented:

Solution
Run vm-support pointing to a VMFS store with sufficient disk space as the working directory (vm-support -w <path>).

That's pretty light on specifics.  Does that also work with the esxupdate command? What is an example of <path> that would be acceptable?
0
 
PenguinNCommented:
I don't know yet, but it's one of the few options you have. Make the partition larger or crate a temp dir where you can expand on a differeent partition. So i hope it works.
0
 
snowdog_2112Author Commented:
I ran the update using the rCLI tool - had to install it on a windows machine.

Installed using the procedures outlined in the docs.

This link provided a good example of the exact syntax from the windows machine:

http://communities.vmware.com/message/1572720 
0
 
snowdog_2112Author Commented:
Sorry mate, the link you provided makes no mention of esxupdate, and even at that, the command referenced had no supporting doc to provide any sort of meaningful direction (not even an example).  I appreciate the attempt.  I need to clear off the question.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now