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.