0 Seasons listed on bottom - first time noticing this

Plex Media Server Plex Pass Betas
1

Hey I don’t know if this is just happening on my install but I’m getting “0 Seasons” listed under every tv show, even though I have more than one season for each show listed. I have a separate server for my mom setup and we both are running the same Plex Server Beta’s and her tv shows have the correct number of tv seasons properly showing. My server on the other hand is showing 0 Seasons for every TV library. This a bug? *I mean, it HAS to be a bug cuz I wouldn’t have noticed otherwise lol - I never had issues until this latest beta.

cb3al4ep9zll.jpeg635×536 393 KB

2

Same server version, works fine for me with the online version of Plex Web

3
  1. activate debug logging (not ‘verbose’!)
  2. quit Plex Server
  3. wait 1 minute
  4. start Plex Server
  5. wait 5 minutes
  6. fetch log files and attach them here

Or inspect them yourself. Take a look at the Plex Media Server.log file and seek for messages about database corrupt or malformed.
If you find these, you may have to repair your database.
https://support.plex.tv/hc/en-us/articles/201100678-Repair-a-Corrupt-Database

4

This is what I found. After I saved the logs, I followed the database repair procedure and now the Server app won’t open. I have had to repair my database before but on a previous install on this same machine so I know I followed correctly. What I don’t know is how to go about fixing the repair process to fix what’s wrong in my server database. The original com.plexapp.plugins.library.db file was 1.73GB but the newly repaired com.plexapp.plugins.library.db file says 33kb. I haven’t tried using another backed up database so I’ll report back in a few.

Feb 10, 2018 13:40:57.502 [0x70000834e000] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: database disk image is malformed

Feb 10, 2018 13:42:29.926 [0x7000074fa000] ERROR - SQLITE3:0x7000075ff640, 11, statement aborts at 1072: [analyze] database disk image is malformed

Feb 10, 2018 13:42:29.926 [0x7000074fa000] ERROR - SQLITE3:0x7000075ff640, 11, database corruption at line 79160 of [fc49f556e4]

Feb 10, 2018 13:42:45.716 [0x700007912000] ERROR - SQLITE3:0x7000075ff640, 11, database corruption at line 73878 of [fc49f556e4]

5

If the repaired file is only 33KB, then the database file was beyond repair-ability.
Try with one of the older backup snapshots.
https://support.plex.tv/articles/202485658-restore-a-database-backed-up-via-scheduled-tasks/

6

I’m going to just rebuild my library from the bottom up. I’ve done a lot of file testing and edits with file names with this server and can see this being my fault more than Plex right now. With me constantly changing Library names and trying to organizing it to my liking, I neglected to see the backend issues that would cause the database to not properly balance itself. Thanks for your assistance.

7

Make sure to solve the issue at the root: by using proper naming and folder organisation.

And never, ever move your Plex data folder to a network share. Or you’ll face the same issue again very soon.

8

Question:

If I had a premium music library in the latest database (Jan 2018) and don’t have it saved in my new database or last working database - but kept the metadata folder, would the scanner STILL download again the same data or will it use the metadata already saved prior?

9

No, if you blow away your database file, all the other files in the metadata folder are useless.

10

That’s what I wanted to know. Thanks again.