Freetic unexpected library rescan and playlist issues

Plex Media Server
,
1

Server Version#: Version 1.41.5.9522
Player Version#: Plex Web Version 4.145.1

Hello,

I’m currently experiencing an issue with my Plex server. It has started rescanning my entire library, and I’m not sure why.

Background:

  • Server Setup: My Plex server library is mounted using rclone.
  • Recent Changes: I made minor adjustments to the mount point and tweaked the Plex server configuration.

Issue:

  • Unexpected Rescan: The server suddenly started rescanning the entire library, beginning from “M” and moving backward through the alphabet. It is currently at “J.”
  • Potential Data Loss: It appears that parts of my library may have been deleted before rescan, leading to partial loss of playlists that I have been building for years.

Concerns:

  • Playlist Recovery: I am worried about the loss of my playlists and am looking for a way to recover or find a backup of them.

Questions:

  1. Has anyone experienced a similar issue with Plex rescanning the library unexpectedly?
  2. Is there a way to recover or find a backup of my playlists?

Additional Information:

  • The rescan has helped identify duplicates, but the potential data loss is concerning.

Request for Help:

  • Any insights or suggestions on how to address this issue would be greatly appreciated.

Thanks in advance for your help!

2

If you did this while Plex server was still running, then you probably also have “Automatic library updates” enabled. Or maybe a periodic library scan happened to overlap with your activity.
In any case that is pretty much your fault.

See https://support.plex.tv/articles/202485658-restore-a-database-backed-up-via-scheduled-tasks/ on how to go back to a version of your server database before the incident.

If your media are not stored inside your server machine, never enable " Empty trash automatically after every scan" in the server preferences.

3

Thank you @OttoKerner for your answer.

I am aware that the issue is likely due to my actions.

I am considering running the DBRepair reindex command, as I mentioned in this forum post:

Perhaps this could also address another issue I am experiencing.

Before proceeding, I would like to know if it is safe to stop the server to restore a backup. Will this have any adverse effects?

Thank you in advance for your help.

Best regards,

4

You can’t perform the restore action without stopping the server. As long as it is running, it has a file lock on the database.

How to stop the server in an orderly fashion with Docker, I cannot tell you. I’m sure there is a command line for that. But I don’t know that as I’m a Windows guy.

5

Hi,

I was able to restore the backup without any issues. Thank you for your help.

The more I think about it, the more I believe that running the reindex with DBRepair could explain the frenetic update activity.

Best regards,

6

I’m not sure I follow.
The script cannot be the reason for the original issue above.

7

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