"HostDatastoreSystem.CreateNasDatastore"

gs1uk
gs1uk used Ask the Experts™
on
Hi Experts,

 I'm not able to add a NFS Share on my ESXi 4.1. Apparently i was using this share for vDR.  i used to backup all the files to this iOmega-x200i drive and all a sudden it was greyed out. If I try to add it again i get the below error. Can you please help me out.

Call "HostDatastoreSystem.CreateNasDatastore" for object "datastoreSystem-28" on vCenter Server "vCenter" failed.
Operation failed, diagnostics report: Unable to complete Sysinfo operation.  Please see the VMkernel log file for more details.


Many Thanks
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Have you changed any permissions of configuration on the NAS, this error is usually because NFS is not enabled, or you are using the incorrect mount/share name.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
ah, okay, you've mounted this once before but it's greyed out, this sometimes can happen, unmount the old datastore name, and try remounting again.

Author

Commented:
Hi,

Nothing had been changed Im been using this nas just as a share drive for vDR. im using the same name im have used..

Thanks
11/26 Forrester Webinar: Savings for Enterprise

How can your organization benefit from savings just by replacing your legacy backup solutions with Acronis' #CyberProtection? Join Forrester's Joe Branca and Ryan Davis from Acronis live as they explain how you can too.

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
See my second post. Check Inventory Datastores, have you removed the old grayed out mounted NFS datastore?

Does the old one still exist?

Author

Commented:
I have unmounted it long back when i was trying to fix this issue. Now there is no such drive or name in the datastores ..

But when I add I still get this error

"Create NAS datastore An error occurred during host configuration."

Thanks
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
okay, we will need to check the vmkernel logs, no changes on either NAS or ESX server, not changed any vSwitches,  VMKernel port, Turned on Firewall?

Author

Commented:
No changes at all. This just happen yesterday during the night. :(

How do i get the vmkernel logs please..

Thanks
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
you got vCenter?

Click Export System Logs?

Author

Commented:
Yea.. Ok i will do it.. After what should I do ?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
if you look through the vmkernel log, you'll see something like...

May  3 10:56:13 vmkernel: 4:19:06:07.879 cpu10:804820)NFS: 149: Command: (mount) Server: (nfsserver) IP: (172.16.xxx.yyy) Path: (datastore29) Label: (datastore29) Options: (None)
May  3 10:56:13 vmkernel: 4:19:06:07.881 cpu7:4103)WARNING: NFS: 213: Got error 13 from mount call
May  3 10:56:13 vmkernel: 4:19:06:07.881 cpu11:804820)WARNING: NFS: 959: MOUNT failed with MOUNT status 13 (Permission denied) trying to mount Server (nfsserver) Path (datastore29)
May  3 10:56:13 vmkernel: 4:19:06:07.881 cpu11:804820)NFS: 171: NFS mount nfsserver:datastore29 status: The mount request was denied by the NFS server. Check that the export exists and that the client is permitted to mount it

post those bits here, and lets see what's going on....this will tell us why, we are getting a permission denied.

Author

Commented:
Hi hanccocka,

Im generating the logs...

Meanwhile when I went to Home - Inventory - Storage - Datastores i can see the NFS datastore greyed out still and (inactive). How do i permanently remove it ?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Ah, okay.

This could be the reason, are you trying to add the datastore with the same name as before?

Author

Commented:
I removed it now .. one of the esx server had it in its storage. So now its gone for good (ithink). I changed many names to to add as a NFS share name. still same error
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
if you check the Inventory datastores, you'll see if it's still there.

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
upload the logs, when you are ready, another thing you can quickly do if you have access to the console, is try a vmkping <nas ip address> and see if it responds.

Author

Commented:
Sorry can you explain what path can i find this log you are specific about.. Im using esxi 4.1
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
did you use export system logs from vcenter or \var\logs

vmkernel

Author

Commented:
i exported from vcenter
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
the path on your workstation?

Author

Commented:
I found these logs :


May 14 21:52:40 vmkernel: 0:03:31:45.128 cpu5:8154)Vol3: 1604: Could not open device 'naa.60022190c5f43500115b9ca804570cda:8' for probing: Permission denied
May 14 21:52:40 vmkernel: 0:03:31:45.130 cpu5:8154)Vol3: 644: Could not open device 'naa.60022190c5f43500115b9ca804570cda:8' for volume open: Permission denied
May 14 21:52:40 vmkernel: 0:03:31:45.133 cpu5:8154)Vol3: 1604: Could not open device 'naa.60022190c5f43500115b9ca804570cda:5' for probing: Permission denied
May 14 21:52:40 vmkernel: 0:03:31:45.135 cpu5:8154)Vol3: 644: Could not open device 'naa.60022190c5f43500115b9ca804570cda:5' for volume open: Permission denied
May 14 21:52:40 vmkernel: 0:03:31:45.139 cpu5:8154)Vol3: 1604: Could not open device 'naa.60022190c5f43500115b9ca804570cda:6' for probing: Permission denied
May 14 21:52:40 vmkernel: 0:03:31:45.141 cpu5:8154)Vol3: 644: Could not open device 'naa.60022190c5f43500115b9ca804570cda:6' for volume open: Permission denied
May 14 21:52:40 Hostd: [2011-05-14 21:52:40.259 647D8B90 verbose 'Hostsvc::DatastoreSystem'] VmfsUpdate: got VMFS message [N11HostdCommon18VmkernelUpdateVmfsE:0x646d97b0] timestamp=12705569808 specific=0 name= label=
VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
is nfs running on the nas?

has the ip address changed?

can you resolve the dns name correctly?

check vmkping at the console with its ip address and dns name?

also check its not mounted ?

Author

Commented:
Hi hancoccka.

I got the fix from this form : http://communities.vmware.com/message/1594676

I changed my Static IP to DHCP and the dns was updated and im not able to get access to the nfs store.

Thanks a lot for you help to resolve it. you where every helpful

Cheers
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
glad its working

Author

Commented:
Thanks dude

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial