You used the AUTO option, correct?
What was the output? Did it say the database was OK?
Before you go nuclear, post a set of log files.
Hi
I’ll give it another try. The time I look into if I have to start all over is beyond my horisont. So another look into the log files may be worthwhile.
My latest log files after a DBRepair are attached.
Logs.zip (3.3 MB)
Thank you for the logs.
Someone / Something changed the permissions of the PlexMediaServer shared folder.
Jan 13, 2026 20:41:16.659 [140555923278480] DEBUG - Opening 20 database sessions to library (com.plexapp.plugins.library), SQLite 3.39.4, threadsafe=1
Jan 13, 2026 20:41:16.659 [140555923278480] ERROR - SQLITE3:0x80000001, 14, cannot open file at line 41714 of [a29f994989]
Jan 13, 2026 20:41:16.659 [140555923278480] ERROR - SQLITE3:0x80000001, 14, os_unix.c:41714: (13) open(/volume1/PlexMediaServer/AppData/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db) - Permission denied
Jan 13, 2026 20:41:16.659 [140555923278480] ERROR - Promise destroyed without handling exception: Promise fell out of scope without resolving or rejecting
This is preventing PMS from opening its files and databases.
Local Users to System Internal UsersPlexMediaServer has R/WNow you must fix the files themselves. This will be messy
If you’re using a third-party program AND having it put media in the PlexMediaServer shared folder then STOP doing that. It will break the PlexMediaServer shared folder. You must move your media storage to a separate shared folder which PMS can read.
Hi
According to my insight Permissions should be set properly. See attached picture: System Internal Users (1), PlexMediaServer (2) and Read/Write (3).
But I guess U pointed out my wrongdoing. I think I might be guilty in copying files into the Shared Folder while Plex was scanning the Folders.
Does that mean I corrupted the database all together or am I able to save it by putting a lot of work into sorting out the mess I made?
You write I must fix the files themselves and it will be messy and point out a link a FAQ. Does the link show how to do that? Or do you think it will less time consuming starting all over again setting up my Plex Server from scratch?
Copying which folders ? What did you copy into PlexMediaServer ?
You shouldn’t be touching anything in the PlexMediaServer shared folder except to get Logs.
DSM 7 is very fragile. PlexMediaServer has no ability to fix itself (they took that away from us in DSM 7).
Now you wil need to confirm.
Hi
Sorry, for my misunderstanding. I thought you meant copying files into a movie folder. That was what I did while Plex was scanning the movie folder. I haven’t copied anything into the PlexMediaServer Folder. My mistake in writing it that way. The only file I copied into the folder was “DBRepair.sh”.
I will try to follow the instructions i FAQ32.
Thank you for your kind and patient support. It means the world to me to have such good support.
Copying DBRepair.sh into PlexMediaServer (at the top, above AppData) is safe to do. I recommend it this way so it’s easy to keep track of.
In FAQ 32, I give you the screenshot of how to setup the Scheduled Task (so it runs as root user (critical).
The body (the shell commands) are a simple COPY/PASTE from the FAQ into the DSM page. No editing required.
When it sends you the notification email that it’s successfully completed, you can restart Plex.
Hi again
What is the duration of the process in FAQ 32?
I haven’t received an email yet and the proces in Task Scheduler started approx. 14 hours ago.
The duration depends on the number of folders and files in the Plex Data Folder, but it should be much faster than 14 hours.
I’ve a DS918+. The task runs in 15 minutes. The PlexMediaServer folder is 155 GB / 146757 files / 82500 folders (In Synology File Station, right click on the PlexMediaServer shared folder and choose Properties).
Use Synology Resource Manager to see if the processes are still running. Expand DSM Desktop and look for bash, chown, and find. If they are listed, then the task is still running (or another user defined task using the same commands).
Here is the task running on my DS918+:
The Synology must be configured to send notifications when a task completes.
To test if e-mail notifications are working, create a simple test task. Set it up the same way as FAQ32, but use the following for the user defined script:
#!/bin/sh
echo "$(date) this is a test"
Run the task and you should receive an e-mail similar to this:
Task Scheduler has completed a scheduled task.
Task: test message
Start time: Fri, 16 Jan 2026 13:02:41 -0600
Stop time: Fri, 16 Jan 2026 13:02:42 -0600
Current status: 0 (Normal)
Standard output/error:
Fri Jan 16 13:02:41 CST 2026 this is a test
Hi
Latest update on my apparently never ending hickups.
I suppose I managed to run DBRepair.
I restarted the Plex. When I open Plex I login. But shortly thereafter I receive the same error when I try to open Plex. Plex closes almost right away.
I attached the log files and hope and cross my fingers some of you can decipher it and point me towards a solution.
I’m pretty close to the the extent of my abilities.
Logs.zip (3.4 MB)
Thanks for the log files.
The database errors no longer appear in the log files. I do not see anything that looks like permission errors.
But PMS still stops ~20 seconds after it is started.Try this:
Go back to the public release, 1.42.2. The beta release, 1.43.0, has an updated transcoder, and Plex is still working out the kinks.
Synology does not permit direct downgrades. You will have to uninstall 1.43.0 first, then install 1.42.2. When you uninstall Plex, choose the “Uninstall Only” option.
You’ll want the DSM 7.2.2+, Intel/AMD 64-bit version (plex.tv download page, direct link)
Do not login to Plex after installing and running the public release.
Do not try to access the server using any client.
After starting Plex, you logged in ~10 seconds later. Plex then crashes while sending images (posters, etc.) to the client. Unknown if crash is due to login or if it would have crashed anyway. So, don’t login and see if Plex still runs.
After three minutes, check Package Center to see if Plex is still running.
This gives Plex time to fully start and log the startup sequence.
If Plex is still running, try to login.
If Plex has stopped already, or if it stops when you try to login, pull and post a new set of log files.
Hi
Thank you for assisting. After doing as suggested the Plex Media Server sadly stopped.
I did the following:
Everything seemed to been running.
But as soon as I clicked on the Movie section the Plex Media Server stopped.
The latest log files are attached
Logs.zip (3.4 MB)
Do you use Collections?
If so, I recommend downloading and running DBRepair 1.14.00
I just released an update which addresses previously unknown DB problems.
Hi ChuckPa
Yes, I use collections.
I downloaded your updated DBRepair-file.
I managed to execute it. Thanks to all the support I have had in here (you included)
In the terminal windows I got some errors when I ran the script. Some what like “FTS Indexes are damaged”. I have attached a part of the message from the terminal windows. I got the complete error message and can post it if needed.
Likewise I attached the newly log-files.
Logs.zip (3.5 MB)
Part_of_DBRepair-script-Error-message_in_Terminal Window.txt (887 Bytes)
Any Suggestions?
The FTS Indexes error is fairly normal. The Auto routine should have corrected those, but if not, you can run the Auto routine again.
The reason for the server stopping seems to be related to file permissions.
Open File Station and right click on the PlexMediaServer folder and select Properties.
On the Permission tab, highlight PlexMediaServer and click on Edit.
Make sure all permissions are granted and click on Done.
Make sure you enable Apply to this folder, sub-folders and files Important! and then click on Save.
The process will take quite some time to complete, so be patient.
After that, you should’nt have any issues, fingers crossed.
Hi there
Thank you for your effort.
Changed permissions
Tried again. Sadly no luck.
Then I ran a new DBRepair-script.
I’ve attached the new logfile to this message.
There appears to be errors in line 46 to 49.
It is a FTS Check.
If it these errors that corrupts the database I don’t know how to repair it.
Any suggestions?
Logfile20260209.txt (9.3 KB)
The DBRepair log file looks good. It fixed the FTS problems. Notice the log entries for the last run all say PASS.
Plex is crashing when accessing the Phototranscoder cache directory. Plex creates these files when someone browses a library. It is the scaled versions of posters and other artwork sent to the client.
Try deleting the contents of the directory. Plex will re-create them as needed.
/PlexMediaServer/AppData/Plex Media Server/Cache/PhotoTranscoder.00, 8d, ff, etc.This may not fix the problem. It will not hurt anything to try.
If Plex crashes again, then please pull and post a new set of log files.
Hi again
I’ve deleted the content of the Photetranscoder cache folder.
Ran Plex. Shortly after Plex stopped or crashed again.
The new logfile are attached.
Errors begins at line 45 and ends at 48.
The first line of error says: “FTS Check: fts4_metadata_titles - FAIL (Error: stepping, database disk image is malformed (11))“
Kind regards
Logfile20260213at10200.txt (11.2 KB)
I should have been clearer in my last post.
Please upload a set of server log files that capture the crash.
The database is fine. The DBRepair log shows no errors for the last run.
