Playlists empty and continuously corrupted database

Server Version#:1.41.9.9961-46083195d
Player Version#:

investigating lost playlists and rebuilding collection on multiple occasions.

Maybe unrelated but I am getting these errors

Aug 29, 2025 03:02:03.518 [13672] ERROR - [Req#89146b/Transcode/16749245-488f-422d-a547-490c967a28db/ab69328c-7a24-45b2-b719-149129857dea] Error while decoding stream #0:1: Invalid data found when processing input

I cant find any log entries related to rebuilding the db but here is a screenshot of the db files

the server runs on a SSD. SMART shows no errors in HDTune, the device runs fine.\

Db files from a couple weeks back

I am a developer, and had no luck repairing with sqlite tools. i would like to find source of issue. need advice.

Was this sqlite3.exe in the folder screenshot copied from the plex server program folder?

Is this database folder located in the very same machine where Plex server is running?

Is there an anti virus running which is allowed to interfere in the plex data folder?

Is the plex server machine part of an active directory with roaming user profiles?

Are the media files stored on storage volumes inside the server machine?
If not, is “Empty trash automatically after every scan” still activated in the plex server settings?

Was this sqlite3.exe in the folder screenshot copied from the plex server program folder?

i copied it there, its a backup dir i used in restore attempt

Is this database folder located in the very same machine where Plex server is running?

Yes

Is there an anti virus running which is allowed to interfere in the plex data folder?

only Malwarebytes

Is the plex server machine part of an active directory with roaming user profiles?

No, but the music libraries are on a NAS

Are the media files stored on storage volumes inside the server machine?

on a NAS with network drive to the server
If not, is “Empty trash automatically after every scan” still activated in the plex server settings?

Yes it is

That is very likely the reason for your empty playlists.

A network connection is not as speedy as local file access. If you also allow the NAS to spin down the platters of the HDDs, it can take sometimes too long to spin them back up. That can be long enough for Plex server to consider (some) media files as deleted if they are not returned timely enough when accessed. With that checkbox active, they get ousted from the database immediately. Even if the media files are later re-added by an automatic/periodic library scan, they remain absent from the playlists.

Try (at least for a time) to restrict any real-time anti virus guard from interfering and potentially locking files in the plex data folder. This can be a potential reason for database corruption.
Other typical reasons would be

  1. plex data folder on a network share,
  2. not enough free storage space on the volume which houses the plex data folder,
  3. sudden power loss or hard resets of the server machine

thx for the recs

originally Empty trash automatically after every scan was unchecked but i checked it after experiencing this corruption issue. i unchecked it.

i excluded the servers %appdata% dir from malwarebytes

sometimes after a reboot my network drives dont always reconnect without manually browsing the folders first, this only happened once that i know of- i dont think it is the cause.

plex data dir is not on a network drive its local to the server host (laptop). only the media is on NAS.

Server resources are good.

no sudden power loss.

This doesn’t imply a database corruption, rather it implies that there is an issue with the media. If you think you have database corruption have you tried ChuckPa’s tool? GitHub - ChuckPa/DBRepair: Database repair utility for Plex Media Server databases

I wasnt sure what that error was related.

I ran the tool, no playlists were restored but we will see if new playlists persist

Understood, but make sure the empty after scan option is disabled.

Yes its unchecked, thank you for the support.

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