Updated DSM, Having Some Issues

Plex Server Version#:1.29.2.6364-7000
Synology Version#:7.1.1-42962

So, I updated my Synology to DSM 7, then updated Plex to the latest version, but now I have two listings of “SERVER” on my menu. One works, but I had to reinstall the libraries and lost all customizations, and the other one says “SERVER is currently unavailable”

I’d love to be able to repair the working installation so I have all the posters, collections, etc that I spent so much time personalizing.

I do see the option to simply REMOVE the non-working version.

I’ve attached my log files.
Plex Media Server Logs_2024-08-31_15-04-22.zip (5.0 MB)

The upgrade to DSM 7 includes a number of severe changes to the platform by Synology. There’s a dedicated guide on how to upgrade/migrate an existing Plex Media Server setup after upgrading to DSM 7.

1 Like

You updated from DSM 6 to DSM 7, correct?

Do you still have the /Plex shared folder?

Are the database files still in /Plex/Library/Application Support/Plex Media Server/Plug-in Support/Databases?

If yes to all three, see Struggling with migration from DSM 6 to DSM7 - #2 by FordGuy61

There are 13 .DB files in the databases files. 2 with todays date, and the rest with various dates from the past

Completely read the post I linked.

After reading, follow the steps.

Pay attention to each step, especially when setting permissions is required.

Write back if you’ve any questions or something goes amiss.

Hi, thanks for that detailed tutorial. I went through it and everything seemingly went exactly as you described. It did take awhile, but it finally finished and Plex is indeed installed. And there is only a migration file in the Plex folder. But…

When I run Plex, it only runs for about 20-25 seconds before stopping on it’s own. During that time, I can hear the server really churning away. Also, during that time, Plex won’t load in a browser using the IP address.

I zipped the logs and include them here.
Plex Media Server.1.zip (148.4 KB)

Good: The migration worked.
Bad: Synology won’t update the PMS version in Package Center and I did not ask which version you were running when on DSM 6.

Download and install the current public (1.40.5) or beta release (1.41.0) of Plex Media Server.

Based on the error messages in the log files, it looks like you were running a 1.40+ release prior to updating to DSM 7. Due to Plex database changes, it is not possible to go from 1.40 to releases earlier than 1.31.2.

PMS 1.29.2 sees the db changes as errors and then shuts down.

Installing a current release should resolve the problem.

You may see a “503 maintenance” message in Plex Web when PMS first start. If so, that is PMS performing database maintenance. Check back every 5 - 10 minutes to see if it has finished. You’ll need to refresh the web browser, the page does not auto-update. If the maintenance process is still running, do not interrupt it. It will just start over the next time you start PMS.


Sep 01, 2024 12:16:40.899 [0x7f12dd42f0d0] ERROR - SQLITE3:0x80000001, 1, near ">>": syntax error in "UPDATE tags SET extra_data = extra_data ->> 'url' WHERE extra_data IS NOT NULL and json_valid(extra_data)"
Sep 01, 2024 12:16:40.899 [0x7f12dd42f0d0] ERROR - Exception inside transaction (inside=1) (/data/jenkins/server/3537899744/Library/DatabaseMigrations.cpp:289): sqlite3_statement_backend::prepare: near ">>": syntax error for SQL: UPDATE tags SET extra_data = extra_data ->> 'url' WHERE extra_data IS NOT NULL and json_valid(extra_data)
Sep 01, 2024 12:16:40.903 [0x7f12dd42f0d0] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::prepare: near ">>": syntax error for SQL: UPDATE tags SET extra_data = extra_data ->> 'url' WHERE extra_data IS NOT NULL and json_valid(extra_data)

You’re right about my Plex version. In fact, I had just upgraded it a few days before this and did see that 503 Maintenance error for a little while.

After a bit of a struggling determining which package to download, I have the new one installed and it’s all there! Thanks so much!

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