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/dat
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-40c
vfat 249.7M 4.0k 249.7M 0% /vmfs/volumes/bab1ed7a-4a2
vfat 249.7M 59.3M 190.4M 24% /vmfs/volumes/96cf367a-a63
vfat 4.0G 0 4.0G 0% /vmfs/volumes/4b06a686-6b8
vfat 285.9M 230.2M 55.7M 81% /vmfs/volumes/efd8efe3-03b
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?
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/dat
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-40c
vfat 249.7M 4.0k 249.7M 0% /vmfs/volumes/bab1ed7a-4a2
vfat 249.7M 59.3M 190.4M 24% /vmfs/volumes/96cf367a-a63
vfat 4.0G 0 4.0G 0% /vmfs/volumes/4b06a686-6b8
vfat 285.9M 230.2M 55.7M 81% /vmfs/volumes/efd8efe3-03b
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?
ASKER
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?
Those other 2 vfat entries would be user-configured (i.e., I created them), right?
Check this article for a solution
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010611
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010611
ASKER
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?
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
vfat 4.0G 0 4.0G 0% /vmfs/volumes/4b06a686-6b8
vfat 249.7M 4.0k 249.7M 0% /vmfs/volumes/bab1ed7a-4a2
You SHould also checkout whats in there.