ReadyNAS 102 on 6.1.8 rsync password config fails #23712613

That is correct for Ubuntu versions.

I have tried many commands to mount, including using the exported nfsv4 path that I can't recall rigth now.
mount -t nfs 10.10.55.102:/data/MRD_FILES /mnt
mount -t nfs 10.10.55.102:/MRD_FILES /mnt
mount 10.10.55.102:/data/MRD_FILES /mnt
mount 10.10.55.102:/MRD_FILES /mnt
etc.... etc...

Try putting sudo before the command.

What error do you get when you try to mount it doing the following?:

# sudo mount -t nfs 10.10.55.102:/data/MRD_FILES /mnt

I was running it as root.
I get a timeout after several minutes.

I can run showmount - e <ip> and it takes about 10 minutes to eventually return the export list from the NAS. The fact that it returns, but takes so long should be an indication of some problem.

Some interesting debug output:

utilite@system-z:~$ sudo mount -t nfs 10.10.55.223:/data/MRD_FILES /mnt
[sudo] password for utilite:
^Cutilite@system-z:~$ ^C
utilite@system-z:~$ ^C
utilite@system-z:~$
utilite@system-z:~$
utilite@system-z:~$ sudo mount -vvv -t nfs 10.10.55.223:/data/MRD_FILES /mnt
mount: fstab path: "/etc/fstab"
mount: mtab path: "/etc/mtab"
mount: lock path: "/etc/mtab~"
mount: temp path: "/etc/mtab.tmp"
mount: UID: 0
mount: eUID: 0
mount: spec: "10.10.55.223:/data/MRD_FILES"
mount: node: "/mnt"
mount: types: "nfs"
mount: opts: "(null)"
mount: external mount: argv[0] = "/sbin/mount.nfs"
mount: external mount: argv[1] = "10.10.55.223:/data/MRD_FILES"
mount: external mount: argv[2] = "/mnt"
mount: external mount: argv[3] = "-v"
mount: external mount: argv[4] = "-o"
mount: external mount: argv[5] = "rw"
mount.nfs: timeout set for Thu Sep 4 09:39:39 2014
mount.nfs: trying text-based options 'vers=4,addr=10.10.55.223,clientaddr=10.10.55.203'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=10.10.55.223'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.10.55.223 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.10.55.223 prog 100005 vers 3 prot UDP port 54293
mount.nfs: mount(2): Connection timed out
mount.nfs: Connection timed out

utilite@system-z:~$ rpcinfo -p 10.10.55.223
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 37383 status
100024 1 tcp 53869 status
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100227 2 tcp 2049
100227 3 tcp 2049
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100227 2 udp 2049
100227 3 udp 2049
100021 1 udp 51482 nlockmgr
100021 3 udp 51482 nlockmgr
100021 4 udp 51482 nlockmgr
100021 1 tcp 54985 nlockmgr
100021 3 tcp 54985 nlockmgr
100021 4 tcp 54985 nlockmgr
100005 1 udp 46802 mountd
100005 1 tcp 34530 mountd
100005 2 udp 47096 mountd
100005 2 tcp 45352 mountd
100005 3 udp 54293 mountd
100005 3 tcp 35696 mountd

Sounds like a network issue.

Do you use Jumbo Frames? If so, can you try turning those off?

Can you see if a direct-connection with the NAS works any better (just to try to isolate the cause of the problem)? Note that the NIC is auto-sensing so you can use an ordinary ethernet cable for this (e.g. the one that shipped with your NAS).

I will give that a shot as soon as the rsyncs finish in about 24 hours.

SOLVED!

Rsync:
After a factory default and reinstall with the latest RN102 firmware available in the forums, I created all new shares in the exact same way as the first time and now was able to enable rsync passwords for all shares.

NFS:
It turns out that there was a firware bug with the Netgear Prosafe switch that this NAS is connected to. Netgear JGS524PE
A firmware upgrade resolved the NFS issues.

I appreciate all of the help from the forum, which is what led me in the direction of a possible network problem.

Well... the fun never ends!

I can't enable "Any Host" access to the other shares after having added it successfully to the first share.
I get an "Unknown user name" error message?
I also can not ssh in with ssh enabled. I get an imediate disconnection as soon as the password is entered and I hit return.

Any ideas?

With SSH are you remembering to SSH in as the 'root' user not 'admin'?

On OS6 the root user's password will match the password for the admin user.