Patch "ESXi500-201112001.zip" corrupt?

[martinelli99]

Hello everybody,

when trying to install the latest patch for ESXi 5, I get this error:

esxcli software vib install --maintenance-mode --depot ESXi500-201112001.zip
[MetadataDownloadError]
Could not download from depot at zip:/var/log/vmware/ESXi500-201112001.zip?index.xml, skipping (('zip:/var/log/vmware/ESXi500-201112001.zip?index.xml', '', "Error extracting index.xml from /var/log/vmware/ESXi500-201112001.zip: [Errno 2] No such file or directory: '/var/log/vmware/ESXi500-201112001.zip'"))
        url = zip:/var/log/vmware/ESXi500-201112001.zip?index.xml
Please refer to the log file for more details.

Downloading this patch a different time - because maybe corrupted while downloading - didn't help, although md5sum is correct.

Does anyone know, if there is a problem with this file? Installing the first patches worked without any problems on this host.

Thanks in advance

Regards

martinelli

<42>

[vmroyale]

Hello.

Where is the ESXi500-201112001.zip file actually sitting on the file system - what directory?

I wrote a blog entry not too long ago that might be helpful.

Good Luck!

[martinelli99]

Hi,

different tries, first one with zip on my (local) SSD, from where I started the esxcli-command, then the same

from my iSCSI-Target.

When I execute "esxcli" from /root-dir I named the complete path after "--depot". Both doesn't work.

Again - Installing the first patches didn't make any problems.

With your blog I learned to use "esxcli" for updating my server, so I know this very well, thank you for that!

Regards

martinelli

<42>

[martinelli99]

Hello everybody,

for me I found a solution: Originally I have had an Installation on a USB-Stick (4 GB), more than enough

space for running ESXi 5. Also enough for installing Patch 1 und Patch 2.

But while trying to install Patch No. 3, vmkernel.log shows me, "insufficient space ...". So I changed the

whole installation to a 60 GB SSD and everything is fine, with all the patches.

Now I'm sure, the patch   i s   n o t  corrupt!

Regards
martinelli

[a_p_]

Out of curiosity, did you have the persistent scratch location configured while running the Hypervisor from the USB-Stick?

see http://kb.vmware.com/kb/1033696

André

[martinelli99]

Don't know, cannot check, because of the changed installation-method. But it should have been located

on the SSD, which was already installed as a Backup-Disk for my Virtual Machines, when I ran ESXi from

USB-Stick. And afaik does ESXi configure scratch and log-location automatically on everything "better"

than a stick. Am I right?

And btw - what is the scratch(-setting) good for?

martinelli

<42>

[a_p_]

And afaik does ESXi configure scratch and log-location automatically on everything "better" than a stick. Am I right?

No, the default 4GB scratch partition will only be created if ESXi is installed on disk or SAN, not on USB even if it was large enough. If ESXi is installed on an USB/SD device you have to define the scratch location manually.

And btw - what is the scratch(-setting) good for?

As explained in the KB article I posted, by default all data will be kept in the RAM disk without a scratch partition/location. Since space is limited this can lead to an out-of-disk-space situation like the one you experienced.

André

[martinelli99]

... oh oh, one should read everything...

So I will check again an installation on a Stick, with a persistent

scratch location and then patch 3.

Thanks for your hint!

Regards

Thomas

Message was edited by: a.p. - fixed title and removed email attachment

[a_p_]

So I will check again an installation on a Stick, with a persistent scratch location and then patch 3.

Please let us know what you find out.

André

PS: Genau die richtige Arbeit für einen trüben Sonntag Nachmittag

[martinelli99]

Hi André

I'm sorry for the delay, but there was so much to do on the job (new ESX-Servers, new SAN...) 

Now I set up a test machine, with the same configuration: no disk, boot from an 2 GB USB-Stick and

without a configured scratch partition.

But here I was able to install patch 3 after installing patch 1 and patch 2 without any problems!

Don't know what went wrong with my main machine. Maybe I have to install all the patches before

configuring the rest?

Perhaps I install my server once again, I will observe this situation and have to check the scratch

settings when the error occurs again.

Thanks again!

Best regards

martinelli

[martinelli99]

And now another try the final! - with my main server - the "patch corrupt"-messages appears already while trying to

install patch #1!

After connecting a SSD to the server, the scratch directory was created automatically (after rebooting the system)

and everything was fine, I was able to install all the three patches.

So André was right thanks for that again!

Regards

martinelli

[tonyshawn27]

Obviously cannot open zip file denotes file is corrupted. You would to use tool below

Zip file repair

it helps you to get back archives to proper condition and doesn't change source file data before corruption