This test sets up a new, temporary, “Test” server while keeping your existing server safe. It will help us figure out if the problem is somewhere in the PMS database or in DSM itself.
Here’s what I’d like you to do
-
Make certain latest PMS is installed
-
Stop PMS
-
Sign out of the Plex/web app (upper right corner), close the Plex/Web tab.
-
Open the Plex shared folder in FileStation.
-
Rename
Library
toLibrary.save
(we’re going to keep what exists safe) -
Start PMS
-
Let it startup for a bit (about a minute)
-
Open an Incognito window to http://ip.addr.of.syno:32400/web
-
Start to sign into this new server “Got It”.
-
THIS IS IMPORTANT
-
Give this new server a Friendly name which is unique - “TEST SERVER” (we don’t want the name to collide with the default name for the Syno)
-
After you have “CLAIMed” this new “TEST SERVER”, you no longer need to use the Incognito window.
Here’s where the test will take some time to complete.
- Define a library section and let it populate before doing anything.
- Use it and see if you can recreate the crash. Be certain to allow enough time
- If you cannot make it crash, add another library section
- Repeat steps 2 & 3 until everything is fully built back up.
Possible outcomes are:
-
PMS crashes even in this test configuration → DSM / host problem
-
PMS does not crash after a complete rebuild of the entire configuration → PMS problem.
How do you feel about this?