![]() Once the container is up, it scans my media library and populates it with data such as metadata, posters, watch state, ratings, etc. Could it be one of my media files? Could it be Unraid? Could it be my hard drive?įor context, if unfamiliar with Plex. The question I have then is what if anything can I do to try and fix this or learn about the cause? I would have thought a completely new database would fix my issue, unless it's purely coincidence two back to back databases became corrupted before I could even touch them, with no connection. Upon viewing a table called media_items I get the same error.Ĭlearly one of what I assume to be main tables is corrupt. ![]() I decided to copy the database onto my windows machine and poke around the database to get a better understanding of the structure. ![]() Sqlite3_statement_backend::loadOne:database disk image is malformed The errors I am receieving have changed but as of the last situation (complete wipe and reinstall of a new container) I am getting the following error in the output log: At best I get it up for a few minutes before the container fails again. My Plex container has been failing time and time again on Unraid resulting in me doing integrity checks, rebuilds, dump, import, and a complete wipe and restart (completely remove old directory and start over). ![]() I have posted in both Unraid, and Plex forums with no luck. I am not sure where a question like this really falls as it is from an Unraid Linux server, with a Plex Media Server container, which utilizes SQLite (looking for troubleshooting at the root level).
0 Comments
Leave a Reply. |