Synology Update Breaks PMS - already updated to latest version and nothing

Plex Media Server NAS & Devices
1

Server Version#: v.1.41.2.9200-c6bbc1b53 also tried beta v.1.41.3.9232-434341a9d
Player Version#: 1.105.1.257-3bc35ab9

Not sure how to get the server logs. I like everyone else updated to 7.2.2 and now my Plex is bonked. I have updated to the latest version that supports 7.2.2 and the beta. When that did not work I uninstalled and reinstalled why keep the kiles. Nothing…

It installs, but after the install. It does not start. I go and start it, and it will say manually stopped a minute later… Anything else I can try?

2

DSM 7.2.2 made some changes to the packaging requirements for Plex.

Do the following in the order given:

  1. Uninstall Plex using the first option, uninstall only! (keep all files)
  2. Reboot the NAS (Important)
  3. Go to Plex Downloads and download the package for DSM 7.2.2+
  4. Install the package you just downloaded manually in Package Center

Just remember, from now on, you need to download the latest Plex package for DSM 7.2.2+

image
image997×522 27.6 KB

If that fails, then open File Station on the NAS and navigate to PlexMediaServer/AppData/Plex Media Server and then right click on the Logs folder and select Compress to Logs.zip.

image
image777×559 19.8 KB

Attach the Logs.zip file to your post, thanks.

3

Thank you @trumpy81 I had tried all that and still nothing. But I tried it again just to be safe! Still the same thing. It starts and then manually stops seconds later.

Attached are the logs.
Logs.zip (395.4 KB)

4

Thanks.

From your logs:

Nov 28, 2024 14:33:44.688 [139652031130256] ERROR - SQLITE3:0x80000001, 1, statement aborts at 4: [SELECT `id` FROM metadata_item_settings WHERE extra_data -> 'pv:SyncedViewAt' IS NOT NULL or extra_data -> 'pv:SyncedRatedAt' IS NOT NULL] malformed JSON
Nov 28, 2024 14:33:44.688 [139652031130256] ERROR - Exception inside transaction (inside=1) (/home/runner/actions-runner/_work/plex-media-server/plex-media-server/Library/DatabaseMigrations.cpp:342): sqlite3_statement_backend::loadRS: malformed JSON
Nov 28, 2024 14:33:44.690 [139652031130256] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::loadRS: malformed JSON
Nov 28, 2024 14:33:44.690 [139652031130256] ERROR - Database corruption: sqlite3_statement_backend::loadRS: malformed JSON
Nov 28, 2024 14:33:44.690 [139652031130256] ERROR - Error: Unable to set up server: sqlite3_statement_backend::loadRS: malformed JSON (N4soci10soci_errorE)

As you can see, your database is corrupt.

Click on this link PlexDBRepair - ChuckPa and download ChuckPa’s database repair script and follow his instructions and run it on the NAS.

Fingers crossed, that should repair the database and allow you to run Plex again.

If not, then you may need to restore the earliest database backup you have.

https://support.plex.tv/articles/202485658-restore-a-database-backed-up-via-scheduled-tasks/

5

Not looking good… Still the same thing happening and the same thing in the log file. Did the DB repair and nothing. Then restored two different backups and nothing. Yet when I do a Check with ChuckPa it says all good.

Checking the PMS databases
Check complete. PMS main database is OK.
Check complete. PMS blobs database is OK.

6

That is not good at all.

Obviously, your database has been corrupt for some time, since you were unable to restore an earlier backup and continue.

The only thing you can do now, is uninstall Plex completely, using the option in red and then start over.

If all of your media files are correctly named and organised, then the rebuild should not take too long and should be relatively painless.

I wish you luck with it though. :slight_smile:

7

When I do the red option, will I have to deal with the Server. Claiming and Unclaiming… I’m thinking maybe I should just go container and see what happens.

8

You should not have to reclaim the server, since it will be a whole new server as far as Plex is concerned.

Personally, I do NOT like Docker for a number of reasons, and I personally do not see it as a viable option.

It can be useful when running other apps, but otherwise I would avoid it.

You can try it if you like, just be prepared to lose some hair in the process … lol

1 Like
9

Which version of PMS did you update from ?

I’ve only seen those messages when older DBs (Created a long time ago) were used.

PMS 1.40.0 and above are very strict about the DB.
I have seen several cases were previously-undetected errors were reported.

It is still possible to repair the DB

Alternatives at this point are:

  1. Force a repair
  2. Use one of the older backup DBs and see if the problem is isolated to pre-1.40.0 or post 1.40.0
10

Thank you @ChuckPa I wound up rebuilding and staying on the Synology Package. I will make sure to update more often moving forward to prevent this from happening again.

11

You should also backup the PlexMediaServer folder on a regular basis.

You can do that easily by opening File Station, go to PlexMediaServer/AppData and right click on the Plex Media Server folder and select Compress to Plex Media Server.zip, then store that .zip file on another machine.

You can also write a script to do that for you and then add the script to a scheduled task.

I use such a script and have it set to run every month. I store the file on my other NAS & PC.

12

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