Error During The Configuration Of The Host Cannot Open Volume
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this
Operation Failed, Diagnostics Report: Cannot Open Volume
site About Us Learn more about Stack Overflow the company Business Learn more call "hostdatastoresystem.createnasdatastore" for object about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault the mount request was denied by the nfs server netapp is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer https://kb.vmware.com/kb/1008591 The best answers are voted up and rise to the top ESX NFS error "Cannot open volume: /vmfs/volumes/ up vote 1 down vote favorite I'm trying to add an NFS share to my ESX 5.5 server. When I try to add the share, I get the following error: Call "HostDatastoreSystem.CreateNasDatastore" for object "ha-datastoresystem" on ESXi "[ESX Server's IP address]" failed. Operation failed, diagnostics report: Cannot open http://serverfault.com/questions/674776/esx-nfs-error-cannot-open-volume-vmfs-volumes volume: /vmfs/volumes/07188eae-a88dc069 I'm fairly certain that the VMKernel is setup correctly, because when I vmkping the NFS server using the CLI, I get replies. When I did some googleing, I read that it might be a firewall issue. I went to the Security Profile page under configuration, and found that the NFS Client was not allowed in the firewall. I added it to the allowed outgoing connections and specified "all" as the allowed IP addresses. I then attempted to add the NFS share again, and got the same error. Upon looking at the Security Profile again, the NFS Client was no longer allowed through the firewall. vmware-esxi vmware-esx share|improve this question asked Mar 12 '15 at 1:02 Evan Goldstein 62 What have you entered for the mount properties ("Server" and "Folder")? –VFrontDe Mar 12 '15 at 7:38 @VFrontDe "server" is the hostname of the nfs server, which is a Windows Small Business Server 2008, and the folder is the name if the share I set up (folder properties --> NFS sharing tab). –Evan Goldstein Mar 13 '15 at 15:38 Check this forums thread, it should help: communities.vmware.com/message/2461528 &
error after setting up and FlexVolume on a Netapp filer and trying to connect to it from vSphere ESX host. I had run through the wizard and made sure that each of the ESX hosts https://karciauskas.wordpress.com/2010/02/18/error-during-the-configuration-of-the-host-cannot-open-volume-vmfsvolumes/ had read/write access as well as “Root” access to the export/volume but I continued to get this error: “Error during the configuration of the host: Cannot open volume: /vmfs/volumes/270c64e8-cae0114b” Originally I thought it http://mindwatering.com/SupportRef.nsf/webpg/9947AEA5621C5BC1852576AC00148343 may be that I had underscores in my export name as described in the Vmware KB article. I changed the export name to something without an underscore but still no dice. It turns error during out even if you specify Unix security when creating the export, the Netapp filer will create it using NTFS by default! Why it sets the underlying security to NTFS on a NFS export with Unix security is beyond me. It may be the version of OnTap on our old dev filer (7.2.6.1) To change this you need to do the following: Logon to your filer web management error during the interface Expand “Volumes” Expand “Qtrees” Click “Manage” Click on the “NTFS” link next to the export you need to change Change the security style to “Unix” and then apply Go back to your host and try adding the NFS volume I recommended getting familiar with this Netapp and vSphere best practices document as well. Like this:Like Loading... Related This entry was posted on February 18, 2010, 3:28 pm and is filed under NetApp, Vmware. You can follow any responses to this entry through RSS 2.0. You can leave a response, or trackback from your own site. Comments (9) #1 by Rob on February 24, 2010 - 4:22 pm I had been looking everywhere for a solution to this error, your suggestion is just what I needed! Reply #2 by Ben Karciauskas on February 24, 2010 - 5:35 pm Hey your welcome. Thanks for the comment Cheers, Ben Reply #3 by Tony L on May 18, 2010 - 9:46 pm Thanks Ben this was a lifesaver! Reply #4 by Luis on June 14, 2010 - 5:08 pm Thank you very much! We had been trying and trying to figure out this one. What's strange is that we have to N
backup and recoveryLotus Notes / Domino Appsfree Lotus Notes apps hosting web site hostingLotus application hostingcheck your mailrequest a hosting quote training training overviewLotus Notes whiteboard drawingsLotus admin & dev training sound client services billing orders and invoicesbilling & payment policiescopyright & liability policiespricing & turnaround policiesprivacy statementhelp & support contact e-mail MWget filessend files Error on ESX / ESXi 3.5x or 4.0x Host Adding NSF Storage Mindwatering Incorporated Tripp W Black on 01/14/2010 at 10:44 PM Category: VMWare Storage - NFS Issue: You are adding a NSF share/storage to your VMware environment. When you complete the wizard, you get the error: "Error during the configuration of the host: Cannot open volume; /vmfs/volumes/.....". Solution: This is a permissions issue. If it is only on one ESXi or ESX server, then you mostly like have a client group issue on the NFS storage box. Go to the list of allowed clients and add the IP address of the ESX server denied. (/etc/exports on NFS server) example: $ sudo vi /etc/exports /local/myshare 192.168.99.99(rw,sync,no_subtree_check,no_root_squash) or /local/myshare 192.168.99.0/24(rw,async,no_wdelay,nohide,no_subtree_check,no_root_squash)