Jump to content

Rich Minear

Members
  • Content Count

    49
  • Joined

  • Last visited

Community Reputation

7 Neutral

About Rich Minear

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So that depends on what you mean by "new/fresh". Each database that I fell back to was "known good", and had been cleaned after prior corruption. I had an earlier post where I showed how to clean a database so that it contained no corruption. But two of the times, I started over from scratching, letting Plex build it. None of the databases that I restored to had any corruption.
  2. The last 6 or 7 posts that I did about corruption all occurred within hours. None lasted a day. The diags were attached. 6.6.7 is rock solid. No corruption for weeks.
  3. Is it possible to get an idea of what has changed in the new version (6.8.0rc1) that we believe may fix the issue? I'm more than happy to try it and see...if we have something that we believe was changed to fix it. My machine can usually recreate the problem in less than a day. If its just a *hope*, then I will just wait to see what others find..... Some of us had corruption within hours or minutes....
  4. You may have to read through the previous pages. I'm pretty sure that I saw that some people were having issues even with appdata on a cache drive.
  5. There were a couple of things that I did. Usually....I did not have to do a full blown rebuild of Plex. I would have backup databases that I could fall back on. And I also found the information on how to rebuild the database without losing all of my plex data. I have a shell script that does the following: (must be done with the docker image stopped, and you have to go to the location of the Plex database files on the file system) cp com.plexapp.plugins.library.db com.plexapp.plugins.library.db.original sqlite3 com.plexapp.plugins.library.db "DROP index 'index_title_sort_naturalsort'" sqlite3 com.plexapp.plugins.library.db "DELETE from schema_migrations where version='20180501000000'" sqlite3 com.plexapp.plugins.library.db "PRAGMA integrity_check" sqlite3 com.plexapp.plugins.library.db .dump > dump.sql rm com.plexapp.plugins.library.db sqlite3 com.plexapp.plugins.library.db < dump.sql chown nobody com.plexapp.plugins.library.db chgrp users com.plexapp.plugins.library.db Occasionally when you have a database that really has issues, you will end up with a dump.sql file that has issues then also. I found that when you pull the dump.sql file back into an empty database, you will see errors, and then the db will have a zero byte file size. Those error messages will point to line numbers in the dump.sql file. You can go in with a text editor and delete those lines. And the last line in the file may be set to rollback. You have to change that also. But then you can re-import the file, and it gets your db back at least to a point where the Plex server can take over and get things back to normal. There is also a database tool built into Plex. Its under SETTINGS, TROUBLESHOOTING. There is a button that says "Optimize Database" When I was having the corruption, I would run that shell script (If i didn't have a backup to fall back on), bring Plex back up. I would let it catch up with any new TV shows or Movies that it found on the disk that might not have been in the database. And then I would run that Optimize action. Once it was done....I would stop Plex, and make a "known good" backup of the database (copying it a the shell level) so I had a place to start again if it failed. The script would also work on Sonarr (or Radarr). It just has to be tweaked to run for it's database instead of Plex. You can lose the first three lines that are specific to the Plex DB schema. Since I have been back on 6.6.7, and have a clean database....I have had ZERO corruption: no matter how busy my Plex and Sonarr get. I know it is a hard thing to troubleshoot, and they are working to find it...but it is something to do with the later versions of Unraid, or the utilities that it contains. 6.6.7 is rock solid, not matter what version of Plex and Sonarr I am running.
  6. I had a week of much-needed vacation, and my dockers/db's were rock solid on 6.6.7 while I was gone. Has there been any movement on this? Any new ideas or changes in code?
  7. I just spent two hours fixing databases on my system, after downgrading to 6.6.7. I want to help...but I can't keep rebuilding all the time. And I'm heading out on vacation...I need it to be solid.
  8. Good morning. So I fixed the corrupt databases last night right after I posted, and then went to bed. There was no corruption when I turned off my computer (not the NAS...obviously). Within an hour, there was corruption in my plex database. Unless someone has something meaningful to try based on my diagnostics, I'm going back to 6.6.7 tonight. The entire system was stable for almost a MONTH after going back....and it corrupted in the first day when trying this new release candidate.
  9. So it doesn't appear that 6.7.3-rc4 is the answer. 😞 Second day of corruption...less than 24 hours. Both Plex and Sonarr. Here are the diags. Is there something else we should be doing?? swissarmy-diagnostics-20190925-0313.zip
  10. I do not have a cache drive. I have seen the corruption issues for a couple of months, and originally started the former thread about having to downgrade to 6.6.7 because of the corruption in the databases for Plex and Sonarr.
  11. And plex corrupted 30 minutes late. 😞
  12. I found my first corruption today with 6.7.3-rc4. Sonarr had its DB corrupt after one day. Diags attached. swissarmy-diagnostics-20190924-0210.zip
  13. The Plex logs would show if you had a db problem. You would see lines that show "malformed" db entries and lines.
  14. I bit the bullet and upgraded again from 6.6.7 (Stable as a rock for three weeks!) to 6.7.3-rc4. I am kicking off some updates, downloads with Sonarr and seeing what happens..... 🤞