NFS mount failed permission denied

[falynxfx]

Im getting the following error when trying to mount an NFS folder on my 1u4500:
mount: 192.168.1.112:/raid0/data/test failed, reason given by server: Permission denied

I hadn't been having any problems using NFS, then I switched to SMB because I added some windows users, now I just need NFS again so switched back and cant get it to work.
In the 1u4500 admin site I go to network > nfs, and confirmed that it is enabled, I even disabled and re-enabled to make sure.
In storage > folder, I go to my 'test' folder and go to edit, browseable 'yes', public 'yes', share limit '0'
On the NFS button for folder 'test' I have Mount point: [/raid0/data/test]
hostname '*', privilege 'rw', access as 'root user'

The mount command Im using from linux: mount -t nfs 192.168.1.112:/raid0/data/test /mnt

'showmount 192.168.1.112' gives 'Hosts on 192.168.1.112:'
'showmount --exports 192.168.1.112' gives 'Export list for 192.168.1.112:'
'rpcinfo -p 192.168.1.112' gives
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100011 1 udp 684 rquotad
100011 2 udp 684 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100021 1 udp 32768 nlockmgr
100021 3 udp 32768 nlockmgr
100021 4 udp 32768 nlockmgr
100021 1 tcp 32769 nlockmgr
100021 3 tcp 32769 nlockmgr
100021 4 tcp 32769 nlockmgr
100005 1 udp 696 mountd
100005 1 tcp 699 mountd
100005 2 udp 696 mountd
100005 2 tcp 699 mountd
100005 3 udp 696 mountd
100005 3 tcp 699 mountd

So NFS must be running, when I stop it and do the same command nothing shows up.

And yes I tried restarting the server several

I can't access the NFS share from other computer that used to be able to access it either

Any ideas?

[phishkiller]

I am having the same problem:


-bash-3.1# mount nas01:/raid0/data/pg -o tcp,nfsvers=3,intr /data/pg
mount: nas01:/raid0/data/pg failed, reason given by server: Permission denied



I've tried /raid/data/pg /raid0/data/pg /data/pg and /pg as the exported FS. None of them work, all of them toss the exact same message. Frustrating for certain.

No answer for you, but I'm certainly experiencing similar frustration. If you did get this resolved, what turned out to be the problem?

Just to add some additional diag info.


-bash-3.1# rpcinfo -p 10.1.1.200
  program vers proto   port
   100000    2   tcp    111  portmapper
   100000    2   udp    111  portmapper
   100011    1   udp    719  rquotad
   100011    2   udp    719  rquotad
   100003    2   udp   2049  nfs
   100003    3   udp   2049  nfs
   100003    2   tcp   2049  nfs
   100003    3   tcp   2049  nfs
   100021    1   udp  32770  nlockmgr
   100021    3   udp  32770  nlockmgr
   100021    4   udp  32770  nlockmgr
   100021    1   tcp  32769  nlockmgr
   100021    3   tcp  32769  nlockmgr
   100021    4   tcp  32769  nlockmgr
   100005    1   udp    920  mountd
   100005    1   tcp    923  mountd
   100005    2   udp    920  mountd
   100005    2   tcp    923  mountd
   100005    3   udp    920  mountd
   100005    3   tcp    923  mountd


-bash-3.1# showmount --exports 10.1.1.200
Export list for 10.1.1.200:


-bash-3.1# ping 10.1.1.200
PING 10.1.1.200 (10.1.1.200) 56(84) bytes of data.
64 bytes from 10.1.1.200: icmp_seq=1 ttl=64 time=0.155 ms
64 bytes from 10.1.1.200: icmp_seq=2 ttl=64 time=0.165 ms
64 bytes from 10.1.1.200: icmp_seq=3 ttl=64 time=0.122 ms
ç64 bytes from 10.1.1.200: icmp_seq=4 ttl=64 time=0.077 ms
64 bytes from 10.1.1.200: icmp_seq=5 ttl=64 time=0.158 ms

--- 10.1.1.200 ping statistics ---


NFS is running on the server. I can reach the IP 10.1.1.200 even switched the mount to 'public' and 'browsable' and still nothing. Rebooted server several times as well.

[omega]

Hi guys,

you've posted the reason already: the export list on your Thecus device is empty (see: showmounts -e <your-thecus>).

Now, the question is: why is your export list empty?
Try to check the contents of /etc/exports manually by logging in using SSH and then: cat /etc/exports.

