I'm having a strange issue with NFS and I am surely overlooking something obvious, even though I've been using NFS for 20 years. So here goes:

 

I'm trying to mount /mnt/disk2 onto one of my machines. In order to identify each disk, I've made the following files:

 

root@leng:/mnt# ls disk*/I_am*
disk1/I_am_disk1  
disk2/I_am_disk2  
disk3/I_am_disk3  
disk4/I_am_disk4  
disk5/I_am_disk5  
disk6/I_am_disk6  
disk7/I_am_disk7

 

My NFS exports, as automatically built by unRAID:

 

root@leng:/mnt# exportfs -v
/mnt/disk1    	<world>(rw,async,wdelay,no_root_squash,all_squash,no_subtree_check,anonuid=0,anongid=0)
/mnt/disk2    	<world>(rw,async,wdelay,no_root_squash,all_squash,no_subtree_check,anonuid=0,anongid=0)
/mnt/disk3    	<world>(rw,async,wdelay,no_root_squash,all_squash,no_subtree_check,anonuid=0,anongid=0)
/mnt/disk4    	<world>(rw,async,wdelay,no_root_squash,all_squash,no_subtree_check,anonuid=0,anongid=0)
/mnt/disk5    	<world>(rw,async,wdelay,no_root_squash,all_squash,no_subtree_check,anonuid=0,anongid=0)
/mnt/disk6    	<world>(rw,async,wdelay,no_root_squash,all_squash,no_subtree_check,anonuid=0,anongid=0)
/mnt/disk7    	<world>(rw,async,wdelay,no_root_squash,all_squash,no_subtree_check,anonuid=0,anongid=0)

 

On the machine where I am mounting the disks:

 

[root@ws1 mnt]$ mount | grep disk
leng:/mnt/disk1 on /mnt/disk1 type nfs (rw,addr=10.8.2.5)
leng:/mnt/disk2 on /mnt/disk2 type nfs (rw,addr=10.8.2.5)
leng:/mnt/disk3 on /mnt/disk3 type nfs (rw,addr=10.8.2.5)
leng:/mnt/disk4 on /mnt/disk4 type nfs (rw,addr=10.8.2.5)
leng:/mnt/disk5 on /mnt/disk5 type nfs (rw,addr=10.8.2.5)
leng:/mnt/disk6 on /mnt/disk6 type nfs (rw,addr=10.8.2.5)
leng:/mnt/disk7 on /mnt/disk7 type nfs (rw,addr=10.8.2.5)

 

But look at the ID files I placed on each disk:

 

[root@ws1 mnt]$ ls disk*/I_am*
disk1/I_am_disk1  
disk2/I_am_disk1  
disk3/I_am_disk3  
disk4/I_am_disk4  
disk5/I_am_disk5  
disk6/I_am_disk6  
disk7/I_am_disk7

 

Note that disk2 is disk1. No matter what I do, this keeps happening, I can't seem to access disk2 by NFS. Now mind you, I did mount disk2 via NFS when I first put all my data onto it. I have tried rebooting both the unRAID server and this Linux workstation, to no avail. What am I missing?

I will add that it works just fine over Samba. 

What does the actual /etc/exports file look like on the unRAID server?

Here's the exports file, as requested. I don't see anything out of kilter, sadly.

 

root@leng:~# cat /etc/exports
# See exports(5) for a description.
# This file contains a list of all directories exported to other computers.
# It is used by rpc.nfsd and rpc.mountd.

"/mnt/disk1" -async,no_subtree_check,anongid=0,anonuid=0,all_squash *(rw,no_root_squash)
"/mnt/disk2" -async,no_subtree_check,anongid=0,anonuid=0,all_squash *(rw,no_root_squash)
"/mnt/disk3" -async,no_subtree_check,anongid=0,anonuid=0,all_squash *(rw,no_root_squash)
"/mnt/disk4" -async,no_subtree_check,anongid=0,anonuid=0,all_squash *(rw,no_root_squash)
"/mnt/disk5" -async,no_subtree_check,anongid=0,anonuid=0,all_squash *(rw,no_root_squash)
"/mnt/disk6" -async,no_subtree_check,anongid=0,anonuid=0,all_squash *(rw,no_root_squash)
"/mnt/disk7" -async,no_subtree_check,anongid=0,anonuid=0,all_squash *(rw,no_root_squash)

Nobody?  :'(

I did a full shutdown of everything in my house (vacation for 2 weeks) and the problem persists after returning home. Any ideas? I'm stuck, and it's really annoying not to be able to use a disk.

I know you have posted here, but have you sent an e-mail to support@lime-technology??

 

Who knows, there might be a patch to NFS available.

 

It might be that the wrong disk is being exported, or it might be that the wrong disk is being imported by your other PC.

 

Perhaps boot up another PC, even if only on a "live" CD and see if disk2 can be imported.

 

Joe L.