An NSS volume might not be found by the ncpcon utility if the volume’s mount point is renamed (the directory path is changed). For example, this might occur if you change the mount point’s directory path from /media/nss/volumename (the default path) to /targetpath/volumename.
When an NSS volume is created, the NCP server gets the path to the volume and caches it, assuming that it never changes. When you later run the NCP Console (ncpcon) utility and enter the volume command, it reports the volumes that are still found at their respective mount points. Only the volumes that are still valid as compared to the list in cache are reported.
Use the following methods to avoid or resolve this problem:
If you know in advance that you want to modify default path of the volume’s mount point, make sure to create the NSS volume with iManager and change the default mount point as you configure the volume. For example, if you are setting up an NSS volume to use for the home directories, change the mount point from /media/nss/home to /home.
Creating the volume in NSSMU does not allow for the mount point to be changed during the volume setup, only afterwards.
To modify the mount point for an existing volume, you can use either iManager or NSSMU to change it, then restart eDirectory by entering the following at a terminal console prompt:
Restarting eDirectory causes the NCP volume cache to be updated.