Plex Media Server on Synology DS218 NAS not showing any media after update

Plex Media Server NAS & Devices
1

Server Version#: 1.29.2.6364-7000

Plex was working fine untill I upgraded to the above version.

Now when I open Plex Media Server it says “Something Went Wrong” for all my libraries including Home.

All permissions are correct as I upgraded to DSM 7 over a year ago and it was working fine until I upgraded.

Any help would be appreciated.

2

@Wils1975

The upgrade from older versions to 1.29.2 can take quite a bit of time (database upgrading itself)

Plex/web is not the smartest tool. It can’t recognize “still busy” with “something really failed”.

In 99/100 cases, restarting the web session clears it.

If you’ rushed the NAS and stopped PMS, we might have a separate issue
but first go with (try each of these, one at a time , advancing to the next ONLY if needed)

  1. Restart Plex web
  2. Restart PMS
  3. Reinstall 1.29.2 (Use the KEEP option when uninstalling)
3

Thanks for the quick responce.

I’ve tried all 3 and its still the same.

In my browser the Server loads but it is still not showing any media.

When I open the app on my android phone it says “NO items to display”

4

Thanks.

Time to ask some basics.

  1. You’re on the same subnet as the server is? (server at: 192.168.1.199)
  2. You’re signed in to your account (in Plex/web) ?

From what I see, as I write this (15:00 EST), the server was last seen around 13:00 EST.

Does this make sense to you?

Would you please:

  1. Stop PMS

  2. Open FileStation

  3. Navigate to: PlexMediaServer/AppData/Plex Media Server

  4. Right-Click “Logs” → “Compress to Logs.zip”

  5. Download that Zip file

  6. upload here so I may see what’s happening

5

Yes, Same subet. The NAS is hard wired into the router and my laptop connects vire Wi-Fi.

I can open the Plex web app and can see that I am logged in. All my libraries are showing on the left hand side, I just can see any media or my home screen.

please see logs attached…

Logs.zip (15.5 MB)

6

Thanks for the logs. I found it immediately.

Mar 23, 2023 16:35:51.777 [0x7f6539fe50d0] ERROR - SQLITE3:0x80000001, 11, database corruption at line 65785 of [1b256d97b5]
Mar 23, 2023 16:35:51.777 [0x7f6539fe50d0] ERROR - SQLITE3:0x80000001, 11, statement aborts at 16: [INSERT INTO vacuum_db.‘metadata_items’ SELECT*FROM"main".‘metadata_items’] database disk image is malformed
Mar 23, 2023 16:35:51.871 [0x7f6539fe50d0] ERROR - SQLITE3:0x80000001, 11, statement aborts at 1: [VACUUM] database disk image is malformed
Mar 23, 2023 16:35:51.882 [0x7f6539fe50d0] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::loadOne: database disk image is malformed
Mar 23, 2023 16:35:51.974 [0x7f6539fe50d0] DEBUG - ChangestampAllocator: initialized to 5575132
Mar 23, 2023 16:35:51.980 [0x7f6539fe50d0] DEBUG - Opening 2 database sessions to library (com.plexapp.plugins.library.blobs), SQLite 3.35.5, threadsafe=1
Mar 23, 2023 16:35:51.986 [0x7f6539fe50d0] INFO - Running migrations. (EPG 0)

Did you recently suffer a power failure or have some other kind of abrupt Power OFF event for the Synology?

The database needs to be repaired or replaced with a backup.

How good are you with the Synology command line shell ?

7

Not that I’m aware of?

not too bad, I think.

I’ve done a bit linux commad line.

8

Cool,

I have a tool for you to use which will attempt to fix the errors in the DB.
If it can’t fix the ‘current’ database, you’ll be able to “Replace” the current (active) database with the newest backup database (PMS backup created during maintenance)

I recommend you look over the Readme I put there so you can familiarize yourself with it

You run it as ‘root’ user and you’ll have all the privileges necessary to control PMS and effect repairs.

If the common sequence (stop, auto. start) doesn’t fix it

then:

  1. stop
  2. replace
    – Let it search your backups for the newest available and valid DB to use.
    – It will ask “Use date_here”
    – You answer Yes/No.
    – If you say “yes”, it will make a backup of the current then copy the backup to use
    – It will then retest.
  3. auto (this is to be 100% safe)
  4. start
  5. – PMS should now be recovered (check in Plex/web browser)
  6. – Scan Files / Refresh metadata if you’ve added since the date of the backup
  7. When satisfied with the recovery, Exit
    – you can delete the temporary files.
9

Wow, I’m back up and running!!!

The repair option didn’t work but the replace option did.

My Plex is fully working again.

Thanks for such great support. 10/10

10

As followup,

How was that tool and documentation for you?

Was it clear enough to get you to the task you needed easily?

Did you have any unexpected surprises ?

11

I got there in the end but might be a bit hard for someone without command line knowledge.

The hardest part I found was getting the DBRepair.sh file on the NAS. Then finding it with Putty.

here’s what I did in Putty…

Open Putty and SSH to 192.168.1.199 (NAS IP)

Login as Admin

sudo -i

cd /

cd volume1/PlexMediaServer

./DBRepair.sh

Thanks again.

12

Cool…

Thank you.

I’ll write up a “How to use Task Scheduler” (for dummies) edition :slight_smile:

13

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