Reini

Same for me with Version 7.0.1: unRAID nginx: 2025/03/20 11:39:30 [error] 4070043#4070043: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory ...

@limetech this request wasn't considered within 15 month. What do I have to do to get attention here? Please respond.

No. Only with the described manual changes, it's possible to get it to work - including AD authentication - without any issues.

I was hoping to get this "Feature Requests", which was already implemented in the past, reactivated in the actual 6.10.x Version. But after 15 month, nothing happens. So, I still need to using "User Scripts" to get the /etc/samba/smb-shares.conf manipulated. This is not good, really "☹️"

@limetech, some news on this? Please give some feedback. Thanks.

Dear unRAID Team, Some news on this?

If SMB Settings "Enable SMB" is set to "Yes (Active Directory)", which means "AD join status" is "Joined", then the setting "Enhanced macOS interoperability" setting to "Yes" and the "SMB Security Settings" at "Export" setting to "Yes/TimeMachine" doesn't work for using it on Apples Time Machine. (AFP is also extremely instabil in Active Directory Services (ADS) for more (4+) Macs doing Time Machine Backups. If good luck, then it works some weeks. Next is unRAID's note: "Please note that AFP is deprecated, please use SMB instead.". This will prevent from using AFP - but it's OK.) At the moment, the only way to get SMB based Time Machine backup running in ADS environments with more Mac-Users is to add these lines to "Samba extra configuration:" This must be done, because if "Enable SMB" is set to "Yes (Active Directory)", all "macOS interoperability" settings will be ignored from unRAID OS - so far as I remember from Tom (cause of ADS problems in the past). With the quoted settings above, we are running SMB based Time Machine backups in an ADS environment long time without any issues. But there is one problem, because these settings are global, the option "fruit:time machine = yes" and "fruit:time machine max size = 4T" is valid for ALL shares. If Macs are connecting to any other share, the share limit is 4TByte for ALL shares. Leaving the option "fruit:time machine max size = 4T" is not an option, because Time Machine is taking ALL available storage. So, please re-enable the "macOS interoperability" and TimeMachine based GUI settings if ADS is active (SECURITY="ads" in /boot/config/ident.cfg) to prevent from manual adding "Samba extra configurations". Thanks in advance.

It seems that the "Time Machine support via SMB" is not working if Active Directory is enabled (joined to an Active Directory domain controller) at the SMB settings. Correct?

You mean it's not possible to configure it over the unRAID GUI - correct? Because on OS level, it is possible to configure different MTU sizes at different VLANs on the same physical interface.

Hi unRAID-Team, are there some news on this topic?

I got a new unRAID system with a 2x 10GB NIC for 802.3ad bonding as a single trunk (bond0). Have also configured 3 VLANs and want to configure the MTU of one of these to 9000 (jumbo frames). It is possible to set the MTU to 9000 on the interface (default VLAN at br0) itself. But I couldn't find out how to set the MTU only on the 2nd VLAN (br0.777) to 9000 and leave the other both VLANs (br0 and br0.666) to MTU 1500. (Have already set up different Linux-Systems with this settings successfully) It would be great if anybody has any idea how to configure it at unRAID. Thanks in advance.