For me is working fine:
- macOS 15.5.
- Empty /etc/nsmb.conf.
- In the Synology, Enable SMB3 directory leasing. Apply to all shared folders.
- No errors in your script.
Anyone attempt with plain os26 Tahoe?
I’m mid data scrubbing so don’t want to do anything that could cause large scale calls.
I’m way to terrified to be the Guinea pig on this one.
@Anyware @gmfreed @Speidel Is there any single post in this thread that we can elevate as a solution for this thread? Seems like this recent post is a good candidate. Obviously if your storage source is not Synology, then maybe just make the /etc/nsmb.conf edits.
My ask for a Solution tag is merely for ease of discovery for any new users finding this thread. This isn’t something I’ll be forcing, just an ask for consideration from the more active members here and the OP. Huge THANKS!!! 
to you active members here for all your guidance, testing, and assistance in this thread. It is very much appreciated!
The request for Direct SMB connection within Plex was filed awhile ago but is a heavy lift and not something we’ll be able to tackle for some time. Sorry…
4 Likes
@Atomatth… yeah that should be a good place for users to start. Some of us have slightly different Synology settings, but I believe the rest is the same across the board. the conf file and using Automounter to connect to the smb shares seems to be the main changes that fix this for most users.
Thanks for the update on possibility of a direct SMB option in the future.
Did not have any issue for weeks thanks to all the workarounds from this thread… until today and of course it’s just after I left for a trip abroad. So, I’m sorry if it’s slightly off topic but do you guys have any recommendation on how to remote login into a Mac ? I just need to re-mount servers connection.
I am using google remote.
[https://remotedesktop.google.com/]
1 Like
Yeah that makes sense. Ok so for next time, what would be my options ? All the solutions I seem to find online look more like screen sharing than remote login. Is there anything similar to synology quickconnect for a Mac ?
@GastonK pretty smooth experience for me with JumpDesktop
1 Like
@Atomatth I took the liberty to put this together. Hope it helps peeps.
Plex Media Marked “Unavailable” on Mac (Synology NAS via SMB) – Root Causes & Solutions
Understanding the Issue and Symptoms
Many Mac-based Plex Media Server users (especially on macOS 15 “Sequoia”) have reported a strange issue: Plex suddenly flags a large portion of their library as missing (red trash-can “unavailable” icons) even though the files still exist on an external NAS. In these cases, Plex may stop updating new files and mark existing ones as “unavailable,” yet local playback (or third-party players) can still access the files. Remote Plex clients, however, fail to recognize/play those items because Plex believes the files are gone.
This often occurs sporadically and without a clear pattern. Sometimes after a manual or scheduled library scan, you’ll see perhaps half your TV shows or movies suddenly marked with the trash icon. If Plex’s Empty Trash feature runs at that moment (either automatically or manually), it can purge those entries from your library—causing you to lose posters, watch history, and metadata until the files are re-added later.
IMPORTANT TIP: Disable “Empty trash automatically after every scan” immediately to prevent data loss while troubleshooting.
Users have observed that this bug tends to affect network-mounted media (e.g. SMB shares from a NAS) on macOS 15+. One person described it as a “yo-yo” – a scan might randomly mark a set of files unavailable even though they’re present, and a subsequent scan might bring some back while marking others missing. In one case, two-thirds of an entire library was erroneously deleted from Plex after a scan, despite the files still residing on the NAS.
Importantly, this mostly seems to happen on macOS, and started after upgrading to macOS 15 “Sequoia” – strongly hinting that something changed in Apple’s network filesystems.
The issue doesn’t appear to be caused by Plex settings or network dropouts (the NAS and network are otherwise stable), nor by user error; rather, it’s a compatibility bug between Plex and the way macOS handles SMB-mounted drives in recent versions.
Root Cause Analysis: macOS SMB Bug
All evidence points to a bug in macOS’s SMB client introduced around macOS 15. In short, Apple’s SMB network-drive handling is not reliably reporting directory contents or connectivity status to Plex.
Plex relies on the OS to access the files; if the OS intermittently fails to see the files or times out, Plex will think those files vanished. Community experts and Plex staff confirm that this problem is due to a buggy SMB implementation in recent macOS versions. It’s not purely a Plex bug—other software that heavily accesses SMB shares can encounter similar issues—but Plex’s library scanning makes the problem very visible. In essence, the Mac is losing the mount or cache briefly, or returning incomplete directory listings, and Plex interprets that as files being gone.
Specific Technical Factors Theorized
-
SMB Directory Caching/Leasing Issues
macOS 15 introduced changes to SMB caching. When a folder contains a very large number of items (e.g. > 1 000 files or subfolders), the Mac’s SMB client might not report all of them to Plex during a scan. This can make Plex “drop” media entries during library updates due to stale or limited directory caches. Disabling client-side directory caching on macOS completely stopped the disappearing-files problem for some users. -
SMB3 Multi-Channel and Protocol Quirks
Mac Minis with Apple Silicon and fast networks can use SMB3 features like multi-channel. There’s anecdotal evidence that SMB multi-channel or signing on macOS contributes to instability. Turning off SMB3 multi-channel support on the Mac (along with other tuning) greatly improved stability. Multi-channel is meant to improve throughput by using multiple connections, but if there’s a macOS bug in its handling, it could cause the share to reset or drop under load. -
Lack of Real-Time Change Notifications
Unlike local disks, network filesystems on macOS don’t send instant “file changed” events to Plex. Plex won’t know a file is gone or added until it scans or tries to access it. If the NAS drives are asleep or the connection has transient hiccups, the first access could fail. However, in these reports the NAS was accessible outside Plex and files could be manually browsed, so a simple timeout due to drive spin-up is likely not the primary culprit. It’s more about the OS erroneously reporting files as missing or not letting them all be seen as they need to be. -
macOS 15 Network Stack Changes
Early in macOS 15’s release there were known networking issues affecting VPNs and security tools. Some users suspect the macOS firewall or network stack might interfere with SMB traffic. Temporarily disabling the macOS firewall has been suggested as a test. While not a confirmed fix, it’s worth ensuring nothing in macOS is actively blocking or timing out your NAS connection.
Solutions and Workarounds
Several effective workarounds have emerged. You may need to combine these to fully solve the problem:
- Tweak macOS SMB Client Settings (
/etc/nsmb.conf)
Create or modify/etc/nsmb.confon your Mac with:
[default]
dir_cache_off = yes
mc_on = no
dir_cache_off = yesdisables client-side directory caching.mc_on = noturns off SMB3 multi-channel.- After creating the file and rebooting, Plex should no longer “lose” your media during scans.
-
Adjust Synology SMB Server Settings (Enable SMB3 Leasing)
In DSM 7.2+ under Control Panel → File Services → SMB → Advanced, enable SMB3 directory leasing for all shared folders. This improves client-side locking and helps macOS enumerate files reliably. -
Use a Persistent, Single Mount
Continue using AutoMounter (or similar) to keep the NAS share always mounted. Ensure macOS isn’t also mounting the same share via Login Items or Recent Servers, which can create duplicate mount points and confuse Plex. Aim for a single, never-sleeping mount point. -
Prevent Automatic Library Trash Removal
Disable Plex’s Empty trash automatically after every scan (under Settings → Library). This avoids turning a temporary glitch into permanent data loss. With auto-trash off, accidentally marked-missing items will return on the next scan once the share reconnects. -
Consider Alternative Protocols or Clients
- NFS: macOS supports NFS mounts and they tend to be very stable for continuous media streaming.
- AFP: Although deprecated, AFP can still be used on macOS and Synology. Some users found AFP mounts did not suffer the SMB-related “trash can” issues.
- Third-party SMB (e.g. rclone’s go-smb2): Bypasses Apple’s SMB stack entirely, avoiding the bug, though with slightly lower performance.
- Keep Systems Updated & Monitor for Native Fixes
You might want to apply macOS and Plex Media Server updates as they arrive. Up to you. Apple or Plex may eventually address the underlying SMB bug. If a future macOS release fixes it, you can remove the custom/etc/nsmb.conftweaks file.
Conclusion
The Plex “files unavailable” issue on Mac Mini is not user error but a macOS SMB client bug introduced in Sequoia. Plex reacts to what macOS reports—if Apple’s SMB implementation briefly fails, Plex flags media missing. A true fix likely has to come from Apple.
By disabling directory caching and multi-channel on the Mac, enabling SMB3 leasing on the Synology, maintaining a single persistent mount, and disabling auto-trash in Plex, you can work around Apple’s SMB quirks and keep your library intact.
Should the problem persist, fallback options include NFS, AFP, or third-party SMB clients. In the meantime, these workarounds will help ensure your Plex server remains connected to your Synology library without losing metadata. Good luck!
8 Likes
i wish google remote worked, but for some reason, because of my 49" UW screen everything is tiny and i cannot figure out how to adjust the screen size for remote access or atleast give me a magnification option
@rogo43… I just use RealVNC Lite. I do not have an UW monitor connected to my plex server, but RealVNC I believe allows you to connect with a specific resolution. Worth a shot. They bury the “Lite” version on their website, since it’s free and they want you to pay, so here is a direct link:
3 Likes
yeah I haven’t bit the bullet on this one either.
my backup Mac mini that I would attempt with, is from 2018, so its not compatible with Tahoe.
They have responded to the bug filing with a note that the issue should be addressed in an upcoming release (or words to that effect). We just don’t know which release.
4 Likes
i hear ya. im running Plex off an M1 Base Mac Mini, but im considering upgrading to either an M4 to run as a dedicated server or maybe get an M3. Not sure which to do. What do you suggest?
i prefer mac honestly. I know its dumb, but i just do.
3 Likes
Me too.
I am running a Mini in 2 versions. A 3.2 GHz 6-Core Intel Core i7 (2018) and an M2 Pro (2023).
I can say that either will host Plex more that sufficiently. However, the M2 Pro can be more than 3 times faster on the same task. Turning on hardware support on the M2 Pro (not an option on the i7) and it’s even faster.
More than once, I wished I’d cloned my i7 workstation to the M2 Pro and used the i7 as the server. Oh well… next upgrade will move the workstation ahead.
I followed the commendations on my M2 Pro install. I don’t have a Samba config file. I did use Autoloader to map to [path]/movies ([path]/tv shows) and also have map on login to map to just [path]/. This avoid the possibility of a name-1 issue and I’ve not had problems since.
yea. i think ill go with an M4 Mac Mini, Run plex like i am and then run all the ARRs on it as well and use the Synology as a storage device only.
