Server Version#: any version
Player Version#: any version
I always got this after I restart the server, and I have few millions of photos, this is getting me frustrated!!!
please let me know is there anything i can do to resolve this? by manual manipulating the database perhaps? i have basic knowledge to work with SQL, but I cant find teh relationship in the database that cause some media item getting this error!
It’s not an error message.
This comes always up when a library scan sees a file which has been in the library before.
i.e. a sign of totally regular operation
no i dont think so, the normal case should be if the media had been added before, it skip that directory if no file change detected!
the process to skip the whole directory of 100 files, is obviously much much faster than scanning 100 files again one by one! for me something is definitely wrong.
and this no happen in all my directory, but about 20% of all my directory required to rescan all files 1 by 1 just to reuse the media items.
bump!
Your second image is correct when a change is not seen. However, the messages in the first image is correct when a change has been seen and so PMS is double checking if the file is the same or not.
As OttoKerner said, that is not an error but a valid message. I can’t tell from what you’ve posted why PMS thought those files changed.
well, i am very sure that these folders have no change.
i have about 2 million photo and each time Plex will try to run through the whole 2 millions photo and it need to re add about 400k of then… which obviously the file is same old file since years ago.
i forgot to mention, always those same files get readded.
I’m going to need to see the log at the start of those scans.
it show something like this before scan start
*File '/volume2/downloads/media/A Set Collection Pack/IMG_6597.JPG' didn't exist, can't skip.*
then it start to re-add every single photo inside that folder, even though only 1 photo was deleted despite that the folder have few hundreds photos.
I was expecting that Plex should just delete that file in databse that doesnt exist rather than need to recheck the complete folder again. and my collection is mounted remotely so it take really long time to check again the whole collection. normally take weeks to run through.
and if i stop the scan, the next run i will have to go through the whole checking again, it seems plex did not commit the scan record when user stop the scan process manually.
I am not sure how Plex work, but i suggest that perhaps Plex can consider:
provide an option for user to Quick Scan (quickly scan new and deleted items), and a Full Scan (current method where there is a file deleted, it re-scan the complete directory for any file changes)
Plex Media Server should commit the scan record for deleted items immediately even if user interrupt the scan manually, other use the next scan will re-start again.
this suggestion being that media file do not get changed/edit/updated frequently, it usually only get added or deleted, so the purpose of checking and confirming updated metadata seems not essential for most user.
Via what mechanism? Some remote mount protocols don’t preserve accurate timestamps, or return partial information if a request times out.
Things like rclone can be weird with some backends, problems like no modification timestamps for folders, etc.
Re: didn't exist, can't skip -
Do these files have individual duplicates in the Library, or are there two paths in the Library that include the same files twice?
That’s by design. If you don’t want that, use the option to do a partial scan when file changes are detected. These 2 settings.
Are you using a cloud provider like Google Drive? There have been reports from users where cloud providers can at times not respond so the mount will appear as if files are missing/inaccessible. Depending on exactly what is accessible, PMS may think files are missing and end up removing them.
Plex does not support media saved remotely. If you do this, YMMV.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
