Sometimes, when an NFS server is rebooted or off for a while, the volume will remain inactive or inaccessible and greyed out in vCenter\/vSphere. To restore an inactive NFS volume in ESXi version 5.x, after obviously verifying that the NFS server is in fact up, do the following from the command line:<\/p>\n
List the mounted volumes:<\/p>\n
~ # esxcli storage nfs list
\nVolume Name Host Share Accessible Mounted Read-Only Hardware Acceleration
\n———– ————- —– ———- ——- ——— ———————
\nnfsvol1 192.168.0.251 \/nfs1 false true false Unknown
\nnfsvol2 192.168.0.251 \/nfs2 false true false Unknown\n<\/p><\/blockquote>\nThen, remove the volumes:<\/p>\n
~ # esxcli storage nfs remove -v nfsvol1
\n~ # esxcli storage nfs remove -v nfsvol2
\n~ # esxcli storage nfs remove -v nfsvol2\n<\/p><\/blockquote>\nList to ensure that all inactive or accessible volumes are gone:<\/p>\n
~ # esxcli storage nfs list<\/p><\/blockquote>\n
Add or mount the storage:<\/p>\n
~ # esxcli storage nfs add -H 192.168.0.251 -s \/nfs1 -v nfsvol1
\n~ # esxcli storage nfs add -H 192.168.0.251 -s \/nfs2 -v nfsvol2\n<\/p><\/blockquote>\nAnd list again to verify that the volumes are mounted:<\/p>\n
~ # esxcli storage nfs list
\nVolume Name Host Share Accessible Mounted Read-Only Hardware Acceleration
\n———– ————- —– ———- ——- ——— ———————
\nnfsvol1 192.168.0.251 \/nfs1 true true false Not Supported
\nnfsvol2 192.168.0.251 \/nfs2 true true false Not Supported <\/p><\/blockquote>\nNote: You can achieve the same thing by remounting the volumes through the vCenter UI, but why when the command is so much more fun? Besides, in the UI, you might get an error that doesn’t seem to happen from the command line.<\/p>\n","protected":false},"excerpt":{"rendered":"
Sometimes, when an NFS server is rebooted or off for a while, the volume will remain inactive or inaccessible and greyed out in vCenter\/vSphere. To restore an inactive NFS volume in ESXi version 5.x, after obviously verifying that the NFS server is in fact up, do the following from the command line: List the mounted [&hellip<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[386,33],"class_list":["post-1162","post","type-post","status-publish","format-standard","hentry","category-documentation","tag-nfs","tag-vmware"],"share_on_mastodon":{"url":"","error":""},"_links":{"self":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts\/1162","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1162"}],"version-history":[{"count":3,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts\/1162\/revisions"}],"predecessor-version":[{"id":1165,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts\/1162\/revisions\/1165"}],"wp:attachment":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1162"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1162"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1162"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}