Server Version#:1.25…8.5663-7000
NAS: Synology DS214play
It is incredibly annoying that after updating to DSM 7, and then updating the PMS, the PMS did NOT recognize the server. Instead it created another server with the exact same name. This means that I cannot access any of the already created libraries as the PMS is saying that it cannot access the “old” server (there have actually not been any changes to the server)…
Given the very large music library I have that was extensively edited to fix incorrect matches, is there a way that I can still get this metadata and apply it to the new library that I have to create?
Still dumbstruck that PMS would actually do this and not just maintain the connection to the server. It would be an incredible waste of time if I have to recreate the libraries…
The PMS upgrade migration process starts automatically when it detects a Plex shared folder.
There are very few ways this can fail.
The most common is when permissions for the Plex shared folder have been manually set to something non-standard. This becomes a problem the DSM 7 installer doesn’t have administrator privileges anymore. (part of what changed in DSM 7).
The reason you’ll get a duplicate name is because the default server name is the NAS name (hostname)
Did you review the How-To to familiarize yourself with the process?
Thanks for the response. I actually did follow the steps you are mentioning (and did wait for quite a few months to go to DSM 7 so that the teething problems are resolved) and the database still got messed up!!! I’ve given up on it and will now focus on updating the metadata on the music files themselves as this is probably ~5th time over the years that I’ve had the Plex music database fail or get corrupted or whatever and every single time I have to spend lots of time fixing incorrect matches when creating a new one.
It makes no sense that this database information cannot be saved and then applied later when the same database is recreated. It should be a super easy and quick feature to implement.
