dlandon

It is not a feasability issue. UD mounts devices whenever auto mount is set and if the server is not available, UD will not attempt another try to mount. I don't think UD mounting remote shares when the server is online is a good idea. What if the user doesn't want auto mount shares to be re-mounted like this? You should develop a plan to handle this case. Another suggestion would be to unmount remote shares at a certain time (like just before the server goes to sleep) and mount them at a different time when the server would be back online. You can do this manually or programmatically using user scripts.

UD is the only requirement.

Be sure the clients are using NFSv4. NFSv3 has issues when a share is using the cache and files are moved by the mover from the cache to the share disk(s).

Did you update to 6.12.x stable? If you did, read the release notes on what needs to be done to support Zerotier.

I'm seeing this in the log that lead to the problem: May 30 21:04:31 REDACTED shfs: share cache full ### [PREVIOUS LINE REPEATED 3 TIMES] ### ... May 31 09:44:38 REDACTED kernel: shfs[10308]: segfault at 10 ip 000014648b6515c2 sp 000014648af45c20 error 4 in libfuse3.so.3.12.0[14648b64d000+19000] May 31 09:44:38 REDACTED kernel: Code: f4 c8 ff ff 8b b3 08 01 00 00 85 f6 0f 85 46 01 00 00 4c 89 ee 48 89 df 45 31 ff e8 18 dc ff ff 4c 89 e7 45 31 e4 48 8b 40 20 <4c> 8b 68 10 e8 15 c2 ff ff 48 8d 4c 24 18 45 31 c0 31 d2 4c 89 ee ... May 31 09:44:38 REDACTED kernel: ------------[ cut here ]------------ May 31 09:44:38 REDACTED kernel: nfsd: non-standard errno: -103 May 31 09:44:38 REDACTED kernel: WARNING: CPU: 15 PID: 9463 at fs/nfsd/nfsproc.c:889 nfserrno+0x45/0x51 [nfsd] May 31 09:44:38 REDACTED kernel: Modules linked in: wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha rpcsec_gss_krb5 cmac cifs asn1_decoder cifs_arc4 cifs_md4 dns_resolver xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod tcp_diag inet_diag it87 hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls amdgpu radeon gpu_sched drm_ttm_helper ttm btusb edac_mce_amd gigabyte_wmi wmi_bmof mxm_wmi edac_core kvm_amd btrtl kvm btbcm crct10dif_pclmul drm_display_helper crc32_pclmul crc32c_intel btintel ghash_clmulni_intel aesni_intel drm_kms_helper crypto_simd cryptd drm bluetooth May 31 09:44:38 REDACTED kernel: igb rapl nvme agpgart i2c_piix4 i2c_algo_bit k10temp joydev ahci ecdh_generic nvme_core i2c_core ecc syscopyarea libahci ccp sysfillrect sysimgblt fb_sys_fops tpm_crb thermal tpm_tis tpm_tis_core video tpm backlight wmi button acpi_cpufreq unix May 31 09:44:38 REDACTED kernel: CPU: 15 PID: 9463 Comm: nfsd Not tainted 5.19.17-Unraid #2 May 31 09:44:38 REDACTED kernel: Hardware name: Gigabyte Technology Co., Ltd. REDACTED_MODEL/REDACTED_MODEL, BIOS F37b 03/23/2023 May 31 09:44:38 REDACTED kernel: RIP: 0010:nfserrno+0x45/0x51 [nfsd] May 31 09:44:38 REDACTED kernel: Code: c3 cc cc cc cc 48 ff c0 48 83 f8 26 75 e0 80 3d bb 47 05 00 00 75 15 48 c7 c7 17 64 f0 a0 c6 05 ab 47 05 00 01 e8 42 47 94 e0 <0f> 0b b8 00 00 00 05 c3 cc cc cc cc 48 83 ec 18 31 c9 ba ff 07 00 May 31 09:44:38 REDACTED kernel: RSP: 0018:ffffc90000b47b58 EFLAGS: 00010282 May 31 09:44:38 REDACTED kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027 May 31 09:44:38 REDACTED kernel: RDX: 0000000000000001 RSI: ffffffff820d7be1 RDI: 00000000ffffffff May 31 09:44:38 REDACTED kernel: RBP: ffffc90000b47db0 R08: 0000000000000000 R09: ffffffff828653f0 May 31 09:44:38 REDACTED kernel: R10: 00003fffffffffff R11: ffff88a05e2c4bae R12: 000000000000000c May 31 09:44:38 REDACTED kernel: R13: 000000000010011a R14: ffff8881623011a0 R15: ffffffff82909480 May 31 09:44:38 REDACTED kernel: FS: 0000000000000000(0000) GS:ffff889fde3c0000(0000) knlGS:0000000000000000 May 31 09:44:38 REDACTED kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 31 09:44:38 REDACTED kernel: CR2: 00007faf350d6590 CR3: 0000000101500000 CR4: 0000000000750ee0 May 31 09:44:38 REDACTED kernel: PKRU: 55555554 May 31 09:44:38 REDACTED kernel: Call Trace: May 31 09:44:38 REDACTED kernel: <TASK> May 31 09:44:38 REDACTED kernel: nfsd4_encode_fattr+0x1372/0x13d9 [nfsd] May 31 09:44:38 REDACTED kernel: ? getboottime64+0x20/0x2e May 31 09:44:38 REDACTED kernel: ? kvmalloc_node+0x44/0xbc May 31 09:44:38 REDACTED kernel: ? __kmalloc_node+0x1b4/0x1df May 31 09:44:38 REDACTED kernel: ? kvmalloc_node+0x44/0xbc May 31 09:44:38 REDACTED kernel: ? override_creds+0x21/0x34 May 31 09:44:38 REDACTED kernel: ? nfsd_setuser+0x185/0x1a5 [nfsd] May 31 09:44:38 REDACTED kernel: ? nfsd_setuser_and_check_port+0x76/0xb4 [nfsd] ### [PREVIOUS LINE REPEATED 1 TIMES] ### May 31 09:44:38 REDACTED kernel: nfsd4_encode_getattr+0x28/0x2e [nfsd] May 31 09:44:38 REDACTED kernel: nfsd4_encode_operation+0xb0/0x201 [nfsd] May 31 09:44:38 REDACTED kernel: nfsd4_proc_compound+0x2a7/0x56c [nfsd] May 31 09:44:38 REDACTED kernel: nfsd_dispatch+0x1a9/0x262 [nfsd] May 31 09:44:38 REDACTED kernel: svc_process+0x3f1/0x5d6 [sunrpc] May 31 09:44:38 REDACTED kernel: ? nfsd_svc+0x2b6/0x2b6 [nfsd] May 31 09:44:38 REDACTED kernel: ? nfsd_shutdown_threads+0x5b/0x5b [nfsd] May 31 09:44:38 REDACTED kernel: nfsd+0xd5/0x155 [nfsd] May 31 09:44:38 REDACTED kernel: kthread+0xe7/0xef May 31 09:44:38 REDACTED kernel: ? kthread_complete_and_exit+0x1b/0x1b May 31 09:44:38 REDACTED kernel: ret_from_fork+0x22/0x30 May 31 09:44:38 REDACTED kernel: </TASK> May 31 09:44:38 REDACTED kernel: ---[ end trace 0000000000000000 ]--- ... May 31 09:44:40 REDACTED smbd[14715]: [2023/05/31 09:44:40.111782, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) May 31 09:44:40 REDACTED smbd[14715]: synthetic_pathref: opening [.] failed May 31 09:44:40 REDACTED smbd[14714]: [2023/05/31 09:44:40.260325, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) May 31 09:44:40 REDACTED smbd[14714]: synthetic_pathref: opening [.] failed ... May 31 09:44:40 REDACTED smbd[14714]: [2023/05/31 09:44:40.355105, 0] ../../source3/smbd/smb2_service.c:168(chdir_current_service) May 31 09:44:40 REDACTED smbd[14714]: chdir_current_service: vfs_ChDir(/mntREDACTED) failed: Transport endpoint is not connected. Current token: uid=1001, gid=100, 4 groups: 100 3003 3004 3005 May 31 09:44:40 REDACTED smbd[14714]: [2023/05/31 09:44:40.355148, 0] ../../source3/smbd/smb1_process.c:1159(switch_message) May 31 09:44:40 REDACTED smbd[14714]: Error: Could not change to user. Removing deferred open, mid=30024. May 31 09:44:40 REDACTED smbd[14714]: [2023/05/31 09:44:40.355859, 0] ../../source3/smbd/smb2_service.c:168(chdir_current_service) May 31 09:44:40 REDACTED smbd[14714]: chdir_current_service: vfs_ChDir(/mntREDACTED) failed: Transport endpoint is not connected. Current token: uid=1001, gid=100, 4 groups: 100 3003 3004 3005 I can see that after all this, NFS and SMB both are going south. Here are some suggestions: Don't use a cache on your shares for the time being. Your disks are all very full. I'd suggest you verify the 'Allocation Method' and the min free space makes sense for what you are doing. Can you remove some stuff from your array, or add more storage? Your disks are all pretty full. Many are over 90%. I am not an expert on NFS, but try these rules 'IP(rw,sec=sys,insecure,anongid=100,anonuid=99,no_root_squash)'. These are what I recommend for UD devices.

