During the procedure to uninstall the Host Extension, PernixData FVP shows the error "Could not prepare host for uninstallation".
The error came up after a misconfiguration of FVP that made the FVP Cluster unavailable.
After updating the configuration, the FVP Cluster tab was reporting the Resources as unavailable.
To fix the problem we need to put the affected ESXi in Maintenance Mode.
SSH into the ESXi and run the uninstall script.
# cp /opt/pernixdata/bin/prnxuninstall.sh /tmp/ && /tmp/prnxuninstall.sh
The uninstall fails and the script ends with the error:
Could not prepare host for uninstallation.
To fix this matter is necessary to remove the affected VIB from the host, then install the Host Extension again.
To identify the VIBs installed in the ESXi host, type the command:
# esxcli software vib list
The pernixcore-vSphere5.0.0 is the VIB we need to remove. In this case the error shown during the FVP Host Extension uninstall process is due to a wrong FVP release installed (ESXi 5.0) in the ESXi 5.5 host.
First step is to stop the FVP daemon.
# /etc/init.d/prnxd stop
If you receive an error, go ahead with FVP VIB removal procedure. To remove the wrong VIB, the command esxcli is used.
esxcli software vib remove -n <vib_name>
# esxcli software vib remove -n "pernixcore-vSphere5.0.0"
Now upload the correct FVP Host Extension (ESXi 5.5) to the host and try to install new VIB again.
# esxcli software vib install -d /tmp/PernixData-host-extension-vSphere5.5.0_188.8.131.52-33868.zip
This time the installation is successful.
Reboot the ESXi host.
Looking at the vCenter Server's FVP Cluster section, the fixed host is now reported as working.
Exit the ESXi from Maintenance Mode.
Repeat the same procedure for the second host member of the FVP Cluster.
After fixing both hosts, PernixData FVP Cluster started working again.
Check if all accelerated VMs/Datastore are working as expected and no errors are reported.