The installation and migration worked as a charm for me. Reading carefully is key
Question: Plex is notifying me that thereās a new update available and routes me to the Plex download page. I assume I have to ignore this since that arenāt the DSM 7 packages?
Also, you mentioned the updates will be distributed trough package center for now. Is this going to be the normal way to update? Normally I had to install every update manually as a package but āauto-updateā trough package center is always welcome.
i tried after starting Plex as it seems that it does not use the old library directory.
it still does not use not use the āoriginalā library directory nor has imported the old preferences.xml
i did a complete reinstall (first point activated in the new deinstallation dialogue ( i like this new one)) i choose th eold plex share directory as log target and now there is a new folder which contains logs. im very confused
How is the migration work?
Please give path names for āOldā and āNewā where possible?
What you write seems informative but I donāt know your configuration layout so canāt follow the āFrom whereā and āTo Hereā steps. Volume + Folder helps me a great deal.
If referring to the new internal ā thatās easy , write āApphomeā . Iāll know what that means.
I tried installing the Plex DSM 7 from the download link in posted in DSM 7 - Plex Media Server forum preview. I get an error that port 32400 is in use. I tried removing that port from the port forwarding configuration on my DS916+ and in desperation uninstalled the DSM 6 Plex install.
You are probably right, but I removed my old install of Plex, so those files donāt exist anymore. I am probably hosed and will have to wait on the good work of the Plex folks here.
OLD DMS 6 PATH: /volume1/Plex/Library/Application Support/Plex Media Server /volume1/Plex was recognized by the installation wizard as installation directory. I gave the needed permission as shown in the installation guide, but it didnt lead to takeover, so i tried to change the file permission also without any positiv result.
at this time i had to servers with the same name in my plex account, one without any Library and one with the original libraries but unconnectable
now i have removed the whole plex installion (using first option in the deinstallation dialogue)
then i was installing PMS again. i was ask for a directory for the logs and i choose this where the old plex installation was situated. after starting Plex it creates a new log folder inside this directory, so for me no permission problems should be the root cause for this āfailed migrationā
i do have the old data (databases, preferences) - can it be used for copying or something like that?
NEW DSM 7 PATH
/volume1/@apphome/PlexMediaServer/Plex Media Server/
The failed migration is a signal of one of the following; none of which are pleasant.
There is data in the @apphome location with a different UID/GID
Manually changing permissions in the Plex shared folder caused ownership / permission problems when it went to migrate (we expect ACLs and UID/GID = plex:users).
DSMās uid/gid database (which it uses extensively now) differs from /etc/passwd and /etc/group.
I am not concerned about the Log file location. That is easily remedied.
First steps: Letās get this to install and migrate:
I am going to give you the commands to āencourageā it to work for you
Prerequisite:
DSM 7 package installed ā failed state (this created the username)
DSM package ā Uninstall - Remove all data (non-recoverable) option
a. This clears out apphome.
I believe you said your Plex share is on Volume 1. The above commands donāt care where it is. It will find the existing Plex shared folder (where your metadata still lives)
What this does:
Goes to the Plex share
Gives the new Plex username (PlexMediaServer:PlexMediaServer) ownership of everything in the /volume*/Plex/Library directory (which is how it will end up after migration)
It then makes certain to completely clean out any remnants of the DSM 7 storage areas so migration can run cleanly.
Before running this, confirm the existence of the new username, properly defined by Synology (the UID & GID are a big number now)