Copy the to/from an Unraid disk.

Each device needs to give a unique serial number. The one you are showing doesn't seem to have a serial number. UD thinks they are the same device.

Post diagnostics so we can help you.

Does the name work? Try this in a terminal and see if it returns the IP address: arp -a NASCEB6D5 Also this one: arp -an NASCEB6D5.LOCAL Bonding is for multiple NICs. If only one of your NICs is working, you can turn off bonding.

Changes have been made in 6.12. Refer to the release notes.

Yes, if you want to make adjustments to that NIC also.

Unount the remote share and the defaut button will show. I've made some changes here. The idea is you create a script when the device is not mounted.

I think you mean the default device script. Click on the 'Default' button when in the device settings and it will fill in the default script.

No. You can pause and restart where it left off, but you can't change the test parameters.

UD does not make any attempts to mount remote shares after the first try to auto mount. About the only thing you can do is set up a script to run on User Scripts to auto mount remote shares. You can run the script on a timed basis. The command to auto mount remote shares is: /usr/local/sbin/rc.unassigned mount autoshares What you might do is set up a User Script to run every 30 minutes and run the remote shares mount command. If the shares are already mounted, the script will just log that the devices are already mounted.

Read the release notes dealing with Zerotier here: https://docs.unraid.net/unraid-os/release-notes/6.12.0/

