not worried about the Operation not permitted. those are harmless.
The last line shows me it’s copying the files.
Given it’s October and we’re now November… It never finished.
Did you restart the Syno at some point???
I can force this together given the processing is complete. I will give you a User-Script to run . When it’s done, you’ll have the old server as it was as of 30 Oct with all its metadata
So the largest amount of content is in Plex>tmp_transcoding, not the Library folder (although the library folder still has around 70GB or so spread amongst the old folder structure). The tmp_transcoding one is 412GB, with 8383 files, 117 folders. Every folder is “music-analysis-input”. I do currently have Sonar Analysis running so I’m assuming it’s related to that, is this part of the running process or junk files? Once that is finished running I should try and merge the folders?
I don’t believe I restarted it but I could be wrong
You can dump EVERYTHING under Plex/tmp_transcoding when you’ve got it idle so you can do so.
Given the Migration log does not say “Completed: Migrate Plex Media Server”, then it never finished that step.
After “Migrate” is “Clean”.
Something did interrupt it. I’m uncertain what did.
Am I correct assuming that you’ve manually set your Plex transcoding temp to /volume1/Plex/tmp_transcoding ?
If it were automatic, it would have moved to PlexMediaServer with the DSM 7 migration.
No, I didn’t. My “PlexMediaShare” folder does have a tmp folder, (tmp not tmp_transcoding) with it’s own media_analysis folders, but it’s much smaller (only 2GB). I was running the Analysis before the upgrade (I stopped it before I went through the uninstalling/upgrade), and have restarted it since.
It either moved pieces of everything into the new PlexMediaShare install, or it’s a mirror for some reason. Although the tmp folder in Plex is MUCH larger.
All of this being said, my Plex install is working fine, it’s fully upgraded and all the MetaData is there, all my libraries, I can watch stuff. DSM7 is installed and working fine. So I’m completely fine leaving that Plex folder if everything is working, just wondering about that tmp_transcoding folder now
(Also if I look inside of Plex, settings>Transcoder the “Transcoder temporary directory” option is a blank box with nothing listed. I’m not sure if there was every anything here)
PlexMediaServer does have a tmp folder. That’s what I set it up to have.
2GB in it sounds correct.
I just can’t figure out what might be running in your Plex share. That’s not making any sense to me.
If you look in tmp_transcoding and then sort on the Date column, Is anything changing / has changed since migration ?
Thanks @ChuckPa! Migration apparently completed during my last installation attempt before timeout. The migration log (the only file remaining in the Plex Share) says that Clean completed. My PMS is back up and running.
I belatedly read through your recommended threads, and everything makes sense, thank you. Apologies for not digging through this material earlier.
Thank you for getting back to me.
I hope all that babbling makes sense now? 
Regarding migration – For those who read this later:
Once started, Even if DSM makes you log out in the GUI / refresh the page
Migration will continue until completed.
It’s running in the background because DSM is in control.
The only requirement is that the NAS not be restarted until after conpletion.
Typical time to complete is 3 minutes for each 1000 items (movies, episodes, vidoes, songs, or pictures) indexed.
No the latest date is October 28th (I can’t say for certain that’s the day I upgraded DSM, but it likely is)
It’s a mix of music-analysis-input folders, pms-2385y2randomletters folders (about two dozen folders in general), and then what appears to be a lot of jpgs (7177 items in total)
I’ve been running Sonar Analysis almost non-stop since the upgrade and have been adding new media as normal, so if it was still using this folder I’m sure there would have been something new by now.
The Plex>Library>Application Support>Plex Media Server folder doesn’t have anything later than October 29th in it either
If there were anything running at time of upgrade, it would have been shut down when DSM restarted.
That said, If all those files are indeed pre-DSM upgrade — WIPE 'EM 
If that’s the only thing remaining in the “Plex” shared folder ,
And you don’t have any use for the “Plex” shared folder,
Go right ahead and get that space back!
I am at a loss for where to begin. I was told by someone who I thought would know that these issues had been worked out with PMS on DSM7. I am running a DS918+ and held off on upgrading for quite a while until a few weeks ago. Being told by a contact who has a fairly high reputation in the Synology world, that these issues had been solved and I was safe to update, I proceeded. Now, I cannot even get PMS to install. I have downloaded 1.24.5.5173 for DMS7 and for DSM6 and get 2 different errors when trying to run manual install. On the DSM6 version, it tells me that it was made for an older version of DSM7. On the DSM7 version, I get an error about Port 32400 being in use. I really hope that I haven’t fried my PMS dbase since I have thousands of files saved. Reinstallation of DSM7 really isn’t an option since I have backups flowing in from another site and I really don’t want to disrupt that. I tried to find info in this forum regarding this specific issue but couldn’t find it. Thanks for any help.
You must be very careful with DSM version labeling because the SPK files are not cross-version compabile.
That’s why you have filenames with DSM6.spk and DSM7.spk .
Trying to install the package for the other DSM version will give the “made for an older version” or “higher version” error.
On the DSM 7 error you’re getting about the port in use, the corrective action here is to restart DSM 7.
My sugestion is:
The package will find your existing DSM 7 installation and use is as-is.
In DSM 7, just as was in DSM 6, Metadata is not removed unless expressly instructed to do so with the “ERASE” uninstall option.
Plex is not installed so there is nothing to stop. But, after restart, I’m still getting the same error.
Check the Synology Firewall.
No, it’s not enabled.
I saw that elmugal1 had the same problem as I am, but I don’t see where it got resolved.
Full disclosure, I got excited to upgrade to DSM 7 and just jumped in, THEN found out Plex had issues and a specific plan so I didn’t break things. So, I’ve been unable to use Plex for a couple of months now, and I’m missing my movies!
I have recently updated further to 7.0.1-42218, but am still getting the “This package is not supported on the platform of DiskStation or is incompatible with the current DSM version.” message.
I have a Synology DS418, and am downloading the package named “PlexMediaServer-1.24.5.5173-8dcc73a59-armv7neon_DSM7.spk”
I’m sure I’m missing something obvious, but what is it? Thanks in advance!
There are separate package versions for DSM 6 and DSM 7. Be careful to get the one for DSM 7.
There are two different CPUs used in the DS418 series.
DS418 Realtek RTD1296 Quad Core 4 Yes rtd1296 DDR4 2GB
DS418play Intel Celeron J3355 Dual Core 2 Yes Apollolake DDR3L SODIMM 2GB
DS418j Realtek RTD1293 Dual Core 2 Yes rtd1296 DDR4 1GB
For the DS418, you want ARMv8, not ARMv7neon
So, any suggestions on this firewall issue? Anything else I can try to get this to install?
This might be one where you need synology support to go in and manually clear it out (which they know how to do).
I see no logical reason for anything to be stuck, based on what you’re telling me.
Hmmm, I didn’t think they would get involved since it was a 3rd party app. Is my current database/meta data safe within the Plex share?
They will assist if the firewall is ‘stuck’.
You’re in a situation where you can’t install an application because of it.
They will assist to the point of helping you get it installed.
After that, they will be ‘contact Plex’.
While Plex is 3rd party, Synology did work very closely with us (even urged us) to be ready for DSM 7 when it launched. It seems Plex is important to them (sales perhaps?)
