PLEX Creating duplicates of all my music without end

I am running the latest version of Plex for Synology NAS. 1.40.2.8395-7000
Recently, when I tried to scan my library for changes, I saw that Plex kept adding copy after copy after copy of the exact same album, to the point that my 215–220 albums, quickly turned into over 1600 and counting. It did not stop until I canceled the scan. By that point, I ended up with 5 to 10 copies of each album, all identical. When I would try to delete the extra albums, I would encounter an error message, saying something to the effect of the operation cannot be completed, or there was an error, something to that effect. Because of this, Plex has become unusable for me , At least for music. What is most frustrating, is that up until now I have had absolutely no problems with Plex scanning my albums correctly, but now all of a sudden, it has gone haywire and made it impossible to use it to play music.
I’m also having metadata problems with my TV shows, although in that case they are, I am seeing is manifesting in a different way. and again, as with my music, it’s a recent development, as both of these issues seem to have started roughly around the same time.

Any help trying to identify the Cause of this behavior would be greatly appreciated.

Attach a set of server logs that capture the problem.

Which ones? I am sorry but I am new at this. When I downloaded the logs, there are dozens of files. I would not know where to start looking …

Upload the entire zip file.

Drag it into the message window. The file will insert at the cursor location. When it finishes uploading, click Reply.

Plex Media Server Logs_2024-05-16_16-39-57.zip (3.7 MB)
Here they are…

It looks like you have snapshots enabled, and Plex is picking up the files in the snapshots.

I did a quick search on the forum.

See this post: Scan results in hundreds of duplicate items in Music Library - #18 by Kubjo

After you get Plex to stop scanning snapshots:

  1. Re-scan all libraries
  2. Empty Trash
  3. Clean Bundles

dance


Then:

  1. Stop Plex Media Server
  2. Wait one minute
  3. Start Plex Media Server.
  4. Wait three minutes (to fully start & log everything).
  5. Pull & post the log files.

Scanning the snapshots is causing some other issues. It should resolve itself by not scanning the snapshot folders, but need to double check.

The Notify errors mean you’ve exceeded the number of directories Plex can monitor (you’re not really out of space). Not scanning the snapshot directories should bring you below the limit. If it does not, it is easy to fix things: FAQ 16: Increase the number of folders Plex can monitor

From Plex Media Server.log:
May 16, 2024 16:20:15.679 [140225138244408] ERROR - [Req#128d7] [Notify] Failed to add watch for "/volume1/music/#snapshot/GMT-04-2024.04.27-10.00.01/THE WORLD OF SYMPHONY/TWOS 4_ The World Of The Symphony [Disc 4]" (28: No space left on device)

WOW. I never thought that snapshot creation would do this to my server. It seemed like a good idea at the time, but I have my media backed up, so it is not really needed… especially if it is causing these kinds of headaches.
I am going to disable them for my media folders and re-scan the libraries. See what happens.

Thank you so much!!. I will update with results.

Update: I actually took the semi-drastic step of deleting all the metadata as well as the snapshots associated with the media folders (just in case). After re-adding each library one by one, and re-scanning each in turn, the issue seems to have resolved itself.

Thanks again, @FordGuy61

If I may augment ?

I worked with FordGuy on this a little bit.

I went into the PMS file scanner source and checked the list of Folders it should be ignoring…

This is an oversight. It looks like snapshots are implemented differently on DSM 7 and BTRFS .

I’ve done the source code work for Engineering to confirm and implement.
Should be a quick trivial fix.

1 Like

Absolutely. Thank you for the clarification. I guess I will keep snapshots off until the fix has been put in place .

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