dlandon

Nothing in the update affected permissions. You should restore your appdata from a backup.

I don't know enough about zfs to help here. @JorgeB can probably offer some assistance.

https://zfsonlinux.org/manpages/0.8.4/man8/zed.8.html

Post diagnostics.

This is more a Windows question than an Unraid question. You should try to get some help on a Windows forum.

This is probably due to the Linux disk caching. The first writes go to ram , then eventually to disk.

Are you using the latest version of UD? I think that might be fixed now.

I see that in your diagnostics. Why is zed even making note of it then?

That option probably corrected some permissions on your UD device.

Not really. It is an old idea from many Unraid versions ago and probably doesn't apply any longer.

You don't need to mount it manually. Look in the log and you'll see why it didn't mount. Probably a password issue. Set the disk password in the UD Settings for that particular disk.

Setting passthrough on a disk in UD does nothing but tell UD not to allow mounting/unmounting of the disk. Look at the response to your post in the UD forum. It looks like you have a Pool configuration issue.

Do you have a ZFS Pool configuration problem? Mar 4 20:34:17 KaraMediaGroup zed[8063]: zed_udev_monitor: skip /dev/sdm1 (in use by ntfs)

Not really. It is a spinner and with 1GB network you will get close to 100+MB/Sec speed of the drive.

NAS, 2 Windows Desktoo VMs, and added functionality in Docker Containers (Security Cameras (Zoneminder), Music Player (LMS), Personal Cloud (ownCloud), Home Device Management (Home Assistant)), all in one box. I've gotten rid of a lot of extra hardware over the years and I'm sure I cut power requirements by doing that.

Linux sees the disk as a raid member and UD won't be able to mount that disk with that format. Put it back in your Synology and do a remote share mount to the Synology and copy files that way.

UD used to share devices 'Public' when SMB Security was set to 'No' as a convenience. This was changed in June of 2022 for security reasons. Per release notes: 2022.06.19 Add: 'Public' setting to SMB Security settings to share devices public. The 'No' setting used to set 'Public' sharing. SMB Security now has to be specifically set to how you want to share all UD devices - Public, Private, or Private Hidden. The 'Share' switch on each device lets you control if that particular device is shared. For you newbees, always assume in Unraid that if you want something shared with SMB or NFS, you have to specifically set up how it will be shared so you always have control over your share security. Just setting a 'Share' switch does not specify how a device will be shared. For those of you old timers just now updating and seeing this issue, how about you update more often than 7 or 8 months, and read the latest release notes so I don't have to explain this issue over and over like I have in the last few days. Set your system to either automatically update plugins, or at least notify you of a plugin update and keep plugins updated!

Did you set the UD Settings->SMB Security to something other than 'No'? And give up to two minutes for the share to be active?

Go to UD Settings and set the SMB Security for the way you want to share the UD devices.

