Upgrading ESXi 6.0 to 6.5 with I loose NFS storage?

Angry

Limp Gawd
Joined
Feb 27, 2006
Messages
481
So, while trying to setup NFS shares with ESXi 6.5, I ran into this issue...

ifqYDvS.jpg


the add Network File System option is missing, and reinstalling ESXi 6.5 did not fix it.
However, downgrading to 6.0 and the option is there and works.

Will I loose the option again if I do and "upgrade" to 6.5? and will I loose any settings?
 
Yep. At least in 6.5...

... 6.0 doesnt have the web client....unfortunately.

The web client is mostly why I want 6.5
 
NFS can be added through the web client on ESXI 6.5 It cannot be added via the local client.

Well, Fudge....Ill have to check that out then....I coulda swore I looked, I may have been a little frustrated at that point though and had a feeling it was something simple.
 
Yep. At least in 6.5...

... 6.0 doesnt have the web client....unfortunately.

The web client is mostly why I want 6.5
6 Does have a web client if you are using vCenter. 6 update 2 I believe introduced the standalone web client.
 
They've deprecated the C++ client starting 6.5, as the new standalone web client will be superseding it. If you go to the standalone web client, you can still add/mount NFS datastores just fine:

upload_2017-2-6_16-19-15.png


Same goes for VCenter for 6.5:

upload_2017-2-6_16-19-46.png
 
lots of frustration with the web client... but it does work.
 
  • Like
Reactions: Angry
like this
I haven't had a chance to upgrade ESXi from 6.0 to 6.5 yet.
I want to clone the drive esxi is installed on before I try the upgrade.

I played around with upgrading ESXI 6.0 to 6.5 in virtualbox and it broke everytime with a pink screen of death.
But I think it's a issue between 6.5 and virtual box. I can install 6.0 just fine, 6.5 I cant...can't upgrade 6.0 to 6.5 either.
 
I would avoid NFS 4.1 unless there is something you need specifically. For me, NFS3 has always been rock solid. Several days ago, I changed my 6.0U2 server to use NFS4.1. Over the next couple of days, all kinds of issues. SVmotions failing, various operations on guests failing with 'in the wrong state', power on of guests taking (literally) minutes. The scary thing was when SVMotion would fail, I'd be left with a corrupted vmdk. I started poking through the logs, and saw a ton of message like these:

vmkernel.5:2017-02-26T03:30:52.294Z cpu23:35099)NFS41: NFS41FileOpenFile:2783: Open of 0x4302e5f99200 with openFlags 0x2 failed: Busy

vmkernel.7:2017-02-25T17:25:23.678Z cpu26:44070)WARNING: NFS41: NFS41FileOpCloseFile:3460: NFS41FileCloseFile failed: Stale file handle

I can't honestly say this is vsphere's fault - possibly the CentOS 7 host serving up the datastore. I don't really care though. I didn't need NFS4.1, so I switched back to NFS3 and it's been (again) rock solid...

A further thought: I forgot to mention I found a couple of guys on reddit who had similar issues awhile back. They were also serving up via linux, so that's still on the table...
 
Last edited:
  • Like
Reactions: Angry
like this
Back
Top