Thanks.
To All in this Thread:
Is everything here solved ?
I am looking forward to when I can complete the program Iām writing which will do detailed analysis of a PMS database.
Itās going to take me a few months, at minimum, to complete the task because Plex doesnāt have them documented. I will need to create controlled test cases and then deduce by manual physical inspection of the data records.
Itās a labor of love in the extreme but I will get there.
Sounds good. Feel free to reach out if I am able to help. I will keep records of both databases
Same issue as of 2 days ago. Tried all the DB repair tools. Donāt have an available backup DB. Not looking forward to having to rebuild Plex. My Nvidia Shield client works fine, but friends & family (and my web access) all have this error message now.
I had this identical issue a couple of weeks ago; I use an LXC on Proxmox for the Plex container. I had to roll back a backup from June ultimately, and the issue has gone away for now, however Iām wondering when it will come back.
It looked like my PMS had done an update in the recent weeks; so for now Iāve blocked my script which auto checks and installs updates and the issue hasnāt come back.
Iāve tried rolling back to versions of the LSIO container from months ago but whatever is causing this seems to have damaged my DB. I fear I may be SOL since I donāt have any usable DB backups. Might be time to run Emby side-by-side.
I have also disabled updates. Iāll make sure to do database backups and system images before I perform updates, until they find out what the db issue is.
