Maxrad

Members
  • Posts

    15
  • Joined

  • Last visited

About Maxrad

  • Birthday 11/25/1971

Converted

  • Gender
    Male
  • Location
    Melbourne, Australia
  • Personal Text
    unRAID Plus | Array 48TB (Store: 6x 8TB. Parity:1x 8TB) | Cache: 1x 500GB NVMe | AMD Ryzen 7 1700X Eight-Core @ 3400 MHz (C states turned off in BIOS) | ASRock X370 Taichi | 16 GiB DDR4 Multi-bit ECC RAM | EVGA GTX 1050ti | Thermaltake Suppressor F51

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Maxrad's Achievements

Newbie

Newbie (1/14)

6

Reputation

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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" travancore1-diagnostics-20210922-1410.zip
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. Quiet patience rewarded! Upgraded to Linuxserver.io - 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.
  11. 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).
  12. A binhex-plexpass docker container for Plex Media Server 1.15.6.1079 isn't being prepared? This update announced here Plex Media Server 1.15.6.1079 is now available to Plex Pass users in the Beta update channel about five hours ago. Perhaps I should just wait patiently. I very much appreciate binhex's work. Thanks.
  13. This looks very similar to my build. unRAID Plus | Array 40TB (4x 8TB array, 1x 8TB Parity, 0x SSD Cache) | AMD Ryzen 7 1700X Eight-Core @ 3400 MHz (C states turned off in BIOS) | ASRock X370 Taichi | 16 GiB DDR4 Multi-bit ECC RAM | EVGA GTX 1050ti | Thermaltake Suppressor F51 I went with the ASRock X370 Taichi because it features 8 SATA ports (plus 2 by ASMedia ASM1061). I've been very happy with this build running very well for several months primarily as a Plex media server. The MSI X370 SLI Plus features 6 SATA ports. I disabled Ryzen C-state in BIOS settings.
  14. My testing was less comprehensive (I hadn't noticed modification dates) but came to same conclusion. I'm not longer using AFP. I'm happy with unRAID SMB setting "Enhanced OS X interoperability" set to "Yes" and macOS Finder connections to unRAID using SMB (Connect to Server smb://sam@192.168.30.40/Media) 🙂
  15. Upgrade from 6.6.7 to 6.7.0 okay. Initially macOS Finder tags applied to files and folders on share (connected via SMB) vanished – no major consequence. Change SMB setting "Enhanced macOS interoperability: Yes" restored macOS Finder tags applied to all files and folders. unRAID Plus | Array 40TB (4x8TB array, 1x8TB Parity) | 0x SSD Cache | Ryzen 7 1700X | ASRock X370 Taichi | EVGA GTX 1050ti | Thermaltake Suppressor F51 | 16GB RAM | Docker containers: binhex-plexpass, tautulli, HandBrake, transmission.