- Advertisement -
HomeVirtualizationVMwareCould not download from depot at zip... Error extracting index.xml

Could not download from depot at zip... Error extracting index.xml

Problem:

Could not download from depot at zip

While using offline software bundles, you are unable to install an async driver or latest upgrades on the ESXi host using the command line (CLI).

You see:

  • Could not download from depot at zip
  • Error extracting index.xml
  • No such file or directory

Example from an ESXi upgrade attempt.

[root@ESXi:~] esxcli software profile update -p ESXi-6.7.0-20190402001-standard -d /vmfs/volumes/5afa57a0-5eb07a05-89f7-001b21bc2484/update2.zip
 [MetadataDownloadError]
 Could not download from depot at zip:/vmfs/volumes/5afa57a0-5eb07a05-89f7-001b21bc2484/update2.zip?index.xml, skipping (('zip:/vmfs/volumes/5afa57a0-5eb07a05-89f7-001b21bc2484/update2.zip?index.xml', '', "Error extracting index.xml from /vmfs/volumes/5afa57a0-5eb07a05-89f7-001b21bc2484/update2.zip: [Errno 2] No such file or directory: '/vmfs/volumes/5afa57a0-5eb07a05-89f7-001b21bc2484/update2.zip'"))
        url = zip:/vmfs/volumes/5afa57a0-5eb07a05-89f7-001b21bc2484/update2.zip?index.xml
Please refer to the log file for more details.

Possible solutions:

  • If you are performing an online upgrade, verify the gateway and DNS settings of your ESXi host.
  • Ensure that the OS driver/datastore is not full. If it is, try freeing space.
  • Make sure your ESXi host is in maintenance mode
  • Check and double-check the esxcli command syntax.
  • Do not run the command from the datastore location. The path specified must be absolute, ensure to use the full path to the zip file.
  • Try using a local ESXi datastore.
  • Try using the Datastore UUID.

Example of a proper command line:

  • vib updates:

esxcli software vib update -d /vmfs/volumes/datastore_name/vib_update.zip
  • Version upgrades:

esxcli software profile update -p Image_Profile_Name -d /vmfs/volumes/datastore_name/ESXi_Upgrade_File.zip

Image Profile Names (Ex. for ESXi 6.7 U2):

  • ESXi-6.7.0-20190402001-standard
  • ESXi-6.7.0-20190402001-no-tools
  • ESXi-6.7.0-20190401001s-standard
  • ESXi-6.7.0-20190401001s-no-tools

Choose your profile image according to the downloaded version, check the VMware release notes for the latest updates and official label.

Juan Mulford
Juan Mulford
I have been active in IT for over fourteen years now. I am a solutions architect, working with storage, virtualization, and VDI solutions. For the past ten years, I have been living and working in Taiwan.

