OVA Deployment Fails at 100% with HTTP 500 and “LBA Out of Range” Errors from Storage Controller
search cancel

OVA Deployment Fails at 100% with HTTP 500 and “LBA Out of Range” Errors from Storage Controller

book

Article ID: 405547

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms

  • Deployment of an OVA template from a backup vendor progresses to 100% but fails with: “Invalid response code: 500”

vCenter logs -

/var/log/vmware/vpxd/vpxd.log 

2025-07-15T08:51:56.719Z error vpxd[2226146] [Originator@6876 sub=Default opID=6995bfca-01] [VpxLRO] -- ERROR task-1918982 --  -- VirtualMachine -- ResourcePool.ImportVAppLRO: :vim.fault.OvfImportFailed
--> Result:
--> (vim.fault.OvfImportFailed) {
-->    faultCause = (vmodl.fault.SystemError) {
-->       faultCause = (vmodl.MethodFault) null,
-->       faultMessage = (vmodl.LocalizableMessage) [
-->          (vmodl.LocalizableMessage) {
-->             key = "com.vmware.ovfs.ovfs-main.ovfs.transfer_failed",
-->             arg = (vmodl.KeyAnyValue) [
-->                (vmodl.KeyAnyValue) {
-->                   key = "0",
-->                   value = "Could not complete network copy for file /vmfs/volumes/63e12044-########-####-88e9a4600d78//contentlib-6db3bc1b-####-####-####-2ff31f032a1d/30dfcf4c-####-####-####-21179f228478/VSNAP-10.#.##-1##-disk2_66bac0de-####-####-####-8ff352ba973b.vmdk"
-->                }
-->             ],
-->             message = "Transfer failed: Could not complete network copy for file/vmfs/volumes/63e12044-########-####-88e9a4600d78//contentlib-6db3bc1b-####-####-####-2ff31f032a1d/30dfcf4c-####-####-####-21179f228478/VSNAP-10.#.##-1##-disk2_66bac0de-####-####-####-8ff352ba973b.vmdk"
-->          }
-->       ],
-->       reason = ""
-->       msg = "Transfer failed: Could not complete network copy for file /vmfs/volumes/63e12044-########-####-88e9a4600d78//contentlib-6db3bc1b-####-####-####-2ff31f032a1d/30dfcf4c-####-####-####-21179f228478/VSNAP-10.#.##-1##-disk2_66bac0de-####-####-####-8ff352ba973b.vmdk"
-->    },
-->    faultMessage = <unset>
-->    msg = ""
--> }
--> Args:
-->

  • Content Library logs report "Service_Unavailable" due to failed import session.

/var/log/vmware/content-library/cls.log 

2025-07-15T08:51:56.462Z | ERROR    | mcbo####-4005381-auto-2dukm-h5:70271851-72-01 | cls-simple-activity-19    | ImportSessionActivity          | OVF import session 45ea1941-####-####-####-981d5e1fa1e6 failed with server error.
com.vmware.vapi.std.errors.ServiceUnavailable: ServiceUnavailable (com.vmware.vapi.std.errors.service_unavailable) => {
    messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
    id = com.vmware.ovfs.ovfs-main.ovfs.transfer_failed,
    defaultMessage = Transfer failed: Could not complete network copy for file  /vmfs/volumes/63e12044-########-####-88e9a4600d78//contentlib-6db3bc1b-####-####-####-2ff31f032a1d/30dfcf4c-####-####-####-21179f228478/VSNAP-10.#.##-1##-disk2_66bac0de-####-####-####-8ff352ba973b.vmdk,
    args = [Could not complete network copy for file /vmfs/volumes/63e12044-########-####-88e9a4600d78//contentlib-6db3bc1b-####-####-####-2ff31f032a1d/30dfcf4c-####-####-####-21179f228478/VSNAP-10.#.##-1##-disk2_66bac0de-####-####-####-8ff352ba973b.vmdk],
    params = <null>,
    localized = <null>
}],
    data = <null>,
    errorType = SERVICE_UNAVAILABLE
}

ESXi logs - 

  • /var/log/hostd.log - show long VMDK operations and dirty buffer warnings:

2025-07-07T09:37:14.460Z warning hostd[2101947] [Originator@6876 sub=IoTracker opID=mcboivnp-2427884-auto-1g1d9-h5:70172758-17-25-958f] In thread 2102012, unlink("/vmfs/volumes/66a7af84-########-####-88e9a4600d78/VirtualMachine/VirtualMachine-flat.vmdk") took over 1329 sec.

2025-07-09T09:51:57.533Z info hostd[2101970] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 13927 : Issue detected on <esxihost> in ha-datacenter: BC: 3177: File VSNAP-10.#.##-1##-flat.vmdk closed with dirty buffers. Possible data loss.

  • /var/log/vmkernel.log - display SCSI errors with:
    • ASC/ASCQ 0x21/0x00 (Logical Block Address Out of Range)

2025-07-07T08:34:49.489Z cpu43:2098200)ScsiDeviceIO: 4176: Cmd(0x45d90fd12188) 0x8a, CmdSN 0x9f82383 from world 11359600 to dev "naa.60050#####################" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x21 0x0

  • May see errors similar to the following in your ESXi logs /var/log/vmkernel.log
ScsiDeviceIO: WRITE command failed ... Valid sense data: 0x5 0x21 0x0 smartpqi02: os_raid_response_error: status=0x2
    • These indicate the storage controller has rejected the write request due to addressing a non-existent block, which lies outside the valid range configured for that volume.

 

Environment

VMware ESXi 7.x

Cause

The failure occurs because the ESXi host attempts to write to a disk block that is outside the valid Logical Block Address (LBA) range defined for the volume. This triggers a rejection from the storage controller.

This behavior is typically seen when:

  • Volume metadata is corrupted.

  • The LUN is misconfigured or resized incorrectly.

  • There’s a firmware or driver issue with the RAID/storage controller.

  • The underlying storage medium has physical issues.

SCSI sense data in the logs (/var/log/vmkernel.log) shows: 

2025-07-07T08:34:49.489Z cpu46:2111579)smartpqi02: pqisrc_show_sense_data_simple:0164: [ERR INFO] BTL: 1:0:1 op=0x8a path=Raid K:C:Q: 5:21:0

SCSI Sense Code: 0x5/0x21/0x00 - Meaning: Illegal Request – LBA Out of Range

These messages indicate the storage device could not fulfill a valid write operation due to inconsistencies in the LUN mapping or data layout.

 

Resolution

Engage storage and/or RAID controller vendor to investigate potential LBA mapping or hardware integrity issues.

Note: The issue originates outside the ESXi stack. Until the backend storage issue is resolved, retrying the OVA deployment will likely result in repeated failures.

Powered by Wolken Software