dlandon

Post diagnostics.

Update to the latest release. The AD Extras page was not showing because of some debug I left in the code. Once the plugin is first installed, go to the AD Extras page and click the 'Default' button to apply the necessary Samba settings. After that the settings will be applied on each reboot.

Are you installing tmux with another plugin or package?

Did you have any issues with private permissions?

When that is complete, I will have a plan on what we want to do next. In order to develop that plan, I will need some information. Please answer these questions: When you say shares disappear, what shares are you referring to? Unraid NFS shares, UD NFS Shares, or Unraid user shares? Look at the 'Shares' tab of 'Main' and let me know if user shares show. If none show, that's an issue with shfs. If shares show it will be an NFS issue. When the shares drop, can you access the user shares with a Windows computer? I see you are mounting some Drobo shares with UD. Are these the troublesome shares, or the Unraid shares mounted by another server using NFS? What packages are you loading with NerdTools and Un-get? What comprises your NFS traffic? Media sharing, downloaders, backup? Can you disable all your NIC cards with the exception of the Intel NIC? There is a Linux bug report here that may be related to the issue you are having,

No, only /mnt/user or /mnt/user0.

Let me know how it goes now.

Update and give it a try. I know setting permissons on shares like appdata is a problem. I guess there was a mental lapse for a moment thinking I had a better idea.

Understood. I thought I had a good idea about setting permissions, and it is a fail. I am removing it so nothing will be changed in the next release. Posting fix now.

Ok. I know what that is and will update the plugin. For the moment do a Tools->New Permissions and be sure to exclude appdata.

For the Spaceinvaderone solution?

Please upgrade the AD Extras plugin and see if it doesn't solve the issues you are experiencing.

The plugin has been extensively rewritten and hopefully the issues are addressed so AD will work properly: Access permissions. Backup and restore of database so AD permission settings will be persistent after a reboot. Minimum Unraid version is now 6.11 so it is using the later Samba releases. Please provide feedback so we can incorporate the fixes directly into Unraid.

Do the following: While on the preclear page type ctrl-shift-j and see if there are any Java Script errors. Go to Tools->PHP Settings and see if there are any PHP warnings/errors. Post a screen shot of the UD page.

Is there any possibility you can boot the server in safe mode and run the rebuild to see if there is something going on with your hardware or something else? You have too many things going on for us to find what issue is causing your problems. You should get the emulated disk rebuilt anyway.

Your best bet is to keep this friom happening. Your idea of incremental file transfers would also work. Another approach is to check that the WIndows computer is online (ping) before starting an rsync, and keep it on line while files are being transferred.

Do you lose just the NFS share access or are all your shares gone. i.e. Do you see shares in the UI on the 'Shares' tab, or is it empty?

Try it this way: timeout 10 rsync -av --human-readable --itemize-changes SMB_SOURCE DEST The timeouot in the rsync command will not timeout rsync on an SMB share that goes offline.

I just found this in your latest syslog. Dec 26 12:51:50 TNAS kernel: r8169 0000:08:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko] Dec 26 12:51:50 TNAS kernel: r8169 0000:09:00.0 eth1: jumbo features [frames: 9194 bytes, tx checksumming: ko] There are several issues here. First the Realtek NICs are notorious for having issues with Linux because the drivers are not well maintained, and second Jumbo Frames are not recommended because it requires a lot of network configuration to get it right and honestly it is not worth the issues caused by misconfiguring Jumnbo Frames. What is confusing is that eth0 is showing in ifconfig with an mtu=1500: eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether 38:d5:47:78:ac:53 txqueuelen 1000 (Ethernet) RX packets 9658345 bytes 13781359482 (12.8 GiB) RX errors 0 dropped 347 overruns 0 frame 0 TX packets 1068484 bytes 413838386 (394.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xfe400000-fe41ffff Please check your configuration and verify that Jumbo Frames are not being used. This can cause a lot of problems with NFS and SMB shares.

Do the following: Upgrade to 7.0.0-rc2. This is the best version to use with NFS issues addressed. Set the shareNOFILE="655360". A much larger number. Do not use the sript mentioned above. Be sure to stop/start or reboot the server to get the setting to take effect.

It looks like one or more of your disks have a problem: Dec 25 18:15:02 Saturn kernel: sd 1:0:1:0: Power-on or device reset occurred Dec 25 18:15:05 Saturn emhttpd: device /dev/sdw problem getting id Dec 25 18:16:14 Saturn kernel: sd 10:0:7:0: device_block, handle(0x0010) Dec 25 18:16:16 Saturn kernel: sd 10:0:7:0: device_unblock and setting to running, handle(0x0010) Dec 25 18:16:16 Saturn kernel: sd 10:0:7:0: [sdw] Synchronizing SCSI cache Dec 25 18:16:16 Saturn kernel: sd 10:0:7:0: [sdw] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Dec 25 18:16:16 Saturn kernel: mpt3sas_cm1: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221103000000) Dec 25 18:16:16 Saturn kernel: mpt3sas_cm1: removing handle(0x0010), sas_addr(0x4433221103000000) Dec 25 18:16:16 Saturn kernel: mpt3sas_cm1: enclosure logical id(0x56c92bf0004cc904), slot(1) Dec 25 18:16:16 Saturn kernel: mpt3sas_cm1: enclosure level(0x0000), connector name( )

Finish your array rebuild and then come back here for more debugging.

Unraid 6.12.9 and beyond all have NFS issues. We believe we have addressed the last of the NFS issues with 7.0.0-rc2. All Unraid versions from 6.12.9 to 6.12.14 will have one issue or another with NFS. Either stay on 6.12.8, or upgrade to 7.0.0-rc2

No.

Share it in Windows and then mount it as a remote mount in UD. You will then have access to the disk in Unraid.