Not consciously!
Open your docker control app.
Please look there and see if you have “Plex” in some form.
Ok then,
If all the following are TRUE
- Package center has a version of Plex with the
-7000package identifier (DSM 7) - Your Server and all it’s contents are fully accessible
- Everything appears to be running normally,
-THEN-
-
You’re free to delete the
Plexshared folder. -
I would advise keeping your backups for a week or two.
-
I suggest this because of changes which are about to be published for how PMS runs on Synology. ( Packaging “2.0” release )
I believe I saw reference to build 3744 somewhere ?
If you’re using this, please do update Plex from plex.tv/downloads
That 3744 package was BETA. Plex.tv/downloads is the proper “Production” package.
Great! Thanks for your generous help. I appreciate it. 
One last question:
Is there any way to tell which Database (the dir structure) the server is using??
Not sure why that is of importance because that is all part of the “Plex Metadata” .
Everything fits as a unit:
MediaMetadataPlug-in Support
These are the heart of what PMS knows about your media. Separate out any piece and you have a lot of reconstructing to do.
OK. We’ll leave it at that!
Update! I just deleted all the Database files from the Plex shared folder and re-started the Plex server with no issues. The Database was astro-magically migrated ‘somehow’ to the @apphome directory all as discussed above.
Chuck,
I migrated 2 days ago and all seemed to go well, I can access and play all files using the package you uploaded in the 2.0 thread. I am also now using Hyper Backup to backup my database files once again. But despite all this, I am still a bit nervous.
If I answer the 2 questions you posed another user above, I get slightly concerned. Did I:
- Have to claim the server ? - No.
- Have to recreate any Library sections ? No.
I also don’t have a migration log in the original Plex folder.
Does this seem normal?
I’ve uninstalled Plex with the delete option; set all the permissions correctly; installed fresh with new token.
I start Plex, it runs for about 10 seconds and then says it has manually stopped.
I’m running PlexMediaServer-1.23.6.4881-e2e58f321-x86_64_DSM7.spk on a DS918+
Any ideas what else I can try?
The new packaging (2.0) does some clever moving of an existing DSM 7 server installation from the internal storage area to an administrator-visible shared folder.
There are no permissions issues or migration issue to worry about because all that pain was done when we migrated from DSM 6 (just as I promised).
The biggest reason I pushed hard to make this work now is because we really NEED to make backups of our metadata and DSM 7.0.41890 appears stable.
HyperBackup had to get access (it can see the internal easily enough) but Synology wouldn’t allow the app to talk to it so I had no choice but to find a way to get the data to HyperBackup.
If you go back to the Packaging 2.0 Preview thread I opened, you’ll find I laid it all out there. Nothing is hidden.
My ONLY request in all this:
- Everyone has the Plex shared folder if they want
- PLEASE leave the
PlexMediaServershared folder alone. It containsAppData(Application Data) only.
To answer your question:
There is no migrating . I make the move as part of any install or upgrade – silently.
uninstall + Erase that one
Now download and install the OLD one from Synology Package Center.
Also , is this an ARMv7 NAS ?
Hi Chuck, thanks for the thorough explanation - the time you’re taking in this thread is massively appreciated.
Sorry, my post was poorly worded - I should I have said my post was in relation to the initial DSM 6 to DSM 7 update.
I never had to reclaim the server, or was asked to recreate libraries. I don’t have a big library (around 5TB) so although I was expecting a quick migration, mine was almost instant.
The almost instant transfer, along with the lack of migration log, is possibly what is what is making me slightly worried.
Something and nothing likely, I can see the new Plex Media Folder and am now backing up the contents so presumably I couldn’t do that if something had gone wrong.
Stan,
Given we have two things going on at once in here, please do try to be specific.
Line item detailing is often the best for me and my pedantic
methods ![]()
Using the Plex version downloaded from https://plex.tv/downloads
When migrating from DSM 6 → DSM 7, the expected main events are:
-
Grant
System Internal UserPlexMediaServerFull Control of thePlexshared folder by using theCustompermissions button inControl Panel→Shared Folders. -
Scripting then does the following:
a. Changes ownership to PlexMediaServer
b. Converts any legacy metadata linkages to new format. (about 500/minute)
c. Bulk move of the entire “Plex Media Server” folder to the new location
d. Cleans up the old, now unused, Plex share
Plex Media Server migration to DSM 7 started: Thu Jul 29 22:02:51 -05 2021
=== Thu Jul 29 22:02:51 -05 2021 === Start: Change ownership
=== Thu Jul 29 22:09:07 -05 2021 === Completed: Change ownership
=== Thu Jul 29 22:09:07 -05 2021 === Start: Convert symbolic links
=== Thu Jul 29 22:17:10 -05 2021 === Completed: Convert symbolic links
=== Thu Jul 29 22:17:10 -05 2021 === Start: Migrate Plex Media Server
=== Thu Jul 29 22:17:10 -05 2021 === Completed: Migrate Plex Media Server
=== Thu Jul 29 22:17:10 -05 2021 === Completed: Migrate Plex Media Server
=== Thu Jul 29 22:17:10 -05 2021 === Start: Clean /volume1/Plex
=== Thu Jul 29 22:17:10 -05 2021 === Completed: Clean /volume1/Plex
Now, if you use my new “Packaging 2.0” version,
- The migration is the same
- Additionally, it will move an existing DSM 7 package out to the new location.
Please clarify for me. Your answers will determine if I have a problem or not.
- Did you upgrade DSM 6 → DSM 7 ?
- Did you then use my new ( 2.0 ) packaging to migrate ?
According to the specs it’s an Intel Celeron J3455. The only one of the 5 options that would install was the Intel 64-bit version
My bad, apologies!
Yes, I upgraded DSM 6 → 7 on Thursday night.
I initially used the Plex version 1.24.0.4897 as published on the Plex website downloads section. After some troubleshooting, all worked fine. (as expected, I couldn’t yet see the Plex Media Server folder).
Then on Friday night, I used the 1.24.0.4897 pre-production version. Downloaded and installed per the Google Drive link in the “2.0” thread linked previously in here. (now able to see the Plex Media Server folder).
Hope this makes more sense!
I don’t have a Plex available in the installable packages list. When I go to the Synology Package Centre online there’s nothing downloadable.
Stan,
Now it makes sense.
-
You would get a “Migration.log” in the Plex shared folder when you use the production package because that was the actual DSM 6 → DSM 7 migration.
-
Any time (production or my pre-production) a DSM 6 → DSM 7 migration is performed, I will write “Migration.log”
-
Upgrading (moving) an existing DSM 7 installation is instantaneous .
Got you!
Should I not see a migration.log file for the original migration then? Nothing ever appeared!
Also, the instantaneous migration I mentioned was the DSM 6 → 7 migration.
That’s weird. You are the 3rd or 4th person to report that.
I’ve never found out why.
Maybe we chalk it up to Gremlins given the machine is running 100% normally without having needed reclaiming or re-initializing in any way? 
How do I get to the plex logs? When I installed, I chose the “use internal PMS storage” option for the logs (and now I have uninstalled completely with delete
