{"id":1640,"date":"2015-04-16T13:14:17","date_gmt":"2015-04-16T12:14:17","guid":{"rendered":"http:\/\/www.bussink.ch\/?p=1640"},"modified":"2018-05-23T17:57:37","modified_gmt":"2018-05-23T15:57:37","slug":"nfs-volume-mounting-error-following-a-network-change","status":"publish","type":"post","link":"https:\/\/www.bussink.ch\/?p=1640","title":{"rendered":"NFS volume mounting error following a network change"},"content":{"rendered":"<p>I recently redesigned my network configuration from a single \/24 address range to multiple \/24 ranges with routing done on my core switch. Part of this change meant shutdown the vSphere cluster, and the storage arrays (Synology) and reassigning new IP addresses and gateways to all of these entities.<\/p>\n<p>When my hosts and my storage arrays had their new IP addresses and I attempted to re-map my NFS volumes to the Synology, I got a strange error message while attempting to mount my NFS volumes. &#8220;<strong>There are incorrect or missing values below.<\/strong>&#8221;<\/p>\n<p><a href=\"http:\/\/www.bussink.ch\/wp-content\/uploads\/\/2015\/04\/unable_to_mount_nfs_point_webgui.jpg\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1641\" src=\"http:\/\/www.bussink.ch\/wp-content\/uploads\/\/2015\/04\/unable_to_mount_nfs_point_webgui.jpg\" alt=\"Unable to mount NFS point in vSphere Web Client\" width=\"634\" height=\"515\" srcset=\"https:\/\/www.bussink.ch\/wp-content\/uploads\/2015\/04\/unable_to_mount_nfs_point_webgui.jpg 634w, https:\/\/www.bussink.ch\/wp-content\/uploads\/2015\/04\/unable_to_mount_nfs_point_webgui-300x244.jpg 300w\" sizes=\"(max-width: 634px) 100vw, 634px\" \/><\/a><\/p>\n<p>Another error message &#8220;<strong>Unable to add new NAS, volume with the label X already exists<\/strong>&#8221; was given on the ESXi shell when I attempted the same operations using a SSH session directly on my host.<\/p>\n<p><a href=\"http:\/\/www.bussink.ch\/wp-content\/uploads\/\/2015\/04\/Unable-to-add-new-NAS-volume-with-the-label-already-exists.jpg\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1642\" src=\"http:\/\/www.bussink.ch\/wp-content\/uploads\/\/2015\/04\/Unable-to-add-new-NAS-volume-with-the-label-already-exists.jpg\" alt=\"Unable to add new NAS volume with the label already exists\" width=\"806\" height=\"37\" srcset=\"https:\/\/www.bussink.ch\/wp-content\/uploads\/2015\/04\/Unable-to-add-new-NAS-volume-with-the-label-already-exists.jpg 806w, https:\/\/www.bussink.ch\/wp-content\/uploads\/2015\/04\/Unable-to-add-new-NAS-volume-with-the-label-already-exists-300x14.jpg 300w\" sizes=\"(max-width: 806px) 100vw, 806px\" \/><\/a><\/p>\n<p>Yet the <strong>esxcfg-nas -l<\/strong> command did not return any values.<\/p>\n<p>Well it seems that the old NAS entry is still in the ESXi host, but not listed. To fix this small issue, you need to delete the non-existing NFS mount point and recreate it.<\/p>\n<p>In the next screenshot you see me listing my mount points, attempting to mount a new NFS volume (legolas_nfs), erasing the non-visible entry, and at last adding the new NFS volume.<\/p>\n<p><a href=\"http:\/\/www.bussink.ch\/wp-content\/uploads\/\/2015\/04\/erasing_nfs_ghost_mount_point_2.jpg\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1644\" src=\"http:\/\/www.bussink.ch\/wp-content\/uploads\/\/2015\/04\/erasing_nfs_ghost_mount_point_2.jpg\" alt=\"erasing_nfs_ghost_mount_point_2\" width=\"901\" height=\"319\" srcset=\"https:\/\/www.bussink.ch\/wp-content\/uploads\/2015\/04\/erasing_nfs_ghost_mount_point_2.jpg 901w, https:\/\/www.bussink.ch\/wp-content\/uploads\/2015\/04\/erasing_nfs_ghost_mount_point_2-300x106.jpg 300w\" sizes=\"(max-width: 901px) 100vw, 901px\" \/><\/a><\/p>\n<p>I hope this can save someone some\u00a0precious time.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I recently redesigned my network configuration from a single \/24 address range to multiple \/24 ranges with routing done on my core switch. Part of this change meant shutdown the vSphere cluster, and the storage arrays (Synology) and reassigning new IP addresses and gateways to all of these entities. When my hosts and my storage [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":1645,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[9],"tags":[108,203,202,204,99],"_links":{"self":[{"href":"https:\/\/www.bussink.ch\/index.php?rest_route=\/wp\/v2\/posts\/1640"}],"collection":[{"href":"https:\/\/www.bussink.ch\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bussink.ch\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bussink.ch\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bussink.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1640"}],"version-history":[{"count":1,"href":"https:\/\/www.bussink.ch\/index.php?rest_route=\/wp\/v2\/posts\/1640\/revisions"}],"predecessor-version":[{"id":1646,"href":"https:\/\/www.bussink.ch\/index.php?rest_route=\/wp\/v2\/posts\/1640\/revisions\/1646"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.bussink.ch\/index.php?rest_route=\/wp\/v2\/media\/1645"}],"wp:attachment":[{"href":"https:\/\/www.bussink.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1640"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bussink.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1640"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bussink.ch\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1640"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}