dlandon

Yep, that's what I see. Remove the UD plugin and stop the array. See if Unraid will recognize the disk and show it in the Unassigned Devices tab.

This is an Unraid message. What shows in the UD web page? Post diagnostics file.

If anyone has Multichannel turned on, turn it off and try. There has been a report of a problem with Multichannel.

I appreciate the feedback. I was pretty sure we were looking at a network issue. I saw you posted a bug report. We'll be looking into this. I guess the Samba team made some changes that broke Multichannel. Unfortunately, this is the "whack-a-mole" with Samba - fix one thing and another issue pops up.

Post a new diagnostics.

It's a really nice script. I worked with him initially to get some bugs worked out. I'd like to see it work the way you want.

There are two lines in the script that can be removed. The PATH= is not needed. Unraid handles passing in the proper $PATH to the script. The sync command is not needed as it does nothing where it is. UD handles device sync when it is unmounted. You got old code from UD that has been changed. The issue is this section of code: 'ADD' ) if [ "$OWNER" = "udev" ]; then # do your hotplug stuff here sleep 1 else # do your user initiated stuff here sleep 1 fi If $OWNER = "udev", the script is initiated by a hotplug event or the lightning icon is clicked to start the script when the device is mounted. If $OWNER = "user", the "Mount" button has been clicked to mount the device. If the user doesn't want to execute the script when the device is manually mounted, just exit the script. If the script is exited when the "Mount" button is pressed, the operation would then be: Hotplug the device - the device mounts if auto mount is set and the script executes. If the disk is unmounted, clicking the "Mount" button will mount the device and not execute the script. If the disk is mounted, clicking the lightning icon will execute the script. This is what @wacko37 is looking for.

Have the author contact me if there are any questons.

Take the issue back to the script author and have them work it out. It needs to be fixed.

Remove the fi at line #123.

Your script has a problem at line #123.

No.

Put an exit where I show here. When you click on the "Mount" button, the script will exit without running. Then click on the lightning icon: to run the script whenever the disk is mounted.

You want to run the script before the device is mounted? Why?

There is code in the script to differentiate between a hotplug event and a user event - clicking the "Mount" button. 'ADD' ) if [ "$OWNER" = "udev" ]; then # do your hotplug stuff here sleep 1 else # do your user initiated stuff here sleep 1 fi The "user initiated stuff" can be used to exit the script when the user clicks the "Mount" button if you don't want the script to run.

Release 6.11.1 will be released shortly. We've made some changes to SMB that might fix this issue. Please try that.

Yes. Add more memory.

Yes. Sorry for the confusion.

Now that I look at it, I don't think it's a bug, it's wrong in the OP. Unraid doesn't apply the settings on a samba restart, it applies the changes when there is a change in the share settings - when changing the share, or restarting the server.

I'm not sure this is an issue, but you only have 8GB of memory. What I would try is to reboot in safe mode and see if you can reproduce the problem. If not, then install CA manually, and start adding back plugins and see if one of them is causing the error. If the issue still happens in safe mode, post your diagnostics file.

Yes, I stand corrected.

Remove NerdPack and reboot. It's not compatible with 6.11. It looks like you are installing the mcelog package, but that is already in Unraid. Your best bet would be to boot in safe mode, install ca manually and start adding back plugins and docker containers to see if one of them is causing the problem.

Please post your diagnostics file.

I just did a little research on AD and based on what I found is yes, AD can be used for share permissions on an Unraid share. You need to enable AD on Unraid in SMB settings. If you switch back to WORKGROUP, you need to run the fix permissions script on the AD shares to get permissions back to nobody:users.

Start by updating your nvidia driver plugin. You have eth1 and eth2 set up with Jumbo frames (MTU = 9000) , while the eth0 and br0 MTUs are set to 1500. You should set eth1 and eth2 to the default MTU. Jumbo frames requires every device on the network to be set for Jumbo frames in order to work properly. br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.200 netmask 255.255.255.0 broadcast 0.0.0.0 ether 04:d9:f5:21:8e:9a txqueuelen 1000 (Ethernet) RX packets 1607 bytes 563297 (550.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1444 bytes 1412369 (1.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 inet6 fe80::42:d0ff:fe84:1c6b prefixlen 64 scopeid 0x20<link> ether 02:42:d0:84:1c:6b txqueuelen 0 (Ethernet) RX packets 312 bytes 63357 (61.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 251 bytes 74263 (72.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether 04:d9:f5:21:8e:9a txqueuelen 1000 (Ethernet) RX packets 1649 bytes 591715 (577.8 KiB) RX errors 0 dropped 4 overruns 0 frame 0 TX packets 1853 bytes 1434399 (1.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xfc600000-fc61ffff eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet 10.10.10.200 netmask 255.255.255.0 broadcast 0.0.0.0 ether 00:25:90:97:0d:f2 txqueuelen 1000 (Ethernet) RX packets 1643 bytes 372389 (363.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 12410 bytes 17396792 (16.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet 10.10.10.201 netmask 255.255.255.0 broadcast 0.0.0.0 ether 00:25:90:97:0d:f3 txqueuelen 1000 (Ethernet) RX packets 185 bytes 65981 (64.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 82 bytes 24161 (23.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 I don't understand your network configuration. You are not bonding NICs. NAME[0]="br0" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" BRNICS[0]="eth0" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.1.200" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.1.1" METRIC[0]="1" DNS_SERVER1="192.168.1.254" DNS_SERVER2="192.168.1.253" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" IFNAME[1]="eth1" PROTOCOL[1]="ipv4" USE_DHCP[1]="no" IPADDR[1]="10.10.10.200" NETMASK[1]="255.255.255.0" MTU[1]="9000" IFNAME[2]="eth2" PROTOCOL[2]="ipv4" USE_DHCP[2]="no" IPADDR[2]="10.10.10.201" NETMASK[2]="255.255.255.0" MTU[2]="9000" SYSNICS="3" You need to check your network configuration. What are you using eth1 and eth2 for?