dlandon

The Dashboard is not managed by UD. It is part of the base Unraid OS. Feel free to post a bug report to Unraid.

Maybe your IP address is wrong on the 'plex' mount.? The root share is using the server name.

You have what looks like a routing problem: Aug 16 04:13:28 TGTBServer kernel: CIFS: Attempting to mount \\10.147.19.9\plex Aug 16 04:13:28 TGTBServer kernel: CIFS: VFS: Error connecting to socket. Aborting operation. Aug 16 04:13:28 TGTBServer kernel: CIFS: VFS: cifs_mount failed w/return code = -111 Aug 16 04:13:28 TGTBServer unassigned.devices: SMB default protocol mount failed: 'mount error(111): could not connect to 10.147.19.9Unable to find suitable address. '. Return code = -111 is a connecion issue. The SMB listen IP addresses from testparm are: interfaces = 192.168.2.53/24 127.0.0.1 10.147.19.188/24 The range of usable IP addresses within this subnet is from 10.147.19.1 to 10.147.19.254. Your target IP address of 10.147.19.9 is within this range, so it should work. Check your network layout and your remote server. Unraid 6.12 requires some configuration for ZeroTier. The issue could also be with the remote server. If the orb ball is green, it means the remote server is responding to a ping, but does not guarantee that the remote share will mount. I'm assuming that the remote server is being accessed over the Internet because you are using ZeroTier. Be sure port 445 is able to pass through your routers on both ends.

What you want to do is to install the "User Scripts" plugin and set up a script to run at a set time. I use this script to mount a disk, do a backup, and unmount the disk when it's done. #!/bin/bash #description=Backup Music Folder. #backgroundOnly=true #arrayStarted=true #clearLog=true # LOGFILE="/tmp/unassigned.devices/logs/Music_Backup.log" # Mount the backup disk /usr/local/sbin/rc.unassigned mount name=MusicBk # Backup the Music folder to the backup disk rsync -av --delete --exclude .Recycle.Bin '/mnt/user/Music' '/mnt/disks/Music Backup/' 2>&1 >> $LOGFILE # Unmount the disk /usr/local/sbin/rc.unassigned umount name=MusicBk You can have the disk detach by loading the default script in UD and uncomment the line to detach it: 'REMOVE' ) # do your stuff here # Spin down disk - uncomment this if you want the disk to be spun down after the disk is unmounted /usr/local/sbin/rc.unassigned spindown $DEVICE # Detach the disk - uncomment this if you want the USB disk to be detached after it is unmounted /usr/local/sbin/rc.unassigned detach $DEVICE /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Unassigned Devices" -d "Device unmounted" -i "normal" ;;

The script that runs when the device is plugged in is the device script. Plug the device in and then click the Edit Device Settings icon (three gears). Then click the 'Default' script button and fill in your commands in the appropriate event section. Once you are happy with the script, switch on the 'Auto Mount' switch and then when you plug in the USB device the script will run. You can unmout the disk in the script when it has completed the operations.

