Hello,
I had already configured and working NFS (from windows server, using SFU), before my VI Infrastructure crash. Now when I try to mount the datastore from VirtualCenter, receive following message box error
"Error during the configuration of the host: Cannot open volume: /vmfs/volumes/323513cc-2394148d "
I have tried to use the same old datastore name, and a new name, but the error always occurs.
Does anyone may help me, please ?
Thanks in advance,
regards Davide
You may want to follow this thread: to see if steps describe so far help you or if a resolution has been found
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at:
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
Hi,
I have already read and followed the thread, without any effect. Hereafter, the ls -la /vmfs/volumes of my hosts, with a very strange value of accused volume. Are there any way to delete this ?
drwxr-xr-x 1 root root 512 Jun 5 16:29 .
drwxrwxrwt 1 root root 512 Jun 4 10:52 ..
drwx------ 1 4294967294 4294967294 64 Jun 5 12:51 323513cc-2394148d <----
******* this is the datastore that appears in the error message *******
drwxr-xr-t 1 root root 1260 May 18 15:00 488a3ff4-c0616acc-8d82-001a64d19406
drwxr-xr-t 1 root root 2520 May 18 14:59 488ddc43-a19a18f2-9662-001a64d19406
drwxr-xr-t 1 root root 2380 May 18 15:02 48e3b149-f3ba0aee-01d3-001a64d19406
drwxr-xr-t 1 root root 1680 May 28 15:46 49df1b7b-512d430c-72ca-001a64d19404
lrwxr-xr-x 1 root root 35 Jun 5 16:29 HMS1Datastore -> 48e3b149-f3ba0aee-01d3-001a64d19406
lrwxr-xr-x 1 root root 35 Jun 5 16:29 HMS2Datastore -> 49df1b7b-512d430c-72ca-001a64d19404
lrwxr-xr-x 1 root root 35 Jun 5 16:29 HMSDatastore -> 488ddc43-a19a18f2-9662-001a64d19406
lrwxr-xr-x 1 root root 17 Jun 5 16:29 isoimg -> 323513cc-2394148d
lrwxr-xr-x 1 root root 35 Jun 5 16:29 labinfesx1:storage1 -> 488a3ff4-c0616acc-8d82-001a64d19406
thanks
Davide
Do you get any output from:
esxcfg-nas -l
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at:
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
I have deleted from Veeam FastSCP the /vmfs/volumes/isoimg link, but this has not delete the corresponding special file /vmfs/volumes/323513cc-2394148d
Error performing operation: Unable to create object, volume Name not valid
I have not solved my problem yet. All NFS server/client configuration and setup are ok. On ESX server I have the following situation under /vmfs/volume
lrwxr-xr-x 1 root root 17 Jul 21 10:44 isoimg -> 323513cc-2394148d
drwx------ 1 4294967294 4294967294 64 Jun 5 12:51 323513cc-2394148d
and I think my problem is that I cannot able to remove the folder named " 323513cc-2394148d".
I have tried chown unsuccesfull (permission denied).
Are there any other way to solve this problem ?
Thanks in advance
regards Davide
I have solved. One problem was the "User Name Mapping" service on NFS server was stopped.
I have NFS shared the folder with a new name.
At this point I have created a new mountpoint on ESX, and the system has mount a new and also a old NFS filesystem, as you see below:
lrwxr-xr-x 1 root root 17 Jul 21 11:21 isoimages -> afb696fd-ee5de6af
lrwxr-xr-x 1 root root 17 Jul 21 11:21 isoimg -> 323513cc-2394148d
If i list the content of isoimg (the older name) I can see the content.
But,now I have the duplicated entry.
Davide