If this is occurring frequently on your browser then it’s time to find a new CPU (not NAS) to run PMS on. The problem is PMS isn’t responding fast enough to keep the browser from going into “Timeout” status (“something went wrong”)
The browser thinks the server should have responded by now but since it hasn’t … “something went wrong”.
Your two choices are:
Upgrade the Syno – Expensive + a DSM 7 conversion (lots of steps)
Use another computer (dedicated) to run PMS which pulls media over the network.
Sometime approx 2023 - early 2024, the 32 bit ARMv7’s crossed the boundary.
Aug 31, 2025 17:28:34.219 [1077915664] INFO - SQLITE3:(nil), 17, statement aborts at 59: [select * from metadata_items limit 1] database schema has changed
Aug 31, 2025 17:28:34.269 [1077915664] INFO - SQLITE3:(nil), 17, statement aborts at 59: [select * from metadata_items limit 1] database schema has changed
Aug 31, 2025 17:28:34.319 [1077915664] INFO - SQLITE3:(nil), 17, statement aborts at 59: [select * from metadata_items limit 1] database schema has changed
Aug 31, 2025 17:28:34.363 [1077915664] INFO - SQLITE3:(nil), 17, statement aborts at 59: [select * from metadata_items limit 1] database schema has changed
@trumpy81 thats not normally database corruption, that could just be plex updating/doing plex stuff. Normally if you have corruption you will see a malformed or sq1 related error.