Article number
Affected Versions
Source Hypervisor
Target Hypervisor

Error ‘Loadstatus: No Such File Or Directory’ During VRA Installation

Viewed 1016 times


This article describes a scenario in which a VRA installation may fail due to the /tmp directory on the host being full.

Root Cause

When installing the zDriver, Zerto uses the /tmp folder to upload files to.

The directory named "/tmp" is used to store temporary files that other applications can utilize as well. Any files in here after a host reboot will be removed and the space is reclaimed.

When the /tmp space is full, we will get this error from the Hostd log and the zDriver will not upload properly:

info hostd[2106050] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 5746 : The ramdisk 'tmp' is full.  As a result, the file /tmp/ could not be written.

Additionally, if Secure Boot is enabled on the host, this issue can also occur.


A VRA install fails with the following error:

scp:/vmfs/volumes/<datastore-name>/zagentid/343437383036584d5138323730364346_<hostname>/loadstatus: No such file or directory


To workaround this issue, follow the steps below:

  1. Ensure Secure Boot is disabled. Log on to the ESXi host via SSH and run the following command. The output will be either 'enabled' or 'disabled': 

    1. /usr/lib/vmware/secureboot/bin/ -s

  2. Check the /tmp folder available space. Log on to the ESXi host via SSH and run the following command to verify the space available in the ramdisk /tmp. Move/delete files/folders no longer needed in this directory and try the VRA install again once space is reclaimed: 

    1. vdf -h

Note: The /tmp space is hardcoded by the OS image installed on the host, so increasing this space is not an option.