dlandon

Network, cable, switch, or router issue?

Post diagnostics.

Understood. Post diagnostics so we can look into it further.

It can take a few minutes for the SMB shares to be current after changes. Give it some time, or if it doesn't go away, just click on the double arrows icon at the the upper right hand of the UD page to refresh UD.

Unrelated, but you have a disk with errors: Jul 3 18:47:01 Lucy root: Fix Common Problems Version 2023.04.26 Jul 3 18:47:02 Lucy root: Fix Common Problems: Error: disk3 (WDC_WD60EFRX-68MYMN1_WD-WX21D84R1EK9) has read errors It looks like the disk mounted r/w: Jul 2 15:25:30 Lucy unassigned.devices: Mounting partition 'sda1' at mountpoint '/mnt/disks/WD_My_Passport_0827'... Jul 2 15:25:30 Lucy unassigned.devices: Mount cmd: /sbin/mount -t 'btrfs' -o rw,noatime,nodiratime,space_cache=v2 '/dev/sda1' '/mnt/disks/WD_My_Passport_0827' Jul 2 15:25:30 Lucy kernel: BTRFS info (device sda1): using crc32c (crc32c-intel) checksum algorithm Jul 2 15:25:30 Lucy kernel: BTRFS info (device sda1): using free space tree Jul 2 15:25:33 Lucy unassigned.devices: Successfully mounted 'sda1' on '/mnt/disks/WD_My_Passport_0827'. Why do you think it's read only? You have errors on that disk: Jul 3 19:27:44 Lucy kernel: BTRFS error (device sda1: state EA): bdev /dev/sda1 errs: wr 515, rd 137, flush 0, corrupt 0, gen 0 Jul 3 19:27:44 Lucy kernel: I/O error, dev sda, sector 2248416 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 2 Jul 3 19:27:44 Lucy kernel: BTRFS error (device sda1: state EA): bdev /dev/sda1 errs: wr 515, rd 138, flush 0, corrupt 0, gen 0 Jul 3 19:27:51 Lucy kernel: I/O error, dev sda, sector 94112 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 2 Jul 3 19:27:51 Lucy kernel: BTRFS error (device sda1: state EA): bdev /dev/sda1 errs: wr 515, rd 139, flush 0, corrupt 0, gen 0 Jul 3 19:27:51 Lucy kernel: I/O error, dev sda, sector 2191264 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 2 @JorgeB can probably help with the disk issues.

The orb ball is only based on being able to ping the remote share server. The 'Mount' button and the size, used, and free indicators (from df) will show mount status.

Your issue is not a UD Preclear issue. Please post your issue with diagnostics here:

I need the log when Unraid shuts down and reboots. Unfortunately, it is lost when rebooting. You have the Tips and Tweaks plugin installed. There is a log archive feature that saves a copy of the syslog on the flash when Unraid is shutting down. Set the "Enable syslog Archiving?" to 'Yes' and then start a preclear and shut down Unraid. When you reboot, the syslog will be archived to '/flash/logs/'.

Unraid 6.12 introduced the concept of listening interfaces. Read the release notes here https://docs.unraid.net/unraid-os/release-notes/6.12.0/ and see if you need to add your interface so UD can mount remote shares. For example, if you use a Zerotail or Tailscale VPN.

Posting diagnostics can help with diagnosing your issue.

I just tried a reboot to see if there was an issue with pausing and resuming a preclear and it worked for me. In order to catch this so I can troubleshoot this, do this: Set up the syslog server to write the log to disk. Reboot while running a preclear. Post the syslog.

Which computer is the client and which is the server?

Here is what I see: Jun 23 04:40:02 Tower root: Fix Common Problems Version 2023.04.26 Jun 23 04:40:03 Tower root: Fix Common Problems: Warning: Unraid OS not up to date Jun 23 04:40:03 Tower root: Fix Common Problems: Warning: Docker Application thespaghettidetective_redis_1 has an update available for it Jun 23 04:40:03 Tower root: Fix Common Problems: Warning: Share Secure-storage is set for both included (disk4) and excluded (disk1,disk2,disk3) disks Jun 23 04:40:03 Tower root: Fix Common Problems: Warning: Share VMs is set for both included (disk3) and excluded (disk1,disk2) disks Jun 23 04:40:03 Tower root: Fix Common Problems: Warning: Deprecated plugin ca.backup2.plg Jun 23 04:40:05 Tower root: Fix Common Problems: Warning: Docker application Dolphin has moderator comments listed Jun 23 04:40:05 Tower root: Fix Common Problems: Warning: Docker application PlexMediaServer has moderator comments listed Jun 23 04:40:05 Tower root: Fix Common Problems: Warning: Docker application steamcache-DNS has moderator comments listed ** Ignored Jun 23 04:40:06 Tower root: Fix Common Problems: Warning: NerdPack.plg Not Compatible with Unraid version 6.11.5 Jun 23 04:40:07 Tower root: minecraft-James-revelation: Could not download icon https://vignette.wikia.nocookie.net/minecraft/images/7/7b/Grass_block.png Jun 23 04:40:07 Tower root: Minecraft-polytech-direwolf20-1.19: Could not download icon https://vignette.wikia.nocookie.net/minecraft/images/7/7b/Grass_block.png Jun 23 04:40:08 Tower root: urBackup-Server: Could not download icon http://192.168.1.90:55414/images/urbackup.png Jun 23 04:40:10 Tower root: minecraft-James-revelation: Could not download icon https://vignette.wikia.nocookie.net/minecraft/images/7/7b/Grass_block.png Jun 23 04:40:11 Tower root: Minecraft-polytech-direwolf20-1.19: Could not download icon https://vignette.wikia.nocookie.net/minecraft/images/7/7b/Grass_block.png Jun 23 04:40:11 Tower root: urBackup-Server: Could not download icon http://192.168.1.90:55414/images/urbackup.png Jun 23 04:40:11 Tower root: minecraft-James-revelation: Could not download icon https://vignette.wikia.nocookie.net/minecraft/images/7/7b/Grass_block.png Jun 23 04:40:11 Tower root: Minecraft-polytech-direwolf20-1.19: Could not download icon https://vignette.wikia.nocookie.net/minecraft/images/7/7b/Grass_block.png Jun 23 04:40:12 Tower root: urBackup-Server: Could not download icon http://192.168.1.90:55414/images/urbackup.png Jun 23 04:40:12 Tower root: Fix Common Problems: Warning: Write Cache is disabled on disk5 Jun 23 04:40:13 Tower root: Fix Common Problems: Other Warning: Unassigned Devices Plus not installed Jun 23 04:40:14 Tower root: Fix Common Problems: Warning: Docker Update Patch not installed Jun 23 04:47:31 Tower apcupsd[7934]: Communications with UPS lost. Here are my suggestions: Go through all the FCP issues and get them sorted out. Be sure to remove the NerdPack plugin as it is not compatible with 6.11. You have some disk mapping issues. Find out why your UPS keeps losing communications. Run Unraid without any Docker containers running and see if the log messages and filling of the log stops.

UD is used by many users like myself to back up files. I plug in a USB disk and a device script runs doing the work I want done for that device. The Historical devices are devices that were in UD but have been removed as you noted. When I plug in a USB disk, the disk mounts and runs the script as defined in the Historical devices. This makes the backup a plug and play operation. Without the Historical device settings, UD does not know what to do when a disk in plugged in.

You have a network issue.

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.