the file will play, then restart once finished saying it’s part 2. The affected episodes show as double the length, due to it believing it’s 2 parts.
what’s even more strange, I’ve found that when I mark as played/watch it & then skip the duplicate, it goes back to recognising it as one file.
It seems to affect everyone that my library is shared to.
When I sort TV programmes by episodes rather than shows, then select ‘duplicates’, I find a random selection of 300ish episodes are affected. When you click get info on them, you can see that it’s the same file twice. The files only exist once.
I have tried rescanning the library, reanalysing the show, ‘the plex dance’, the file naming and path convention is all fine (as shown in the screenshot.
I’m not sure how logs would help in this scenario given that it doesn’t require any activity to happen, but if there’s anything else needed , please let me know
edit: The TV Shows library has 2 paths, both of which are on completely different drives (and so no overlap)
Please drag screenshots directly into the forum message editor.
There is no need to let a 3rd-party website collect yet another set of usage data from all forumists who are looking at this thread.
Occurences like this are often caused by 2 overlapping library scans.
Is your library scanned both periodically and automatically, (and/or perhaps library scans are triggered by an external software or additions are made during the server maintenance hours)?
The only way to repair this is AFAIK a Plex Dance.
Or inspect them yourself. Take a look at the Plex Media Server.log file and seek for messages about database corrupt or malformed.
If you find these, you may have to repair your database. https://support.plex.tv/articles/repair-a-corrupted-database/
Both are enabled. So should I just have the one, and is there one option superior to the other that I’d be best leaving enabled? I’ve been running without changing these settings for a few years now without issues
I forgot to clean bundles after the last plex dance and this has solved the issue for one episode,
Around 300+ random episodes of different shows across 2 drives are affected, so it’s going to be a bit of a job!