[Unraid OS version 6.10.0-rc4 available]

macOS Finder SMB connections to three Unraid (Unraid OS plus) servers on local network (Uraid 6.10-rc3 and Uraid 6.10-rc4) have been rock-solid reliable for me. Several days testing with numerous transfers of 10s folders, 100s files, 2-40 GB total (mostly MP4 files) at a time.

[[6.9.2] SMB 5X Slower Now. Please Make This a Priority.]

I notice you are connecting from macOS FInder. Suggestion here and here (same thread) might help.

[Search of SMB shares not working (MacOS client)]

Thanks for the thanks.

 

The Unraid "Samba extra configuration" change has been well worthwhile but the real "gold nugget" in the KB450114 – MacOS Samba Optimization article is the section "SMB Signing (MacOS 10.11.4 and Before)". I highlight it here because it has been just soooo good for me. This client-side (ie on macOS) configuration change is key for speeding up SMB operations on macOS Finder connecting to Unraid.

 

EDIT. Probably disregard the suggestion in this post "Since the release of OS X 10.11.5, Apple’s SMB Signing has been enabled by default."

[Unraid OS version 6.10.0-rc2 available]

On 12/2/2021 at 12:31 AM, ThatDude said:

Was any progress made regards samba and access from Monterey based Macs?

 

I was hoping a Samba extra configuration change could address the issue(s).

There are bugs in samba version 4.15.0 included in Unraid 6.10.0-rc2 impacting SMB connections from macOS. Bugs noted in samba version 4.15.1 release notes. I have reverted to 6.10.0-rc1 and wait (with calm patience) for a future release of Unraid containing newer samba version. See this post for a bit more info on my experience optimizing Unraid samba for macOS:

 

Unraid 6.10.0-rc1 and Unraid 6.9.2 both seem to provide me with reliable SMB connections for macOS (including Monterey 12.0.1)

[Search of SMB shares not working (MacOS client)]

Below I include my Unraid (Version: 6.10.0-rc1) "Samba extra configuration". This configuration is working  well for me accessing Unraid shares from macOS Monterey 12.0.1

 

I expect these configuration parameters will work okay for Unraid 6.9.2. The "veto" commands speed-up performance to macOS by disabling Finder features (labels/tags, folder/directory views, custom icons etc.) so you might like to include or exclude these lines per your requirements.

 

Note, there are problems with samba version 4.15.0 in Unraid 6.10.0-rc2 causing unexpected dropped SMB connections… (behavior like this should be anticipated in pre-release) but fixes expected in future releases.

 

This configuration is based on a Samba configuration recommended for macOS users from 45Drives here: KB450114 – MacOS Samba Optimization.

 

#unassigned_devices_start
#Unassigned devices share includes
   include = /tmp/unassigned.devices/smb-settings.conf
#unassigned_devices_end

[global]
   vfs objects = catia fruit streams_xattr
   fruit:nfs_aces = no
   fruit:zero_file_id = yes
   fruit:metadata = stream
   fruit:encoding = native
   spotlight backend = tracker

[data01]
   path = /mnt/user/data01
   veto files = /._*/.DS_Store/
   delete veto files = yes
   spotlight = yes

 

My Unraid share is "data01". Give attention to modifying the configuration for your particular shares (and other requirements). I hope providing this might help others to troubleshoot and optimize SMB for macOS.

[Unraid OS version 6.10.0-rc2 available]

I notice Samba 4.15.1 (release notes) contains fixes for macOS. Most grateful if this could be rolled into the next Unraid build to hopefully resolve SMB connection problems. Thanks.

[Unraid OS version 6.10.0-rc2 available]

I think resolved my earlier reported problem of unreliable SMB connections from macOS Monterey 12.0.1 to Unraid 6.10.0-rc2. Removing several user-added parameters (ie added by me several months back) from "Samba extra configuration" seems resolve my problem and I now have reliable SMB connections between macOS Monterey 12.0.1 and Unraid 6.10.0-rc2 (samba: version 4.15.0).

 

My "Samba extra configuration":

#unassigned_devices_start
#Unassigned devices share includes
   include = /tmp/unassigned.devices/smb-settings.conf
#unassigned_devices_end

[global]
   spotlight backend = tracker 

[data03]
   path = /mnt/user/data03
   spotlight = yes

My configuration adds SMB share point "data03" with support for macOS spotlight search. Unraid 6.10.0-rc2 now working very well for me – thanks for great work!

 

EDIT: I posted success too soon. This (intermittent) problem is not resolved.

[Unraid OS version 6.10.0-rc2 available]

On 11/4/2021 at 6:24 AM, Toskache said:

Problem with macOS Monterey?

 

