May 19, 20224 yr I am not sure if it is a bug of the new version 6.10 or it is only a problem I have, so I write here. I was using my Unraid NAS as a NFS server to share my Movies and TVShows library to an Oppo BluRay Display for a year, with previous version of Unraid without any problem. Yesterday after installing 6.10 the Oppo can not red the folders content (folders apears empty). The folder is sharing to the Oppo, so it detects it but the folder is empty. I do not change any configuration. I tried to disable the NFS Share under "Settings-NFS-EnableNFS" and enable it again (tunable is set to 330 - not changed). I tried to setup again the folder configuration under "shares- NFS Security Settings" with different configurations and allways the same. Sharing Folders through SMB works well, but I prefer to use NFS.
May 22, 20224 yr Author I did not try to downgrade. I have also updated to 6.10.1 and continues the same. I tryed to mount the shares with my Qnap NAS and they mounted without problems. The day before upgrading i was using the device with the NFS. The problems started as soon as the upgrade. Could new revisión of UnRaid changed the version of the NFS? Edited May 23, 20224 yr by dellorianes
May 23, 20224 yr Author If it helps, this is the conteny of the file /etc/exports: "/mnt/user/Movies" -fsid=101,async,no_subtree_check 192.168.29.24 "/mnt/user/TvShows" -fsid=102,async,no_subtree_check 192.168.29.24
May 24, 20224 yr Author I have checked the file /etc/nfsmount.conf in my unraid server and it is set up as "Protocol Version [2,3,4] -> Defaultvers=3" (that I think is the same as it was in 6.9.2). I can not understand. As written above, I have tryed: - Mounting Unraid share folders in the Oppo device (both Movies and TVShows and also other folder that I never mount before). Share folders are detected but they appears empty. - Mounting Unraid share folders in the QNap NAS. Share folders detected and all data detected (subfolders and files). - Mounting a QNAP share folder with a media folder inside in the Oppo device. Share folder detected and all data inside it detected (subfolders and files). So the problem is only between the Oppo and the Unraid and it appeared the day I made the upgrade to 6.10
May 25, 20224 yr Author I have also tryed to mount at the same time: - In the Oppo a Qnap folder (independent of Unraid) - In the Oppo a folder of an Unraid folder mounted in the Qnap and this folder mounted again on the Oppo (using the Qnap NAS as a bridge) The result is that the Oppo can see both folders but it can see the content of the Qnap folder but can not see the content of the Unraid folder mounted in the Qnap NAS. Again I think there is a problem between Unraid server setup and the Oppo client setup.
May 31, 20224 yr Author On 5/28/2022 at 6:32 PM, dlandon said: Post diagnostics zip file. Thank you very much for your answer. Please, find attached the diagnostic file: Regards nasdiego-diagnostics-20220531-0916.zip
May 31, 20224 yr I only see two shares being exported with NFS Private. I'm not an expert in NFS, but I see several issues: May 30 00:15:01 NASDiego kernel: FS-Cache: Netfs 'nfs' registered for caching May 30 00:20:02 NASDiego emhttpd: read SMART /dev/sdg May 30 00:23:22 NASDiego kernel: nfs: server 192.168.29.5 not responding, still trying ### [PREVIOUS LINE REPEATED 9 TIMES] ### May 30 00:24:24 NASDiego kernel: nfs: server 192.168.29.5 OK ### [PREVIOUS LINE REPEATED 9 TIMES] ### May 30 00:35:33 NASDiego kernel: traps: lsof[14990] general protection fault ip:14d946a626ae sp:67a7419c4c3996a4 error:0 in libc-2.33.so[14d946a49000+15e000] May 30 00:36:10 NASDiego emhttpd: read SMART /dev/sdd May 30 00:37:44 NASDiego sSMTP[17929]: Unable to connect to smtp.live.com:465 May 30 00:37:44 NASDiego sSMTP[17929]: Cannot open smtp.live.com:465 May 30 00:38:59 NASDiego kernel: traps: lsof[24250] general protection fault ip:14a6f68a06ae sp:c2a16d50cd4ab2c0 error:0 in libc-2.33.so[14a6f6887000+15e000] May 30 00:39:43 NASDiego kernel: traps: lsof[25761] general protection fault ip:150ef49756ae sp:f6c5a1c26c831fcf error:0 in libc-2.33.so[150ef495c000+15e000] May 30 00:40:21 NASDiego kernel: traps: lsof[27336] general protection fault ip:148790ce86ae sp:b5b3372700e49f2d error:0 in libc-2.33.so[148790ccf000+15e000] May 30 00:40:53 NASDiego kernel: traps: lsof[28685] general protection fault ip:15012a9686ae sp:69d11097c51e1bdf error:0 in libc-2.33.so[15012a94f000+15e000] May 30 00:44:50 NASDiego kernel: traps: lsof[29821] general protection fault ip:14dc918976ae sp:c248730f6b03783b error:0 in libc-2.33.so[14dc9187e000+15e000] May 30 00:45:41 NASDiego kernel: traps: lsof[6048] general protection fault ip:15089db146ae sp:8aabd1c1908fa41f error:0 in libc-2.33.so[15089dafb000+15e000] May 30 00:46:02 NASDiego kernel: traps: lsof[7393] general protection fault ip:1511b4ee76ae sp:3a5a68310d99e4af error:0 in libc-2.33.so[1511b4ece000+15e000] May 30 00:46:59 NASDiego kernel: traps: lsof[8104] general protection fault ip:14d97248a6ae sp:b32be53191ae1a77 error:0 in libc-2.33.so[14d972471000+15e000] May 30 00:51:41 NASDiego kernel: traps: lsof[10465] general protection fault ip:14b6710596ae sp:b16b38e7d4ea06dd error:0 in libc-2.33.so[14b671040000+15e000] Your server at 192.168.29.5 is not responding right away and then goes on-line. Shortly after that you are getting GPFs in libc-2.33.so. Not sure if they are NFS related, but should be looked into. I would remove these lines from your go file as they are no longer needed and the i915 driver has been an issue in the past. modprobe i915 chmod -R 777 /dev/dri Unraid handles this in the latest version.
June 1, 20224 yr Author 18 hours ago, dlandon said: I only see two shares being exported with NFS Private. I'm not an expert in NFS, but I see several issues: May 30 00:15:01 NASDiego kernel: FS-Cache: Netfs 'nfs' registered for caching May 30 00:20:02 NASDiego emhttpd: read SMART /dev/sdg May 30 00:23:22 NASDiego kernel: nfs: server 192.168.29.5 not responding, still trying ### [PREVIOUS LINE REPEATED 9 TIMES] ### May 30 00:24:24 NASDiego kernel: nfs: server 192.168.29.5 OK ### [PREVIOUS LINE REPEATED 9 TIMES] ### May 30 00:35:33 NASDiego kernel: traps: lsof[14990] general protection fault ip:14d946a626ae sp:67a7419c4c3996a4 error:0 in libc-2.33.so[14d946a49000+15e000] May 30 00:36:10 NASDiego emhttpd: read SMART /dev/sdd May 30 00:37:44 NASDiego sSMTP[17929]: Unable to connect to smtp.live.com:465 May 30 00:37:44 NASDiego sSMTP[17929]: Cannot open smtp.live.com:465 May 30 00:38:59 NASDiego kernel: traps: lsof[24250] general protection fault ip:14a6f68a06ae sp:c2a16d50cd4ab2c0 error:0 in libc-2.33.so[14a6f6887000+15e000] May 30 00:39:43 NASDiego kernel: traps: lsof[25761] general protection fault ip:150ef49756ae sp:f6c5a1c26c831fcf error:0 in libc-2.33.so[150ef495c000+15e000] May 30 00:40:21 NASDiego kernel: traps: lsof[27336] general protection fault ip:148790ce86ae sp:b5b3372700e49f2d error:0 in libc-2.33.so[148790ccf000+15e000] May 30 00:40:53 NASDiego kernel: traps: lsof[28685] general protection fault ip:15012a9686ae sp:69d11097c51e1bdf error:0 in libc-2.33.so[15012a94f000+15e000] May 30 00:44:50 NASDiego kernel: traps: lsof[29821] general protection fault ip:14dc918976ae sp:c248730f6b03783b error:0 in libc-2.33.so[14dc9187e000+15e000] May 30 00:45:41 NASDiego kernel: traps: lsof[6048] general protection fault ip:15089db146ae sp:8aabd1c1908fa41f error:0 in libc-2.33.so[15089dafb000+15e000] May 30 00:46:02 NASDiego kernel: traps: lsof[7393] general protection fault ip:1511b4ee76ae sp:3a5a68310d99e4af error:0 in libc-2.33.so[1511b4ece000+15e000] May 30 00:46:59 NASDiego kernel: traps: lsof[8104] general protection fault ip:14d97248a6ae sp:b32be53191ae1a77 error:0 in libc-2.33.so[14d972471000+15e000] May 30 00:51:41 NASDiego kernel: traps: lsof[10465] general protection fault ip:14b6710596ae sp:b16b38e7d4ea06dd error:0 in libc-2.33.so[14b671040000+15e000] Your server at 192.168.29.5 is not responding right away and then goes on-line. Shortly after that you are getting GPFs in libc-2.33.so. Not sure if they are NFS related, but should be looked into. I would remove these lines from your go file as they are no longer needed and the i915 driver has been an issue in the past. modprobe i915 chmod -R 777 /dev/dri Unraid handles this in the latest version. The problem with the server 192.168.29.5 (QNAP NAS) is different that what I am asking. Every Monday and Thursday at 00:15 I mount through NFS my QNAP NAS on my Unraid NAS in order to proceed with my backup system. Then the QNAP tunrs off. I have to check this problem, but it is not related to this topic. If I turn ON the QNAP and the rus the script (mounting + backup) I runs. My problem is only with the Oppo device. I seems that the NFS version on Unraid and Oppo are not compatible (it works great with 6.9.2). This afternooon I will try to access the Oppo device and just after that to show you the diagnostic.zip file, but I think the problem does not appear there. I will also try to make a video. About modprobe i915 chmod -R 777 /dev/dri, I put it ther for emby, according some tutorial. Ok I am going to test without it.
June 4, 20224 yr I have the same problem，If I stay at 6.9.2, NFS is working. If I upgrade or reinstall 6.10.X. NFS is empty.
June 5, 20224 yr Unraid 6.9 uses NFSv3. Unraid 6.10 uses NFSv4. I suspect your remote server is not compatible with NFSv4. Check the remote server and see if there is anything in the log regrading NFS.
June 5, 20224 yr 2 hours ago, dlandon said: Unraid 6.9 uses NFSv3. Unraid 6.10 uses NFSv4. I suspect your remote server is not compatible with NFSv4. Check the remote server and see if there is anything in the log regrading NFS. Thank you for your reply.My device is a Bluray player made by OPPO, which has been discontinued， there is no NFS version selection in the settings and no new firmware can be upgraded.😭 Is there a way to downgrade to V3? thanks lot
June 5, 20224 yr 1 hour ago, 银马神神 said: Thank you for your reply.My device is a Bluray player made by OPPO, which has been discontinued， there is no NFS version selection in the settings and no new firmware can be upgraded.😭 Is there a way to downgrade to V3? thanks lot Downgrade to 6.9.
June 6, 20224 yr 17 hours ago, dlandon said: Downgrade to 6.9. 6.9 unable to hardware transcoding for 12th intel GPU😢
June 6, 20224 yr 2 hours ago, 银马神神 said: 6.9 unable to hardware transcoding for 12th intel GPU😢 Ok. I asked you if the log of the BluRay device had anything about NFS. Can you access the log and what does it show? Also, how are you mounting the Unraid share on the BluRay player?
June 20, 20224 yr Author In my case there is no option to take a log. There is no access to the device other than GUI. The mounting process is the same with the resto of devices. From Unraid, setting the NFS configuration as export=yes, private and the device ip. From the Oppo device, there is no setup (no ssh nor smb access); I only access the network section and the ips of the NFS servers appear. Is the same protocol I was following until 6.10 and the same I do with the QNAP NAS, that works. Edited June 20, 20224 yr by dellorianes
July 4, 20224 yr Can confirm this issue with 6.10 -- Also upgraded to each latest hotfix version, still having NFS issues. One of my client servers basically loses access to half the data, empty folders in lots of places.
July 4, 20224 yr 8 minutes ago, Drewster727 said: Can confirm this issue with 6.10 -- Also upgraded to each latest hotfix version, still having NFS issues. One of my client servers basically loses access to half the data, empty folders in lots of places. Post your diagnostics zip file.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.