@NewPlaza said:
Not that I don’t believe you, but we hear this many times and found out the naming was incorrect, or at the very least, inconsistent with the current standard.
This is not a problem of missing metadata, this is a problem of Plex doesn’t scan in the bottom 2 network drives. Since it doesn’t scan, there is no log for those drives despite the drives and files are all good.
I would start by examining your ANIME share. If Plex does not complete a scan then there could be a corrupt file or two causing the hangup. You could remove the path or add the path to the bottom of the list.
Anime share is fine, this isn’t new drive and configuration, I have been using it for almost a year. I just decide to add those to Plex recently.There is no corruption in any file as I check all files using a script to check media info and file integrity. I would have a report for any file corruption.
I could remove the path, but that means I lost around 6,000 files that has been indexed and properly with metadata in Plex.
And that means start indexing and downloading metadata again from beginning.
I notice recently this is the trend of how we solve things in Plex, sort of sacrificing our convenience and starting all over instead of maybe Plex Inc team maybe try to improve their software…
- Missing metadata such as poster, description or background: do Plex Dance ™
- Something doesn’t work: reinstall and do from beginning.
- Plex scan can’t finish: remove the path and start from beginning.
- Plex Cloud scan slow and buffering: don’t use it, or disable some scan feature.
- Something doesn’t work quite well: either reinstall, don’t use it or
It would be nice for a change to hear that maybe Plex Inc team would improve the way they scan, because scanning local and remote NAS is quite different beast than just scanning local drives. There are many factors that could cause Slow queries, things that block file resources OR blocking the scan itself, congested network or network drive IO,
Reading from the logs, it seems that Plex just spend too much scanning files that have been scanned before and too less trying on files that could cause problem.
For example: I have Google Drive mounted also in Plex, some deep nested files are cached in delay by Google Drive File Stream. I notice that this will slow down the whole Plex scanning process. This is absurd.
Plex scanning should be smart enough to know that if a file is remote and still refreshing cache or downloading bits required for scanning, it should do something else to continue scanning other files.
Plex Cloud is indeed their product they sell for Plex Pass.
Having a NAS outside your house could be an issue(yes, yes, cloud people). Are you sure you have rights to it, like always. One hiccup on that drive might tell Plex not to continue the scan.
There is no problem with any of my NAS because I can access it with Kodi or other way from other software. And obviously I have full access right to it.
As I said NAS outside my local network or even Google Drive mounts should not be a problem as Plex Inc is selling Plex Cloud for Plex Pass.
One hiccup on that drive might tell Plex not to continue the scan.
This is absurdly stupid that in 2018 we have to accept such performance for any software. Even more so without any warning to Admin or end user.
For example, few weeks ago I just found out that Plex didn’t properly index and download metadata of 8,000 of my Movies and TV shows for various reason.
Guess where I know this? Not from Plex log, not from Plex warning or report or UI warning of sort.
I found this out from Webtools → FindMedia Tool. A friggin’ unsupported third party app.
If an app like Plex analysis or butler or media scanner failed to do something either because of user mistake such as typo in namings, or bugs, or environment like slow network/drives, I would expect you should get a report that is easily retrievable without diving into DEBUG logs.
To be honest I would start removing the folder paths to determine the hangup issue. And at the very least remove or add to bottom the ANIME folder.
Yes as I said above, eventually I might have to remove folder paths and start from beginning or just give up. that doesn’t say anything about a good solution.