The Dashboard is not controlled by UD. You need to report that in the 6.12 release forum. The Dashboard Unassigned Devices is built into Unraid.

I don't think your remote server is reachable the way you have things setup: Jun 22 11:46:33 NASty unassigned.devices: SMB default protocol mount failed: 'mount error(111): could not connect to 100.72.40.79Unable to find suitable address. '. The 100.72.40.79 address is not reachable. Check the 6.12 release notes on setting up networking for tailscale.

Post diagnostics.

I cannot translate your pictures.

Your remote shares mounted: Jun 21 21:37:48 BX unassigned.devices: Successfully mounted '//192.168.50.50/电影盘' on '/mnt/remotes/192.168.50.50_电影盘'. Jun 21 21:37:48 BX unassigned.devices: Warning: Unassigned Devices are not set to be shared with SMB. Jun 21 21:37:48 BX unassigned.devices: Mounting Remote Share '//192.168.50.50/Download'... Jun 21 21:37:48 BX unassigned.devices: Mount SMB share '//192.168.50.50/Download' using SMB default protocol. Jun 21 21:37:48 BX unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_Download' '//192.168.50.50/Download' '/mnt/remotes/192.168.50.50_Download' Jun 21 21:37:48 BX kernel: CIFS: Attempting to mount \\192.168.50.50\Download Jun 21 21:37:48 BX unassigned.devices: Successfully mounted '//192.168.50.50/Download' on '/mnt/remotes/192.168.50.50_Download'. Jun 21 21:37:48 BX unassigned.devices: Warning: Unassigned Devices are not set to be shared with SMB. Jun 21 21:37:48 BX unassigned.devices: Remote Share 'DSM:' is not set to auto mount. but they cannot be seen on the LAN because you don't have SMB sharing set.

That shouldn't be a problem. File Activity is not the only process to use Inotify Watches.

You can update UD without it affecting the preclear. All UD does is show the preclear status.

Read first post on installing ownCloud and follow the steps.

Post diagnostics.