Server Version#:Version 1.42.1
Player Version#:4.149.0
Really tired of having to rebuild my database every time I do an update. Takes me three days to rebuild the metadata correctly each time. Casting support works differently on ios app (only sees fire TV devices) vs web app (only sees Chromecast devices). Beginning to get tiring managing a PMS server and apps.
I have PMS running on QNAP nas. I try not to update it often as its a ball ache to rebuild. I had to bite the bullet this weekend. Still in rebuild hell.
I have Plex clients on laptop, ipads and iphones, firestick enabled TVs.
I cast audio to chromecast enabled DENON RCD. This stopped working so bit the bullet.
Usual SQLlite - SQLITE3:0x80000001, 11, database corruption at line xxx, repeats three times.
Trying to start UI - Plex Media Server is currently running database migrations.
Yeah, except its not. The database is corrupt as per the SQLLite errors and it just sits there reporting “Plex Media Server is currently running database migrations.”. Hence rebuilding again. Second time this year. Not funny anymore.
You can have Plex Media Server send notifications to the Plex mobile app for many events, including when database corruption is detected.
Plex Media Server: Settings → server_name → General, enable Push Notifications.
Plex mobile app (Android, iOS should be same/similar): Settings → Notifications. At the bottom is the Plex Media Server section. There are notifications for New Devices, Database Corruption Detected, and Database Backed Up.
Think about getting a decent UPS unit for your NAS.
If you remember even a single instance where your NAS unit suddenly lost power (for whatever reason and no matter how briefly) you should seriously consider it.
Sudden loss of power can very much lead to database corruption.
It can also damage hard drives physically. No joke.
The same goes for running out of space on the storage volume where the Plex data folder is stored. Never let that happen, or database corruption is very likely to occur.