Ran repair database script but still getting “database corrupted” notifications

General Discussions
1

Hey all, I’ve been having an issue with my Plex media server. When sorting tv shows by “most recent episode aired” half of the time it will lag out and say “an unexpected error loading library occurred”. I have to restart the sever to get it to load properly. Some basic trouble shooting I’ve done is, optimizing database, cleaning bundles, refreshing metadata and also a database repair as described online. However, when I wake up in the morning, I still get “database was found to be corrupt” notifications.

I am hoping that it is a simple fix regardless because I have spent many hours photoshopping custom artwork and maintaining collections that I would be pretty bummed if I had to start from scratch. Any help would be greatly appreciated.

2

If fixing didn’t work, restoring to an older version might be your only hope.

Good luck!

Chris

3

Hey there, I appreciate the response, friend. Unfortunately for me, the database corruption I’ve got going on is in my backed up databases as well. I forgot to mention that switching out old backups was also a trouble shooting method that I attempted already.

4

Bummer. I was hoping. But if you have to rebuild it, I’d recommend reviewing the new naming for Movies and TV. They allow you to put a metadata ID in the filename of a movie or the parent folder name of a TV Series that the new scanners use. I just finished updating all my folder/filenames and the new scanners are fast.

Chris

5

There are other databases as well.
Try repairing the one with blob in its name too.
Use the “manual” procedure, which dumps the content into an .SQL file and subsequently imports these into a completely new .db file.

If you are using the OTA live TV & DVR feature, delete the database files with epg in their file name. They will get recreated upon EPG refresh.

6

Thanks for the advice, I ran the SQLite integrity check script on the blobs database and it returned a bunch of “page ****** is never used” output. Then I ran the recover and it did it’s thing but I am still having the same issue. One thing I did notice while rooting around is that my library.db file is almost 8 gigs while the older back ups are around half the size. Any idea what could be causing that?

7

This can happen after a lot of changes have been made in the DB. During the coming nights, the server will perform databasde maintenance and reduce this again.
(Provided, the DB maintenance is not thwarted by a defective database file.)

8

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