Unexpected error only under certain views

Server Version#: 1.18.7.2306
Player Version#: Web 4.22.1
Synology DS218+

OK, This is odd and is perhaps just a corrupt database, but it’s not behaving as I’d expect a corrupt database to behave. This is also occurring on every device I’ve used to view it. (Web, iOS, AppleTV, Roku)

I have three libraries (Movies, TV Shows, Music).
-All of them show up as Unavailable on the Home screen, both On Deck and Recently Added)
-Movies: Library view gives “There was an unexpected error loading this library”, Recommended, Collections and Playlists show up just fine, and I can start and watch movies from them. Recommended displays the Recently Added list that doesn’t show up on the Home screen.
-TV Shows: Recommended gives “There was an unexpected error loading this library”, Library view show up just fine. This is the exact opposite from Movies.
-Music: Just like TV Shows, Recommended gives “There was an unexpected error loading this library”, Library view & Playlists show up just fine.

Plex Media Server Logs_2020-02-09_11-20-01.zip (6.1 MB)

Whether or not it is causing this issue (it almost certainly is), you definitely have a corrupt database:

Feb 08, 2020 20:04:10.820 [0x7fdafa88f700] ERROR - SQLITE3:(nil), 11, database corruption at line 64817 of [bf8c1b2b7a]
Feb 08, 2020 20:04:10.900 [0x7fdb1fd11700] ERROR - SQLITE3:(nil), 11, database corruption at line 64817 of [bf8c1b2b7a]
Feb 08, 2020 20:04:10.979 [0x7fdb1f447700] ERROR - SQLITE3:(nil), 11, database corruption at line 64817 of [bf8c1b2b7a]
Feb 08, 2020 20:04:11.059 [0x7fdb1dfc5700] ERROR - SQLITE3:(nil), 11, database corruption at line 64817 of [bf8c1b2b7a]

Your log is full of these. You can try the following procedure to repair it:

Or, if necessary, restore a backup:

[Edit]
@ChuckPa’s linked instructions below for how to restore a backed up DB on a Synology NAS would probably be a better place to start, being more specific to the environment.

1 Like

On Synology, you can repair a corrupt database with the GUI. FAQ 17.

Synology FAQ - Questions, Answers, and a few How-To's

2 Likes

That worked. Thank you. I figured that was the case. It just seemed to be behaving differently than I would have expected a corrupted database to behave, so wanted to be sure.

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