Problem Description
Backups for NFS shares failed with the following error:
Error Code 265:Failed to mount NAS device with given details.
Attempts to use the mount and showmount commands on the newer Linux NAS proxy were unsuccessful because these commands were unavailable.
Cause
The newer Linux NAS proxy lacked the required rpcbind service and nfs-utils package, which are essential for accessing NFS shares.
Also the NAS proxy’s IP address was not included in the allowed list on the NFS storage device.
Resolution
Step 1: Install Required Packages and Services
Verify if the rpcbind service and nfs-utils package are installed:
rpm -qa | grep nfs-utils
systemctl status rpcbindIf not installed, use the following command to install nfs-utils:
yum install nfs-utilsNote: If the server lacks internet access and returns a 500 error, reach to your Unix team to install the nfs-utils package manually using an offline repository or alternate method.
Once installed, start the rpcbind service:
systemctl start rpcbind
systemctl enable rpcbind
Step 2: Verify NFS Shares
After installing the required package and starting the service, use the following command to check available shares on the NFS device:
showmount -e DeviceName
Step 3: Mount the NFS Share Manually
Use the following command to manually mount the NFS share and verify connectivity:
mount -t nfs Devicename:/SharePath/ /mnt/
If this fails, proceed to Step 4.
Step 4: Address Access Permissions
If the manual mount fails due to permissions, enable verbose debugging to identify the issue:
mount -t nfs -o vers=4,tcp Devicename:/SharePath/ /mnt/ --verbose
If the error indicates restricted access for the proxy’s IP: Request the storage team to add the proxy’s IP to the allowed list on the NFS device.
Step 5: Test Backups
Once access permissions are updated:
Verify the manual mount command works without errors.
Test the backup process to ensure it completes successfully.