• Posts

  • Joined

  • Last visited

Everything posted by Maxrad

  1. I refer you to my post here: Search of SMB shares not working (MacOS client) This this solution improved my experience on macOS working with files on Unraid. I too experienced much frustration shifting away from AFP to SMB as the experience seemed much slower. However, with the right configuration changes (both client-side and server-side) I discovered SMB can be as good, if not superior, to AFP. I hope it helps you out.
  2. 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.
  3. I have experience significant performance improvement using macOS Finder connecting to Unraid SMB shares by applying configuration changes detailed here and (most importantly) here. I hope this helps.
  4. Thanks for reporting on your experience Hoopster. Am interested if your experience supports IPMI while Plex docker container makes use of 2288G Quick Sync Video for hardware transcoding. Reading through this thread suggests it should work but will be interested to learn about this for your build (if indeed use case aligns). Thanks.
  5. I notice you are connecting from macOS FInder. Suggestion here and here (same thread) might help.
  6. 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.
  7. You can check the file exists and its contents typing the following command into manOS Terminal: less /etc/nsmb.conf And it should work fine with any new-ish macOS. I'm running macOS 12.1
  8. Sorry to read problem not yet solved. Did you also apply the SMB Signing (MacOS 10.11.4 and Before) tip on the 45Drives page? Well worth doing on the macOS computer to improve SMB performance. These commands typed in using Terminal on macOS. echo "[default]" >> /etc/nsmb.conf echo "signing_required=no" >> /etc/nsmb.conf …and restart macOS for changes to take effect.
  9. I refer you to my post here: Search of SMB shares not working (MacOS client) This this solution improved my experience on macOS working with files on Unraid. I too experienced much frustration shifting away from AFP to SMB as the experience seemed much slower. However, with the right configuration changes (both client-side and server-side) I discovered SMB can be as good, if not superior, to AFP. I hope it helps you out.
  10. 6.5.54 Early Release available 8 hours ago. Note this is Early Release. I expect the General Release/Official (stable) will be available soon-ish. I can’t comment on vulnerability mentioned. I’ve installed it on my Unifi Dream Machine.
  11. I'm sorry. It seems I misunderstood the problem. I am curious and will follow this thread to learn more.
  12. I too for a long time was very frustrated with very slow SMB connections between macOS and Unraid. I had several (somewhat unsuccessful attempts) at reading Samba documentation and adding various parameter combinations. Then I stumbled across a solution that provides excellent (much faster!) result. See here… My Unraid "Samba extra configuration" optimised (and working well) accessing Unraid shares from macOS Monterey 12.0.1
  13. 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)
  14. 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.
  15. 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.
  16. 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.
  17. 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.
  18. I have three Unraid servers. Two are automatically signing-in My Servers automatically after reboot (1x Unraid Version 6.10-rc1 and 1x Unraid Version 6.9.2) and one isn't (1x Unraid Version 6.10-rc1). I can't work out why one instance of Unraid "My Severs" isn't automatically signing-in or retaining settings after a reboot. If (after reboot) I login to web interface and click "Sign-in" it does so no problem. I hope someone might suggest troubleshooting steps. Diagnostics from troublesome Unraid server attached. Thanks. A bit more detail: Not signing in "My Servers" automatically after reboot. Not retaining "Allow Remote Access: Yes" setting after reboot. Not retaining "Send crash information to Unraid developers: Yes" setting after reboot. Further observation. Reviewing My Server settings after a few minutes My Servers indicates it is still logged-in but: "Allow Remote Access: No" "Send crash information to Unraid developers: No"
  19. I'm using the My Servers plug-in/feature(s). I find it to be a very elegant, very useful and I'm using it routinely to manage my three Unraid hosts. I've followed some (not all) the discussion in this thread with interest. Thank you for the work that has gone into creating/adding and refining My Servers. And thanks also to others that have conducted what seems to be fairly thorough review, testing, evaluation and feedback. Thanks again.
  20. 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.
  21. 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.
  22. I experienced the crashing you describe with my Ryzen 1700X build. I applied the small fix to overcome an idiosyncrasy with the first generation Ryzen processors impacting Unraid. You might find this thread helpful with more information about this issue. There might be other threads in this forum with a better explanation. You might try the following. Shutdown Unraid, pop your Unraid USB flash drive into another computer and carefully modify the syslinux.cfg file to add a boot parameter "rcu_nocbs =0-11" The parameter "rcu_nocbs =0-11" would be suitable for the Ryzen 1600X CPU (a 12 thread CPU). As an example here is my syslinux.cfg file containing the appended boot command appropriate for the Ryzen 1700X (a 16 thread CPU): default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append rcu_nocbs=0-15 initrd=/bzroot label unRAID OS GUI Mode kernel /bzimage append rcu_nocbs=0-15 initrd=/bzroot,/bzroot-gui label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label unRAID OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest syslinux.cfg lines 1-19/19 (END) My Ryzen 1700X build running Unraid has been rock-solid ever since. I'm very impressed with Ryzen CPUs and Unraid. I hope you find this suggestion helpful.
  23. Quiet patience rewarded! Upgraded to - Unraid Nvidia 6.8.3 to take advantage of GeForce GTX 1050 Ti for Plex hardware transcoding. All working well. Impressed with and appreciative of your work. Thank you very much.
  24. 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, 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).