total 4 drwxr-x--- 5 root root 120 Mar 4 14:33 ./ drwxrwxrwt 17 root root 380 Mar 4 14:36 ../ -rwxrwx--- 1 root root 634 Mar 4 09:48 add-smb* drwxr-xr-x 2 root root 100 Mar 4 09:48 config/ drwxr-xr-x 2 root root 40 Mar 4 00:41 logs/ drwxr-xr-x 2 root root 40 Mar 4 00:41 scripts/ tower-diagnostics-20230304-1425.zip 171.77 kB · 0 downloads You have some page faults? Mar 4 13:00:48 Tower kernel: BUG: kernel NULL pointer dereference, address: 00000000000000b6 Mar 4 13:00:48 Tower kernel: #PF: supervisor read access in kernel mode Mar 4 13:00:48 Tower kernel: #PF: error_code(0x0000) - not-present page Mar 4 13:00:48 Tower kernel: PGD 0 P4D 0 Mar 4 13:00:48 Tower kernel: Oops: 0000 [#1] PREEMPT SMP PTI Mar 4 13:00:48 Tower kernel: CPU: 8 PID: 1532 Comm: qbittorrent-nox Not tainted 5.19.17-Unraid #2 Mar 4 13:00:48 Tower kernel: Hardware name: Supermicro Super Server/X10SDV-TLN4F, BIOS 2.0c 06/27/2019 Mar 4 13:00:48 Tower kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21 Mar 4 13:00:48 Tower kernel: Code: e8 9d fd 67 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 c1 35 69 00 48 81 c4 88 00 00 00 5b c3 cc cc cc cc <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb Mar 4 13:00:48 Tower kernel: RSP: 0000:ffffc90008d2bcc0 EFLAGS: 00010246 Mar 4 13:00:48 Tower kernel: RAX: 0000000000000082 RBX: 0000000000000082 RCX: 0000000000000082 Mar 4 13:00:48 Tower kernel: RDX: 0000000000000001 RSI: ffff8882764e4000 RDI: 0000000000000082 Mar 4 13:00:48 Tower kernel: RBP: 0000000000000000 R08: 0000000000000028 R09: ffffc90008d2bcd0 Mar 4 13:00:48 Tower kernel: R10: ffffc90008d2bcd0 R11: ffffc90008d2bd48 R12: 0000000000000000 Mar 4 13:00:48 Tower kernel: R13: ffff888046fcf2f8 R14: 0000000000237eeb R15: ffff888046fcf300 Mar 4 13:00:48 Tower kernel: FS: 00001542112ad6c0(0000) GS:ffff88885fc00000(0000) knlGS:0000000000000000 Mar 4 13:00:48 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 4 13:00:48 Tower kernel: CR2: 00000000000000b6 CR3: 00000003477a8003 CR4: 00000000003726e0 Mar 4 13:00:48 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 4 13:00:48 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Mar 4 13:00:48 Tower kernel: Call Trace: Mar 4 13:00:48 Tower kernel: <TASK> Mar 4 13:00:48 Tower kernel: __filemap_get_folio+0x98/0x1ff Mar 4 13:00:48 Tower kernel: filemap_fault+0x6e/0x524 Mar 4 13:00:48 Tower kernel: __do_fault+0x30/0x6e Mar 4 13:00:48 Tower kernel: __handle_mm_fault+0x9a5/0xc7d Mar 4 13:00:48 Tower kernel: handle_mm_fault+0x113/0x1d7 Mar 4 13:00:48 Tower kernel: do_user_addr_fault+0x36a/0x514 Mar 4 13:00:48 Tower kernel: exc_page_fault+0xfc/0x11e Mar 4 13:00:48 Tower kernel: asm_exc_page_fault+0x22/0x30 Mar 4 13:00:48 Tower kernel: RIP: 0033:0x154216b7504d Mar 4 13:00:48 Tower kernel: Code: 00 00 00 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 89 f8 48 83 fa 20 72 33 <c5> fe 6f 06 48 83 fa 40 0f 87 b5 00 00 00 c5 fe 6f 4c 16 e0 c5 fe Mar 4 13:00:48 Tower kernel: RSP: 002b:00001542112ab2c8 EFLAGS: 00010202 Mar 4 13:00:48 Tower kernel: RAX: 0000153640058f60 RBX: 00001542112ac308 RCX: 00001542112ab500 Mar 4 13:00:48 Tower kernel: RDX: 0000000000004000 RSI: 000015088f8ebfe1 RDI: 0000153640058f60 Mar 4 13:00:48 Tower kernel: RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 Mar 4 13:00:48 Tower kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000 Mar 4 13:00:48 Tower kernel: R13: 0000153640004b80 R14: 0000000000000001 R15: 0000557bf3268f70 Mar 4 13:00:48 Tower kernel: </TASK> Mar 4 13:00:48 Tower kernel: Modules linked in: xt_mark tcp_diag udp_diag inet_diag xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net vhost vhost_iotlb tap tun veth macvlan xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc ixgbe xfrm_algo mdio igb x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp ast drm_vram_helper drm_ttm_helper ttm kvm_intel drm_kms_helper kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel ipmi_ssif crypto_simd cryptd rapl intel_cstate drm intel_uncore mpt3sas backlight i2c_i801 agpgart i2c_smbus ahci intel_pch_thermal i2c_algo_bit input_leds joydev acpi_ipmi libahci led_class raid_class syscopyarea sysfillrect i2c_core sysimgblt scsi_transport_sas fb_sys_fops ipmi_si wmi acpi_pad button unix Mar 4 13:00:48 Tower kernel: [last unloaded: xfrm_algo] Mar 4 13:00:48 Tower kernel: CR2: 00000000000000b6 Mar 4 13:00:48 Tower kernel: ---[ end trace 0000000000000000 ]--- Mar 4 13:00:48 Tower kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21 Mar 4 13:00:48 Tower kernel: Code: e8 9d fd 67 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 c1 35 69 00 48 81 c4 88 00 00 00 5b c3 cc cc cc cc <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb Mar 4 13:00:48 Tower kernel: RSP: 0000:ffffc90008d2bcc0 EFLAGS: 00010246 Mar 4 13:00:48 Tower kernel: RAX: 0000000000000082 RBX: 0000000000000082 RCX: 0000000000000082 Mar 4 13:00:48 Tower kernel: RDX: 0000000000000001 RSI: ffff8882764e4000 RDI: 0000000000000082 Mar 4 13:00:48 Tower kernel: RBP: 0000000000000000 R08: 0000000000000028 R09: ffffc90008d2bcd0 Mar 4 13:00:48 Tower kernel: R10: ffffc90008d2bcd0 R11: ffffc90008d2bd48 R12: 0000000000000000 Mar 4 13:00:48 Tower kernel: R13: ffff888046fcf2f8 R14: 0000000000237eeb R15: ffff888046fcf300 Mar 4 13:00:48 Tower kernel: FS: 00001542112ad6c0(0000) GS:ffff88885fc00000(0000) knlGS:0000000000000000 Mar 4 13:00:48 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 4 13:00:48 Tower kernel: CR2: 00000000000000b6 CR3: 00000003477a8003 CR4: 00000000003726e0 Mar 4 13:00:48 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 4 13:00:48 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 I don't know enough about this to offer much help, but I sure would do a memory test. What I was looking for was lock files that were orphaned that might cause UD to hang, but there are none.

Ignore the warning for now. FCP needs an update. UD added that folder. Read UD release notes.

Nothing to fix. Ignore FCP for now until it gets an update. UD added that folder. Read UD release notes for more info.

That folder is for people to add their mounts for things like zfs devices and rclone , rather than putting the mounts in places like /mnt/disks or /mnt/remotes. FCP was updated to not flag that folder, but appears to need another update. For now ignore the FCP warning. Read the UD release notes for more info. Your system doesn’t have a problem.

Turn on the pass through switch when the disk is not mounted. It should stick.

Ignore it. The UD update added the folder and FCP is reporting it as a problem, but it is not.