macOS Server "forgets" movies and tv shows exist randomly

Server Version#: 1.41.8.9834
Player Version#: N/A
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

I’ve running a Windows server for many years. I am now also running an instance on a Mac Studio, adding my libraries one at a time. When my Mac server is stable, I plan on turning off the Windows instance.

All of my media files are on a Synology NAS.

What’s happened is that the Mac instance didn’t see all the files that the Windows instance saw. I found out that, in the thousands of files, each one could be “owned” by one of two IDs. When I cleaned that up - setting the ownership of every file to the ID that the Mac could clearly see, it seemed to clear up.

However, now, suddenly, the Mac will ERASE knowledge of more than half the library (1500+ movies, as an example). I’ll literally be doing nothing and suddenly see the status screen on a web browser blink and poof now it’s 650 or 900 movies instead of 1500. Then they’ll come back (with the annoying side effect of also going to the head of the “Recently Added” lists).

I wanted to identify a specific movie that exhibited this behavior. “A Beautiful Day in the Neighborhood” shows up on my Windows instance, but not the Mac instance. All movies are in one parent directory on the NAS. All files have the same owner. There are a few folders that also have the same owner as do all the files in those few folders.

As I’m writing this, suddenly I see that my movie count has gone from the 600s to 1115. (The above mentioned movie is still not in the Mac’s library).

Scanning the log directory, the word “Neighborhood” doesn’t show up at ALL except for a message scanning an unrelated TV episode that happened to have “Neighborhood” in the filename.

When this happens, my Mac starts driving itself crazy scanning for the credits of all the new-but-not-REALLY-new files that have suddenly returned (even though they were scanned days ago, but vanished so I guess Plex decided to erase the memory of every having had them)

When I manually tell it to scan a particular library, sometimes if “recovers” some of the files, but, evidently, not all of them (I don’t know if the scan-for-credits process is interfering with that).

I have a large library containing some 42TB of data (plenty of raw video in there as well). Am I bumping into some kind of restriction on macOS? While searching I saw something about a problem because of the NAS not responding in time. Sometimes my drives have to spin up. If this could be the case, is there a setting somewhere to tell the server to wait a little longer? I wouldn’t think I’d need it because this does NOT happen on the Windows instance.

Help!!!

Update - as a matter of information, I’m running macOS 15.5.

And I just had it happen AGAIN. 1500+ movies yesterday, 1100 today and WHILE I WAS WATCHING THE MAIN SCREEN - poof down to 665.

Since the original post, I’ve updated the server version to 1.41.9.9961

WHAT IS GOING ON? There should be NO reason why Plex does, then doesn’t see a file that hasn’t been touched - and the Windows box doesn’t see ANY of this kind of behavior so it’s NOT my NAS.

What’s even stranger is that this ONLY occurs in the Movies library. In my library of TV shows/series, it’s rock solid - never bouncing around - and that library is on the same NAS, same access, same share (just different top folders).

Are there any Mac specialists in Plex support?

Did you check the thread posted in the comment previous to your most recent? There’s a known issue with macOS Sequoia with Synology NAS devices in particular. There’ve been some posts which have suggested that making changes to (or adding with those setting) /etc/nsmb.conf helps resolve the issue. It’s also been suggested that Apple is working on a fix.

And turn off “Empty trash automatically after every scan” in you server’s Library settings. That will mitigate the data loss, to an extent, until Apple gets their stuff together.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.