I updated from 6.9.2 to 6.10.0-rc2. At first everything looked fine...
But then when I tried to copy two larger files from a macOS (Monterey) to a samba share, the copy process did not start. The share was even ejected. The share was mounted via simple "network browsing" (smb://nas._smb._tcp.local/data). The whole thing is reproducible. It seems that copying smaller files works. I reverted back to 6.9.2.

 

 

I've been using macOS Monterey 12.0.1 Finder SMB connection to Unraid 6.10.0-rc1 without problem – folders and files copy to and from with the SMB connection stable. However, similar to Taskache's reported experience SMB connection  between macOS Monterey 12.0.1 Finder and Unraid 6.10.0-rc2 fails when copying files.

 

When copying a file (small or big in size) the transfer seems to finish copying but Finder then immediately drops the SMB connection. The SMB connection doesn't drop at the end of every file copy – perhaps about 50% of the time. A new macOS Monterey Finder SMB connection (Command K) is successful.

 

My "Samba extra configuration":

#unassigned_devices_start
#Unassigned devices share includes
   include = /tmp/unassigned.devices/smb-settings.conf
#unassigned_devices_end

[global]
   mangled names = no
   dos charset = CP850
   unix charset = UTF-8
   spotlight backend = tracker

[data01]
   path = /mnt/user/data01
   spotlight = yes

 

It seems something changed with Unraid 6.10.0-rc2. I wonder if a Samba configuration addition/change might deliver a more reliable SMB connection.

 

EDIT: After reviewing Samba documentation and some experimenting I believe I resolved this problem, noted here.

[Search of SMB shares not working (MacOS client)]

I modified SMB Extra to:
 

#unassigned_devices_start
#Unassigned devices share includes
   include = /tmp/unassigned.devices/smb-settings.conf
#unassigned_devices_end

[global]
   spotlight backend = tracker

[Media]
   path = /mnt/user/Media
   spotlight = yes

 

… rebooted Unraid 6.9.2 and spotlight search seems to be working again in macOS Finder over SMB! I haven't  examined logs for potential adverse events but will do in a little while.

 

[Search of SMB shares not working (MacOS client)]

After upgrading from Unraid 6.8.3 to Unraid 6.9.1 I immediately encountered the problem described in this thread. macOS connecting via SMB to Unraid share unable to search. I tend to search on filename and file kind from macOS Finder.

 

I cautiously attempted to apply configuration parameters described in this thread, but unsuccessful returned the Unraid 'SMB extras' field to original text.

 

It would be great if a future update to Unraid might include feature(s) to more easily configure Samba to support Spotlight search. Otherwise I expect I'll invest some time in to learning more about Unraid Samba implementation and Samba configuration.

[[6.7.x] Intel iGPU Hardware Transcoding does not work with Plex + Docker]

I recently built my second Unraid server to host Plex Media Server – this build Intel-based. I am expecting this server will serve mostly video media that doesn't require transcoding. For media that does requires transcoding I'm expecting to favour using software transcoding instead of hardware transcoding. I am however curious to evaluate Intel Quick Sync Video for hardware transcoding. For now, hardware transcoding is not a priority for me.

 

Reading through this forum thread I understand Plex Media Server (Plex Pass) running on Unraid 6.7.2 to leverage Intel Quick Sync Video hardware transcoding is currently not working. This seems to be the case for me – when transcoding the "(hw)" identifier is not appearing in Plex Dashboard.

 

I can contribute one small bit of troubleshooting information that may (or may not) assist developers and/or users (below).

PLATFORM
Unraid OS Plus 6.7.2, ASRock Z270 Gaming-ITX/ac (Bios Version P2.50), Intel Core i7-7700 CPU @ 3.60GHz, 8 GIB DDR4, binhex-plexpass (Plex Media Server, Version 1.16.2.1297), tautulli.

Array: Parity 1x 2TB (Hitachi_HDS722020ALA330), Storage 5x 2TB (Hitachi_HDS722020ALA330). 
Cache: Samsung SSD 970 EVO Plus 500GB (nvme)

The iGPU is identified by Unraid.

 

System Devices:
IOMMU group 2:    [8086:5912] 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)

 

The presence or absence of a fit-Headless (1080p) connected to the motherboard's HDMI port (iGPU) does NOT seem to support enabling hardware transcoding. 

 

The presence or absence of a fit-Headless (1080p) connected to the motherboard's HDMI port (iGPU) produces the same result when entering the following terminal commands

 

Linux 4.19.56-Unraid.
Last login: Sun Jul 14 15:55:51 +1000 2019 on /dev/pts/0.
root@SilverStone:~# cd /dev/dri
-bash: cd: /dev/dri: No such file or directory
root@SilverStone:~# ls -la /dev/dri
/bin/ls: cannot access '/dev/dri': No such file or directory
root@SilverStone:~# 

I look forward to evaluating Intel Quick Sync Video for hardware transcoding at some point (but it is not a high priority for me).