{"id":11916,"date":"2015-02-16T09:00:00","date_gmt":"2015-02-16T08:00:00","guid":{"rendered":"http:\/\/nolabnoparty.com\/?p=11916"},"modified":"2015-02-16T14:31:43","modified_gmt":"2015-02-16T13:31:43","slug":"pernixdata-fvp-could-not-prepare-host-for-uninstallation","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/pernixdata-fvp-could-not-prepare-host-for-uninstallation\/","title":{"rendered":"PernixData FVP \"Could not prepare host for uninstallation\""},"content":{"rendered":"

\"pernixdatauninstallerror01\"<\/p>\n

During the procedure to uninstall the Host Extension, PernixData FVP shows the error \"Could not prepare host for uninstallation\".<\/p>\n

The error came up after a misconfiguration of FVP that made the FVP Cluster unavailable.<\/p>\n

<\/p>\n

After updating the configuration, the FVP Cluster tab was reporting the Resources as unavailable<\/strong>.<\/p>\n

\"pernixdatauninstallerror02\"<\/p>\n

 <\/p>\n

Procedure<\/h2>\n

To fix the problem we need to put the affected ESXi in Maintenance Mode<\/strong>.<\/p>\n

\"pernixdatauninstallerror03\"<\/p>\n

SSH<\/strong> into the ESXi and run the uninstall script.<\/p>\n

# cp \/opt\/pernixdata\/bin\/prnxuninstall.sh \/tmp\/ && \/tmp\/prnxuninstall.sh<\/span><\/p>\n

\"pernixdatauninstallerror04\"<\/p>\n

The uninstall fails and the script ends with the\u00a0error:<\/p>\n

Could not prepare host for uninstallation.<\/p><\/blockquote>\n

To fix this matter is necessary to remove the affected VIB from the host, then install the Host Extension again.<\/p>\n

To identify the VIBs installed<\/strong> in the ESXi host, type the command:<\/p>\n

# esxcli software vib list<\/span><\/p>\n

\"pernixdatauninstallerror05\"<\/p>\n

The pernixcore-vSphere5.0.0<\/strong> is the VIB we need to remove. In this case the error shown during the FVP Host Extension uninstall process is due to a\u00a0wrong FVP release installed\u00a0(ESXi 5.0) in the ESXi 5.5 host.<\/p>\n

First step is to stop the FVP daemon<\/strong>.<\/p>\n

# \/etc\/init.d\/prnxd stop<\/span><\/p>\n

\"pernixdatauninstallerror06\"<\/p>\n

If you receive an error, go ahead with FVP VIB removal procedure. To remove the wrong VIB<\/strong>, the\u00a0command esxcli is used.<\/p>\n

esxcli software vib remove -n <vib_name><\/p><\/blockquote>\n

# esxcli software vib remove -n \"pernixcore-vSphere5.0.0\"<\/span><\/p>\n

\"pernixdatauninstallerror07\"<\/p>\n

Now upload the correct FVP Host Extension (ESXi 5.5) to the host and try to install new VIB<\/strong> again.<\/p>\n

# esxcli software vib install -d \/tmp\/PernixData-host-extension-vSphere5.5.0_2.0.1.0-33868.zip<\/span><\/p>\n

\"pernixdatauninstallerror08\"<\/p>\n

This time the installation is successful.<\/p>\n

Reboot<\/strong> the ESXi host.<\/p>\n

# reboot<\/span><\/p>\n

\"pernixdatauninstallerror09\"<\/p>\n

Looking at the vCenter Server's FVP Cluster section<\/strong>, the fixed host is now reported as working.<\/p>\n

\"pernixdatauninstallerror10\"<\/p>\n

Exit the ESXi from Maintenance Mode.<\/p>\n

\"pernixdatauninstallerror11\"<\/p>\n

Repeat the same procedure<\/strong>\u00a0for the second host member of the FVP Cluster.<\/p>\n

\"pernixdatauninstallerror12\"<\/p>\n

After fixing both hosts, PernixData FVP Cluster started working again.<\/p>\n

\"pernixdatauninstallerror13\"<\/p>\n

Check if all accelerated VMs\/Datastore are working as expected and no errors are reported.<\/p>\n

\"firma\"<\/p>\n","protected":false},"excerpt":{"rendered":"

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.<\/p>\n","protected":false},"author":3,"featured_media":11903,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[987,903],"tags":[1517,961,960],"class_list":["post-11916","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pernixdata-en","category-vmware-en","tag-could-not-prepare-host-for-uninstallation-en","tag-fvp-en","tag-pernixdata-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/11916","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=11916"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/11916\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/11903"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=11916"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=11916"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=11916"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}