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:
2019-04-16T23:30:31.025Z info hostd[2106050] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 5746 : The ramdisk 'tmp' is full. As a result, the file /tmp/zloadmod.sh could not be written.
Additionally, if Secure Boot is enabled on the host, this issue can also occur.
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:
2019-04-16T23:30:31.025Z info hostd[2106050] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 5746 : The ramdisk 'tmp' is full. As a result, the file /tmp/zloadmod.sh could not be written.
Additionally, if Secure Boot is enabled on the host, this issue can also occur.
Symptoms
A VRA install fails with the following error:
scp:/vmfs/volumes/<datastore-name>/zagentid/343437383036584d5138323730364346_<hostname>/loadstatus: No such file or directory
scp:/vmfs/volumes/<datastore-name>/zagentid/343437383036584d5138323730364346_<hostname>/loadstatus: No such file or directory
Solution
- Ensure Secure Boot is disabled.
- Check the space used for /tmp. Have the customer move/delete files/folders no longer needed in this directory and try the VRA install again once the space is reclaimed.
The Linux command "vdf -h" can be used that will print out the Total/Used/Free capacity of each partition on each disk.
It should also be noted that the /tmp space is hard coded by the OS image installed on the host, so increasing this space is not an option.