Indeed, I agree with this assessment: improved, but not solved.
I ran the thrashing script (from the Feedback report I filed with Apple) on Tahoe over the last two days, and while Tahoe is definitely better, it isn’t perfect. It fails less often, but it still fails on occasion, especially if the Finder (and perhaps other processes) are also monitoring the folder. I can cause this failure condition by running the thrashing script while having Finder open to the same folder. It’ll almost always fail in that case. With the Finder closed, though, it’ll often pass the test.
With the nsmb.conf file in place, though, it never fails, even with the Finder open to that folder. So they still have some kind of issue to address.
Fortunately (?), Apple hasn’t asked me to verify the bug on Tahoe as a result of my report. That would normally be the case if they thought it was fixed in this release…at least based on my years of experience with bugs and Apple.
OS26 beta seemed to the be the fix at first. It ran for a month without any issue but I didn’t post here because I didn’t want to suggest people using beta software, as it was buggy as hell, but didn’t bother me since my Mac mini is headless and not a daily driver. Before OS26 I couldn’t get things to work for more than 24 hours with the conf files, automounter, etc. Disappointed to say that after updating to the official NON beta released last week, the problem came back this morning.
I am now going to try the Synology SMB setting changes.
For what it’s worth, I gave up on this problem a long time ago, and just installed Plex on my Synology. To my surprise, it actually transcodes everything ok, with 2 caveats. 1. It does WEB-DL 4K fine, but buffers with 4K Remux and CPU usage is a constant 90%. 2. single stream only.
Mods to the Synology are 32GB RAM and Plex is installed on an nVME volume.
That is interesting it was fine on Beta but not on the Public.
I’m curious if they use some extra settings for beta that help keep things alive, reporting/logging, that they turn off for public. hopefully the upcoming .1 beta will bring that fix back?
Re Synology, I think I’ll personally begin migrating away from synology, as their lockdown on drives is getting annoying, either a DIY or I’m also looking to switch to SSD, but getting affordable ssds for 90TB is a bit much. (I want less noise and size)
I have a related issue, with music files. In many folders i had both .mp3 and .FLAC files for the same music files, I deleted the .mp3 files and now the folders in Plex show the trashcan icon, even though the .FLAC files are still in the folder and accessible. I have scanned the library and for some reason it is still picking up the deleted .mp3 files. I can delete them manually in Plex, and that removes the trash can icon, but seems there must be a better way to remove these ghost files?
this does sound like a different issue, your issue sounds like doing the plex dance may be your better option. Or trying the empty library trash, as they will stay there until trash is emptied, either as the schedule task or manually if you have that turned off.
the issue on this thread is related to SMB mounts basically not being kept alive or being woken back up by Mac for Plex.
Issue persists with macOS 26.1. Most all my movies have a red trash can post library scan for the 3rd time in a row (restored from backup twice). It’s driving my nuts..
I agree. If anything, it feels like it’s gotten worse. And I have the recommended nsmbd.conf and Synology settings from earlier in the thread in place.
The etc/nsmb.conf mods were having a detrimental effect on my Chronosync jobs, so had to reverse any changes made. In particular the setting dir_cache_off=yes was causing very slow backups. One thing I have noticed, is that automatic Plex library updates always seem to run without issue. It’s the manual library scans that cause the trashcan icons to appear for me.
For those having issues, especially in MacOS 15, there is a HUGE bug in Spotlight that can cause this same behavior. If this is the case, STEP 1: You can temporarily fix it by running DiskWarrior and then Disk Utility. STEP 2: To permanently fix it, you need to have the machine stop spotlight from indexing and would probably be best to delete the spotlight database on the drive. Regardless, you should do step one after you do step two.
To be able to effectively search your files, I use NEOFinder to auto catalog the drives.
Hello all. I found this thread after some searching because I am experiencing the same issues. I just migrated PMS to a Mac mini M4 with my libraries on my Synology NAS - with an SMB mapping. I’m running PMS 4.147.1 on MacOS 26.2. I’ve just installed Automounter to see if this resolves my disconnecting network drive.
I’m also having an issue with my libraries not auto updating when I add new media unless I run a manual scan - but this will sometimes result in my files showing as “unavailable.” I have not modified any files on my Mac. This issue is very annoying! I do have Scan my Library Automatically enabled, and also have it set to do a scan every 15 minutes - still no dice.
Have you tried the modifications to etc/nsmb.conf as listed in this thread?
I have a very similar setup as you and between Automounter and the etc/nsmb.conf modifications my setup is extremely stable in regards to network files.
I hadn’t, but now I have completed this. Ran a manual scan and none of my files switched to “unavailable.” Thank you!
My library still does not auto update when I add media, is this related to this SMB issue, or should I continue to troubleshoot this? I understand this isn’t the thread for that issue if unrelated. Thanks again