{"id":8888,"date":"2014-04-29T12:46:40","date_gmt":"2014-04-29T11:46:40","guid":{"rendered":"http:\/\/nolabnoparty.com\/?p=8888"},"modified":"2023-07-16T11:22:04","modified_gmt":"2023-07-16T09:22:04","slug":"esxi-55-uninstall-update-1-fix-nfs-issue","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/esxi-55-uninstall-update-1-fix-nfs-issue\/","title":{"rendered":"ESXi 5.5: uninstall Update 1 to fix NFS issue"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter\" style=\"margin: 10px auto 5px; padding-left: 0px; padding-right: 0px; float: none; padding-top: 0px; border: 0px;\" title=\"removeupdate1esxi01\" alt=\"removeupdate1esxi01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2014\/04\/removeupdate1esxi01.jpg\" width=\"602\" height=\"202\" border=\"0\" \/><\/p>\n<p>The NFS disconnection bug in the ESXi 5.5 Update 1 (<a href=\"http:\/\/kb.vmware.com\/kb\/2076392\" target=\"_blank\" rel=\"noopener\">KB2076392<\/a>) has not been solved yet. The workaround is to <strong>uninstall Update 1<\/strong> to fix NFS issue.<\/p>\n<p>The re-installation of ESXi is not always the optimal solution, especially if you have several hosts in your network.<\/p>\n<p><!--more--><\/p>\n<p>The downgrade process <strong>without reinstalling the ESXi<\/strong> host can be achieved through <strong>esxcli<\/strong> as described in the <a href=\"http:\/\/www.v-front.de\/2014\/04\/struck-by-nfs-bug-here-is-how-to.html#more\" target=\"_blank\" rel=\"noopener\">Andreas Peetz\u2019s blog<\/a>.<\/p>\n<p>&nbsp;<\/p>\n<h2>Procedure<\/h2>\n<p>Enable <strong>SSH access<\/strong> on the ESXi 5.5 host.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter\" style=\"margin: 0px auto; padding-left: 0px; padding-right: 0px; float: none; padding-top: 0px; border: 0px;\" title=\"removeupdate1esxi02\" alt=\"removeupdate1esxi02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2014\/04\/removeupdate1esxi02.jpg\" width=\"600\" height=\"450\" border=\"0\" \/><\/p>\n<p>Note: The ESXi 5.5 <strong>build number 1746018<\/strong> means the host has latest patches already installed (Update 1 + <a href=\"http:\/\/kb.vmware.com\/selfservice\/microsites\/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=2076665\" target=\"_blank\" rel=\"noopener\">Heartbleed fix<\/a>).<\/p>\n<p>Using an <strong>SSH client<\/strong> (e.g. PuTTY), log in to the host.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter\" style=\"margin: 0px auto; padding-left: 0px; padding-right: 0px; float: none; padding-top: 0px; border-width: 0px;\" title=\"removeupdate1esxi03\" alt=\"removeupdate1esxi03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2014\/04\/removeupdate1esxi03.jpg\" width=\"600\" height=\"182\" border=\"0\" \/><\/p>\n<p>Open firewall port to allow outgoing <strong>http requests<\/strong>.<\/p>\n<p><span style=\"color: #0000a0;\"># esxcli network firewall ruleset set -e true -r httpClient<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter\" style=\"margin: 0px auto; padding-left: 0px; padding-right: 0px; float: none; padding-top: 0px; border-width: 0px;\" title=\"removeupdate1esxi04\" alt=\"removeupdate1esxi04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2014\/04\/removeupdate1esxi04.jpg\" width=\"600\" height=\"44\" border=\"0\" \/><\/p>\n<p>Install the ESXi 5.5 pre-Updated 1 + Heartbleed Fix Image Profile from the VMware <strong>online depot<\/strong>.<\/p>\n<p><span style=\"color: #0000a0;\"># esxcli software profile update -d https:\/\/hostupdate.vmware.com\/software\/VUM\/PRODUCTION\/main\/vmw-depot-index.xml -p ESXi-5.5.0-20140401020s-standard --allow-downgrades<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter\" style=\"margin: 0px auto; padding-left: 0px; padding-right: 0px; float: none; padding-top: 0px; border-width: 0px;\" title=\"removeupdate1esxi05\" alt=\"removeupdate1esxi05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2014\/04\/removeupdate1esxi05.jpg\" width=\"600\" height=\"243\" border=\"0\" \/><\/p>\n<p><strong>Reboot<\/strong> the host.<\/p>\n<p><span style=\"color: #0000a0;\"># reboot<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter\" style=\"margin: 0px auto; padding-left: 0px; padding-right: 0px; float: none; padding-top: 0px; border-width: 0px;\" title=\"removeupdate1esxi06\" alt=\"removeupdate1esxi06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2014\/04\/removeupdate1esxi06.jpg\" width=\"600\" height=\"35\" border=\"0\" \/><\/p>\n<p>Once rebooted, the host ESXi 5.5 <strong>build number changes to 1746974<\/strong>. This procedure downgrade the host ESXi to 5.5 GA version <strong>keeping all security fixes<\/strong> released so far, Heartbleeding fix included.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter\" style=\"margin: 0px auto; padding-left: 0px; padding-right: 0px; float: none; padding-top: 0px; border: 0px;\" title=\"removeupdate1esxi07\" alt=\"removeupdate1esxi07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2014\/04\/removeupdate1esxi07.jpg\" width=\"600\" height=\"248\" border=\"0\" \/><\/p>\n<p>If you didn't upgrade the host to Update 1, to apply the Heartbleed fix only (without Update 1) you can use <strong>same command<\/strong> omitting <em>--allow-downgrades <\/em>option.<\/p>\n<p><img decoding=\"async\" alt=\"firma\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" title=\"\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The NFS disconnection bug in the ESXi 5.5 Update 1 (KB2076392) has not been solved yet. The workaround is to uninstall Update 1 to fix NFS issue. The re-installation of ESXi is not always the optimal solution, especially if you have several hosts in your network.<\/p>\n","protected":false},"author":3,"featured_media":8881,"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":[903,2701],"tags":[885,879,875],"class_list":["post-8888","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsphere-en","tag-datastore","tag-esxi-5-5-en","tag-update-1-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/8888","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=8888"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/8888\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/8881"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=8888"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=8888"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=8888"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}