Looks like the macvlan issue got you: Aug 13 09:42:12 Tower kernel: ------------[ cut here ]------------ Aug 13 09:42:12 Tower kernel: WARNING: CPU: 8 PID: 19104 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Aug 13 09:42:12 Tower kernel: Modules linked in: xt_mark udp_diag xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap veth macvlan xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xfs ccp nvidia_uvm(PO) md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag amdgpu gpu_sched drm_ttm_helper nct6775 nct6775_core hwmon_vid iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs af_packet 8021q garp mrp bridge stp llc bonding tls nvidia_drm(PO) nvidia_modeset(PO) i915 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel nvidia(PO) iosf_mbi drm_buddy kvm i2c_algo_bit Aug 13 09:42:12 Tower kernel: crct10dif_pclmul crc32_pclmul ttm crc32c_intel ghash_clmulni_intel sha512_ssse3 drm_display_helper aesni_intel btusb drm_kms_helper crypto_simd mei_hdcp mei_pxp intel_gtt btrtl cryptd btbcm btintel rapl wmi_bmof intel_cstate bluetooth mpt3sas i2c_i801 drm intel_uncore nvme mei_me agpgart input_leds i2c_smbus ecdh_generic ahci raid_class e1000e i2c_core mei scsi_transport_sas led_class ecc joydev nvme_core libahci syscopyarea sysfillrect vmd sysimgblt fb_sys_fops thermal fan video tpm_crb tpm_tis tpm_tis_core wmi tpm backlight intel_pmc_core acpi_tad acpi_pad button unix Aug 13 09:42:12 Tower kernel: CPU: 8 PID: 19104 Comm: kworker/u40:1 Tainted: P S O 6.1.38-Unraid #2 Aug 13 09:42:12 Tower kernel: Hardware name: ASUS System Product Name/PRIME Z690M-PLUS D4, BIOS 1203 03/04/2022 Aug 13 09:42:12 Tower kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan] Aug 13 09:42:12 Tower kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Aug 13 09:42:12 Tower kernel: Code: 44 24 10 e8 e2 e1 ff ff 8b 7c 24 04 89 ea 89 c6 89 04 24 e8 7e e6 ff ff 84 c0 75 a2 48 89 df e8 9b e2 ff ff 85 c0 89 c5 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 18 dd ff ff e8 93 e3 ff ff e9 72 01 Aug 13 09:42:12 Tower kernel: RSP: 0018:ffffc900003a8d98 EFLAGS: 00010202 Aug 13 09:42:12 Tower kernel: RAX: 0000000000000001 RBX: ffff88813c3f7d00 RCX: 3e2bda644a39e8b0 Aug 13 09:42:12 Tower kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88813c3f7d00 Aug 13 09:42:12 Tower kernel: RBP: 0000000000000001 R08: bc81bf30a6d60746 R09: b81ee9915673b8ee Aug 13 09:42:12 Tower kernel: R10: 02dbe46e6b3802c4 R11: ffffc900003a8d60 R12: ffffffff82a11d00 Aug 13 09:42:12 Tower kernel: R13: 0000000000037cac R14: ffff8882781d6200 R15: 0000000000000000 Aug 13 09:42:12 Tower kernel: FS: 0000000000000000(0000) GS:ffff88885f400000(0000) knlGS:0000000000000000 Aug 13 09:42:12 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 13 09:42:12 Tower kernel: CR2: 000035729acd8000 CR3: 000000000420a000 CR4: 0000000000750ee0 Aug 13 09:42:12 Tower kernel: PKRU: 55555554 Aug 13 09:42:12 Tower kernel: Call Trace: Aug 13 09:42:12 Tower kernel: <IRQ> Aug 13 09:42:12 Tower kernel: ? __warn+0xab/0x122 Aug 13 09:42:12 Tower kernel: ? report_bug+0x109/0x17e Aug 13 09:42:12 Tower kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Aug 13 09:42:12 Tower kernel: ? handle_bug+0x41/0x6f Aug 13 09:42:12 Tower kernel: ? exc_invalid_op+0x13/0x60 Aug 13 09:42:12 Tower kernel: ? asm_exc_invalid_op+0x16/0x20 Aug 13 09:42:12 Tower kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Aug 13 09:42:12 Tower kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack] Aug 13 09:42:12 Tower kernel: ? nf_nat_inet_fn+0x123/0x1a8 [nf_nat] Aug 13 09:42:12 Tower kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Aug 13 09:42:12 Tower kernel: nf_hook_slow+0x3a/0x96 Aug 13 09:42:12 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Aug 13 09:42:12 Tower kernel: NF_HOOK.constprop.0+0x79/0xd9 Aug 13 09:42:12 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Aug 13 09:42:12 Tower kernel: __netif_receive_skb_one_core+0x77/0x9c Aug 13 09:42:12 Tower kernel: process_backlog+0x8c/0x116 Aug 13 09:42:12 Tower kernel: __napi_poll.constprop.0+0x28/0x124 Aug 13 09:42:12 Tower kernel: net_rx_action+0x159/0x24f Aug 13 09:42:12 Tower kernel: __do_softirq+0x126/0x288 Aug 13 09:42:12 Tower kernel: do_softirq+0x7f/0xab Aug 13 09:42:12 Tower kernel: </IRQ> Aug 13 09:42:12 Tower kernel: <TASK> Aug 13 09:42:12 Tower kernel: __local_bh_enable_ip+0x4c/0x6b Aug 13 09:42:12 Tower kernel: netif_rx+0x52/0x5a Aug 13 09:42:12 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Aug 13 09:42:12 Tower kernel: ? _raw_spin_unlock+0x14/0x29 Aug 13 09:42:12 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Aug 13 09:42:12 Tower kernel: process_one_work+0x1a8/0x295 Aug 13 09:42:12 Tower kernel: worker_thread+0x18b/0x244 Aug 13 09:42:12 Tower kernel: ? rescuer_thread+0x281/0x281 Aug 13 09:42:12 Tower kernel: kthread+0xe4/0xef Aug 13 09:42:12 Tower kernel: ? kthread_complete_and_exit+0x1b/0x1b Aug 13 09:42:12 Tower kernel: ret_from_fork+0x1f/0x30 Aug 13 09:42:12 Tower kernel: </TASK> Aug 13 09:42:12 Tower kernel: ---[ end trace 0000000000000000 ]--- Some other issues: Turn off mover logging. You have a nvme drive issue? Aug 13 09:37:36 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 75100532 off 12288 csum 0x154af3bd expected csum 0x90be6d72 mirror 1 Aug 13 09:37:36 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 29, gen 0 Aug 13 09:37:36 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 75100532 off 16384 csum 0xeb756e35 expected csum 0x8188ffff mirror 1 Aug 13 09:37:36 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 30, gen 0 Aug 13 09:37:36 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 75100532 off 12288 csum 0x154af3bd expected csum 0x90be6d72 mirror 1 Aug 13 09:37:36 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 31, gen 0 Aug 13 09:37:36 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 75100532 off 12288 csum 0x154af3bd expected csum 0x90be6d72 mirror 1 Aug 13 09:37:36 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 32, gen 0 Aug 13 09:37:36 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 75100532 off 12288 csum 0x154af3bd expected csum 0x90be6d72 mirror 1 Aug 13 09:37:36 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 33, gen 0 Aug 13 09:41:24 Tower ool www[20856]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_scrub 'start' '/mnt/cache' '' Display error: Aug 13 03:46:05 Tower kernel: EDID block 0 (tag 0x00) checksum is invalid, remainder is 125 Check your monitor connection and possibly replace the cable.