Did you mark the shares to be exported by NFS?

Andreas

[phishkiller]

Yes. The shares are marked for NFS export. I even changed it to accept ANY host incase the system was not calculation subnet blocks correctly. Nothing.

Yes.. I realize the stupid thing is not exporting anything.... and the question is why.

I did upgrade to V2.00.1 of the firmware. Before that this share was able to be mounted by one of my systems. Maybe that version of the firmware is really hosed. It broke the SSL cert and I'm awaiting info from Thecus support on that.

Unless there is some new way to gain SSH access to the system.. I'm locked out. I followed the steps for creating the shell share and mounting it, then using ln to grain access but.. guess what.. no exported FS.. no way to finish creating SSH access.

Right now port 22 on the device is refusing connections.


-bash-3.1# telnet nasty 22
Trying 10.1.1.200...
telnet: connect to address 10.1.1.200: Connection refused
telnet: Unable to connect to remote host: Connection refused
-bash-3.1#


SMB/CIFS seems to quit working after a while too.. but restarts after a boot up. Of course nothing to that effect is shown in the logs...


2007/11/19 08:34:43 NASty : [Quota] Folder [/raid0/data/pg] add to Quota Management.
2007/11/19 08:32:50 NASty : User admin logged in from 29.14.114.202
2007/11/19 08:32:26 NASty : NASty boot
2007/11/19 08:32:06 NASty : Healthy: The system NASty is healthy now.
2007/11/19 08:32:03 NASty : mdadm: /dev/md1 has been started with 4 drives.
2007/11/19 08:32:03 NASty : [Disk sdd] UUID[raid5;7f66f7af:d9f78796:7548e455:76ec4dfb;Fri Sep 7 16:42:07 2007]
2007/11/19 08:32:03 NASty : [Disk sdc] UUID[raid5;7f66f7af:d9f78796:7548e455:76ec4dfb;Fri Sep 7 16:42:07 2007]
2007/11/19 08:32:03 NASty : [Disk sdb] UUID[raid5;7f66f7af:d9f78796:7548e455:76ec4dfb;Fri Sep 7 16:42:07 2007]
2007/11/19 08:32:03 NASty : [Disk sda] UUID[raid5;7f66f7af:d9f78796:7548e455:76ec4dfb;Fri Sep 7 16:42:07 2007]
2007/11/19 08:32:03 NASty : Assemble RAID [md1] from [ /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2 ]
2007/11/19 08:30:59 NASty : The system NASty WAN network was unplugged.
2007/11/19 08:30:50 NASty : NASty reboot
2007/11/19 08:22:26 NASty : User admin logged in from 29.14.114.202
2007/11/19 02:01:05 NASty : User admin logged in from 24.16.162.222
2007/11/19 02:00:32 NASty : NASty boot
2007/11/19 02:00:31 NASty : Healthy: The system NASty is healthy now.
2007/11/19 02:00:28 NASty : mdadm: /dev/md1 has been started with 4 drives.
2007/11/19 02:00:28 NASty : mdadm: /dev/md1 has been started with 4 drives.
2007/11/19 02:00:28 NASty : mdadm: /dev/md1 has been started with 4 drives.


Now.. it shows that the share (folder is what they call it) was added to the quota matrix.. maybe having that enabled screws something up? None of this makes sense.


-bash-3.1# mount -v -t nfs nasty:/raid0/data/pg -o tcp,nfsvers=3,intr /data/pg
mount: nasty:/raid0/data/pg failed, reason given by server: Permission denied


Changing the export fs to a totally bogus path returns the exact same, equally worthless response:


-bash-3.1# mount -v -t nfs nasty:/x -o tcp,nfsvers=3,intr /data/pg
mount: nasty:/x failed, reason given by server: Permission denied


[omega]

As long as your shares don't show up in "showmount -e" you'll always get the error message "reason given by server: Permission denied".....

It really seems that Thecus did screw up the firmware....

And without SSH access to your device you're really stuck

Is it possible to install my SERGETTY module on your device and does your device have a serial port? Then you would be able to login using a serial connection and a terminal program like HyperTerm, ZOC, etc.....

Andreas

[alexdavidson]

Disable then re-enable NFS.

Yes, it's broken. We ran into this ourselves. Every time you alter the NFS config, you have to stop and start the NFS service manually to reset it.