11 COMMENTS

  1. I am using an absolute path but it produces the same error. I am able to cd to each of the levels successfully so it is not a typo…frustrating…:

    [root@localhost:~] cd vmfs
    [root@localhost:/vmfs] cd volumes
    [root@localhost:/vmfs/volumes] cd InternalRAID6
    [root@localhost:/vmfs/volumes/5db984ee-64230b9b-a683-801844ef8366] cd Updates
    [root@localhost:/vmfs/volumes/5db984ee-64230b9b-a683-801844ef8366/Updates]
    [root@localhost:/vmfs/volumes/5db984ee-64230b9b-a683-801844ef8366/Updates] cd \

    [root@localhost:~] esxcli storage vmfs extent list
    Volume Name VMFS UUID Extent Number Device Name Partition
    ————- ———————————– ————- ———————————— ———
    InternalRAID6 5db984ee-64230b9b-a683-801844ef8366 0 naa.6d094660379c840023f2cbb9237ee95d 1

    [root@localhost:~] esxcli software vib update -d /vmfs/volumes/InternalRAID6/Upd
    ates/ESXi670-201912001.ZIP
    [MetadataDownloadError]
    Could not download from depot at zip:/vmfs/volumes/InternalRAID6/Updates/ESXi670-201912001.ZIP?index.xml, skipping ((‘zip:/vmfs/volumes/InternalRAID6/Updates/ESXi670-201912001.ZIP?index.xml’, ”, “Error extracting index.xml from /vmfs/volumes/InternalRAID6/Updates/ESXi670-201912001.ZIP: [Errno 2] No such file or directory: ‘/vmfs/volumes/InternalRAID6/Updates/ESXi670-201912001.ZIP'”))
    url = zip:/vmfs/volumes/InternalRAID6/Updates/ESXi670-201912001.ZIP?index.xml
    Please refer to the log file for more details.

    nuts

  2. I have faced the same issue before, and it seems the problem was that the datastore name having some white space, then i renamed into a signle word and it solved my problem.

    datastore name before: datastore1 (1)
    datastore name after: datastore1_esx1

  3. I ran this to install the FLING community drivers on ESXi 7. It says there isa problem..refer to the log. Where would the log be?

    [root@node71:~] esxcli software vib install -d /vmfs/volumes/384e78af-04d45456/iso/USBNIC/ESXi800-VMKUSB-NIC-FLING-61054763-component-20
    826251.zip
    [DependencyError]
    VIB VMW_bootbank_vmkusb-nic-fling_1.11-1vmw.800.1.20.61054763 requires vmkapi_2_10_0_0, but the requirement cannot be satisfied within the ImageProfile.
    VIB VMW_bootbank_vmkusb-nic-fling_1.11-1vmw.800.1.20.61054763 requires vmkapi_incompat_2_10_0_0, but the requirement cannot be satisfied within the ImageProfile.
    Please refer to the log file for more details.
    [root@node71:~]

  4. Could not download from depot at zip:/vmfs/volume/634c4469-60864260-3c61-00be43 8e3049/Release_28.0.zip?index.xml, skipping (('zip:/vmfs/volume/634c4469-6086426 0-3c61-00be438e3049/Release_28.0.zip?index.xml', '', "Error extracting index.xml from /vmfs/volume/634c4469-60864260-3c61-00be438e3049/Release_28.0.zip: [Errno 2] No such file or directory: '/vmfs/volume/634c4469-60864260-3c61-00be438e3049/ Release_28.0.zip'"))

    Thi is what I am getting after repeated trials from the datastore location and from the root directory. I used:
    esxcli software vib update -d /vmfs/volume/634c4469-60864260-3c61-00be438e3049/Release_28.0.zip.
    and
    esxcli software vib install -d /vmfs/volume/634c4469-60864260-3c61-00be438e3049/Release_28.0.zip.

    Please help me out in installing driver for my Intel Dual port NIC card (PT1000 Server Adapter)

Leave a Reply

- Advertisement -

Popular Articles

mulcas.com-Raspberry-Pi

Raspberry Pi OS in a Virtual Machine with VMware

4
Although the Raspberry Pi OS is designed and optimized for the Raspberry Pi module, it is possible to test and use it without its hardware, with VMware. This solution can be useful if you are a developer (or just a curious guy) and don't have a Raspberry Pi module with you
Unable to delete inaccessible datastore

Unable to delete an "inaccessible" datastore

7
I was switching my storage array, so I migrated the VMs from that old datastore/storage to a new datastore/storage. The old datastore was shared by 3 ESXi hosts, no cluster. After migrating the VMs and unmount/delete the datastore, it was still presented in two of the ESXi hosts and was marked as inaccessible.
This is not a valid source path / URL

This is not a valid source path / URL - SourceTree and Gitlab

0
I have been working on a project with a friend who set up a repository in Gitlab but even though I was able to view all projects on it, I couldn’t really join the repository. I was using SourceTree and Gitlab.
mulcas.com-VMware-OVF-Tool

How to export a Virtual Machine using the VMware OVF Tool

9
The VMware OVF Tool is implemented by VMware for easily importing and exporting virtual machines in Open Virtualization Format (OVF) standard format. Here, I want to show you how to download and install it, and then how to use it from a Windows machine.
Couldn't load private key - Putty key format too new

Couldn't load private key - Putty key format too new

5
couldn't load private key - Putty key format too new.” This issue happens when you use PuTTygen to generate or convert to a ppk key. Here is how to fix it. 
- Advertisement -

Recent Comments