Plex not working after update 1.18 > 1.28 on DSM 6.24

Plex Media Server NAS & Devices
1

Server Version#:
1.28

Hi,

I made a manual install (as synology DSM 6.2.4 plex package told me) from 1.18 to the newest version.

Now plex server is not starting anymore.

How do I proceed?

This is the log:

*****/volume1/Plex/Library/Application Support/Plex Media Server**$ tail -n 2222 Logs/Plex\ Media\ Server.log

Aug 11, 2022 00:27:20.688 [0x7f80d42f5b38] INFO - Plex Media Server v1.28.0.5999-97678ded3 - Synology DS1815+ x86_64 - build: linux-x86_64 synology - GMT 02:00

Aug 11, 2022 00:27:20.688 [0x7f80d42f5b38] INFO - Linux version: DSM 6.2.4.25556-2, language: en-US

Aug 11, 2022 00:27:20.688 [0x7f80d42f5b38] INFO - Processor: 4-core Intel(R) Atom(TM) CPU C2538 @ 2.40GHz

Aug 11, 2022 00:27:20.688 [0x7f80d42f5b38] INFO - Compiler is - Clang 11.0.1 ([https://plex.tv](https://plex.tv/) 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)

Aug 11, 2022 00:27:20.688 [0x7f80d42f5b38] INFO - /var/packages/Plex Media Server/target/Plex Media Server

Aug 11, 2022 00:27:20.692 [0x7f80d8c91380] INFO - SQLITE3:0x80000001, 283, recovered 172 frames from WAL file /volume1/Plex/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-wal

Aug 11, 2022 00:27:20.794 [0x7f80d8c91380] INFO - Running migrations. (EPG 0)

Aug 11, 2022 00:27:20.799 [0x7f80d8c91380] INFO - Running forward migration 20201103130000.

Aug 11, 2022 00:27:20.960 [0x7f80d8c91380] ERROR - SQLITE3:0x80000001, 11, database corruption at line 83344 of [1b256d97b5]

Aug 11, 2022 00:27:20.960 [0x7f80d8c91380] ERROR - SQLITE3:0x80000001, 11, statement aborts at 10: [SELECT media_item_id, media_streams.extra_data FROM media_streams join media_items on [media_items.id](http://media_items.id/)=media_streams.media_item_id where media_streams.extra_data like '%colorTrc%' and me

Aug 11, 2022 00:27:20.961 [0x7f80d8c91380] ERROR - Exception inside transaction (inside=1) (/data/jenkins/server/3534688490/Library/DatabaseMigrations.cpp:295): sqlite3_statement_backend::loadRS: database disk image is malformed

Aug 11, 2022 00:27:20.965 [0x7f80d8c91380] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::loadRS: database disk image is malformed

Aug 11, 2022 00:27:20.999 [0x7f80d8c91380] ERROR - SQLITE3:0x80000001, 1, no such table: activities in "update activities set finished_at=started_at where finished_at is null"

Aug 11, 2022 00:27:21.000 [0x7f80d8c91380] ERROR - Database corruption: sqlite3_statement_backend::prepare: no such table: activities for SQL: update activities set finished_at=started_at where finished_at is null

Aug 11, 2022 00:27:21.000 [0x7f80d8c91380] ERROR - Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: activities for SQL: update activities set finished_at=started_at where finished_at is null (N4soci10soci_errorE)
2

Based on the errors in your logs, the database has been corrupted. That’s not necessarily linked to upgrading your server but can happen if you shut down the NAS while the database is still trying to write some updates.

https://support.plex.tv/articles/repair-a-corrupted-database/

There’s a dedicated guide on how to do this for DSM7 – though that won’t apply to your DSM6 setup!

3

Thanks, repair worked.
The update process corrupted the database. The updater did not stop the server first. One could say, yes you should stop the server first. But why should the user know these things? I assume that the package is coming from plex. If so, just include a line that shuts down the server first. It´s so easy!

4

Incorrect, typically the database has preexisting corruption that is discovered during the upgrade. The other cause is getting impatient post upgrade, not giving the server enough time to run the needed database upgrade steps, and either restarting or closing plex.

5

Whatever. It might be that the last system failure plus forced shutdown caused the corruption. But the funny thing is, that plex worked fine after reboot for hours until I decided to do the updated.

6

Correct, plex can function with database corruption, but because of how upgrades frequently modify the database structure the damage results in failed upgrades.

7

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