Hi guys,

I upgraded from 6.9.2 to 6.11.2, and lost access to my NFS shares.

Somewhere along the way something got changed, and my current config no longer works.

I have the shares exported as:

Security: Private

Rule: *(ro,insecure)

 

It worked in 6.9.2, and became inaccessible in 6.11.2. After reverting back to 6.9.2 everything worked again.

Could you tell me what changed and how to fix it in the newer versions?

 

Thank you!

Anyone?

AFAIK nothing changed with that, please post the diagnostics from v6.11

Well... I just found that 6.9.2 had NFS V3, while 6.11.2 has V4.

Could it be the reason why clients cannot access it now?

@dlandonmight be able to help.

Your devices can connect with either NFSv3 or NFSv4 with 6.11.  Post your diagnostics file.

Here it is (ignore the 2nd parity drive, it's a separate issue)

 

storage-diagnostics-20221112-1143.zip

Your array is not started:

Nov 12 11:39:38 Storage  emhttpd: shcmd (48): udevadm settle
Nov 12 11:39:38 Storage  emhttpd: Opening encrypted volumes...
Nov 12 11:39:38 Storage  emhttpd: Missing encryption key
Nov 12 11:39:38 Storage kernel: mdcmd (36): stop 
Nov 12 11:39:38 Storage kernel: md1: stopping
Nov 12 11:39:38 Storage kernel: md2: stopping
Nov 12 11:39:38 Storage kernel: md3: stopping
Nov 12 11:39:38 Storage kernel: md4: stopping

 

[mdState] => STOPPED

 

22 hours ago, dlandon said:

Your array is not started

 

 Apologies, that was the wrong file. I used it to show the 2nd parity issue.

Please find below as requested.

 

exportfs -v shows all is well, however remote client cannot access it anymore. As soon as I downgrade to 6.9.2, all works again.

storage-diagnostics-20221126-1559.zip

1 hour ago, Kir said:

 Apologies, that was the wrong file. I used it to show the 2nd parity issue.

Please find below as requested.

 

exportfs -v shows all is well, however remote client cannot access it anymore. As soon as I downgrade to 6.9.2, all works again.

storage-diagnostics-20221126-1559.zip 103.97 kB · 0 downloads

I'm not seeing any connecton attempts in your log.  I would expect to see some.  Is your rule set correctly with the correct IP address for access?

 

What is the remote client?  Have you tried with a different remote client?

The rule is set as described above:

Security: Private

Rule: *(ro,insecure)

 

Remote client is PCH A500. I suspect it doesn't like NFS V4...

I think I found the reason, and it has nothing to do with NFS V3 vs V4. This is what the NFS on unRaid 6.11 looks like:

# rpcinfo -p | grep nfs

    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs

 

There is no NFS over UDP anymore. And PCH A500 connects via UDP by default.

Is there any way to enable it?

Here is the solution from my friend @halfelite <-- BIG thanks!

File /etc/default/nfs needs to be modified to add the following line:

RPC_NFSD_OPTS="-u"

This would enable NFS UDP back.

 

To make it survive the reboot, add the following line to the go file:

echo "RPC_NFSD_OPTS=\"-u\"" >> /etc/default/nfs