Yes, please give it a go.

Update UD+ and see if you can successfully check the disk.

It looks like there is a missing package. Let me look into it and get back to you.

Fixed in the next release. The log message won't show if NFS is disabled.

Cancelling an operation should be handled cleanly by MC. Install the "Open Files" plugin and it will allow you to kill the processes using the file(s).

This is the problem. The sync command timed out. I ill have to add more time to the sync timeout. EDIT: I'll set it up so the sync will not time out in this situation, but the sync timing out didn't necessarily cause the problem of writing to the disk after it is unmounted. If the sync is allowed to complete, it might help, but Linux finished the unmount and supposedly flushed out the disk cache before ending the unmount.

Syncing the disk device itself is not necessary. Linux handles all buffer flushing when unmounting. The added 'sync -f ...' is to allow the syncing to occur before attempting an unmount because it can potentially take a long time and the unmount command would time out. When the 'umount' command completes, Linux has completed all it's writes to the disk. A device level sync will do nothing because the disk writes are already completed. What you are probably running into is the disk itself buffering data and taking a while to finish writing. My suggestion is to add a delay in your device script to give the appropriate amount of time to be sure the device has indeed finished writing all data. For example: 'REMOVE' ) # do your stuff here # Let the disk finish it's disk writes before reporting disk is unmounted # Wait for five minutes to be sure the disk has completed its write operations sleep 300 /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Unassigned Devices" -d "Device unmounted" -i "normal" ;; And wait for the notificaton before removing the disk.

It looks like a memory issue. Run a memory test.

I appreciate that as I don't have any disks near that large to test with. Right now the 'post-read' reads every sector on the disk to memory to verify it is zeroed. This is really overkill and seems to test memory more than the disk. I want to do the verificaton without reading all the sectors into memory.

I'll be testing a different approach to post reads and will have an updated preclear in a day or two. If you are willing, I'd like you to give it a try.

It failed because 'dd' seg faulted. Please post your diagnostics.

I wasn't using a mount point with a space.

The recycle bin was only getting the first part of the mount point (up to the space) so it could not find the recycle bin folder on the disk to add to the recycle bin of the GUI.

The issue is the space in your mount point. Working on a fix. It'll be fixed in the next release.

I thought you were on 6.12. Your diagnostics won't show what I need to see. Please PM me the output of 'testparm -s'.

Post diagnostics.

I was under the impression that you were talking about a remote share mount. Yes, it works on local mounted UD drives. The recycle bin is refreshed every five minutes. If you delete files, it may take up to five minutes to show in the recycle bin. They will show in the log immediately.

Several days ago there was an UD preclear release that had some files missing, That release caused some gui issues. It was posted for about five minutes. You may have caught that release. I'm not sure if that is causing this for you, but remove the UD preclear plugin and see if yur issues clear up.

The Recycle Bin only works on UD disk shares and root shares. It doesn't work through remote shares. It works on Remote Shares when deleted locally and not remotely.