VMware Cloud Community
wfletcher2
Contributor
Contributor

Cannot map NFS drive esx 3.5

I had an esx 3.5 server which unfortunately died, hardware failure. I rebuilt the server and went to connect to the NFS share through the VC gui on the new machine to no avail. I then tried the esxcfg command line which did map the drive, but nothing on it can be seen. The NFS share is on a 2k3 machine (not R2) with Services for Unix installed.

I cannot delete or rename anything on the NFS share through windows. I can view the file conrtents though.

I really need to access the drive and the machines on it. I now receive the error "The specified key, name identifier already exists", when I try to remap it through the GUI. I can see the volume name in winscp, but nothing under it.

Any ideas on how I can get my NFS share back up and running with the machines already build on it?

Thanx up front.

0 Kudos
4 Replies
Texiwill
Leadership
Leadership

Hello,

Verify your SFU configuration first: http://www.astroarch.com/wiki/index.php/Setting_up_Windows_Services_For_UNIX_%28SFU%29_NFS

Then unmount (Remove) the NFS Datastore, then remount (Add) the NFS datastore.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education. As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos
wfletcher2
Contributor
Contributor

Tried that last night. I could never get the map to come up. Had to do it through the Dos command line. Nothing there has changed. Just rechecked and thru the command line and the share is still there and mapped to root.

What I did find using the esxcfg-nas -l was

# esxcfg-nas -l

\Error performing operation: Unable to create object, volume Name not valid

# esxcfg-nas -d f3842be6-65269d04

Error performing operation: Unknown filesystem, cannot remove

old name of the nfs share was 0acf02ae-48dc9c31

esxcfg isn't letting me rename it

# esxcfg-nas -s 0acf02ae-48dc9c31

esxcfg-nas Set the name of the NAS share on the remote system.

-d|--delete Unmount and delete a filesystem.

-l|--list List the currently mounted NAS file systems.

-r|--restore Restore all NAS mounts from the configuration file.

(FOR INTERNAL USE ONLY).

-h|--help Show this message.

# esxcfg-nas -s f3842be6-65269d04

esxcfg-nas Set the name of the NAS share on the remote system.

-d|--delete Unmount and delete a filesystem.

-l|--list List the currently mounted NAS file systems.

-r|--restore Restore all NAS mounts from the configuration file.

(FOR INTERNAL USE ONLY).

-h|--help Show this message.

0 Kudos
Texiwill
Leadership
Leadership

Hello,

That could not be the old Name of the Share. It is the UID for the share. THe share name should be the mount point name.

If 'esxcfg-nas -l' returns an error then you have something more of an issue going on. I suggest you contact VMware Support. I would run 'vm-support' and you may have to reboot the server or remove the vmkernel module for NAS.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education. As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos
nechai2
Contributor
Contributor

see "nfs volume name not valid 3.5" for a possible solution

http://communities.vmware.com/message/1099064#1099064

/nechai2

0 Kudos