With that packaging, you still should NOT blindly try to update via the GUI. I will provide assistance. ( I have not yet worked out a viable How-To for everyone)
Here is the information about what has changed and why.
Yes I thought it was likely related. I added more details about my situation below. I am trying to move my plex server from Nvidia Shield to a Synology NAS.
Here are the steps I took:
copied all media files to the NAS (from external hardrive)
manually installed PLEX on NAS
claimed the new PLEX server with my PLEX acccount
What I would then like to do is import my library structure, metadata and playlists. I did find a tutorial on youtube that walks you through the process, but it tells you to copy into a shared “plex” folder.
Issue: I do not have a “plex” shared folder and I cannot see a “plexmediaserver” user (even though I am using an admin login).
When browsing in PLEX from the “add library” view. I can see that the folder I am likely looking for is “/volume1/@apphome/PlexMediaServer/Plex Media Server”.
I have tried connecting in FTP via filezilla but it brings me to an empty folder with solely a “#recycle” folder. I have tried connecting via SMB but I only see the shared folders (not this @apphome one).
Question: If I couldn’t migrate my entire library, at the very least I would want my playlists. These took weeks to curate. Is that something that could easily be done?
Question: If I want to get my playlists back, should I wait for your new package? Or can I add the libraries today from the new NAS source … and get my playlists back later?
Question: Just out of curiosity, what is the best technical avenue to access hidden folders?
7. Depending on the amount of metadata – this will take an proportional amount of time.
8. When done, you are ready to install PMS for DSM 7
I invite you to consider the updated package (which will be public release in a few days). It contains many improvements which I’ve been working on since the beginning but couldn’t complete until DSM 7 seemed stable.
Here is my Forum Preview.
You will find the SPK file for your machine there.
If you choose to read further down, you’ll see the feedback so far.
If you use this package now, you will be already in the new layout.
As it runs and “Migrates” your data from “Plex” to the new structure, It will do so at about 500 items / minute. This can’t be helped. CPU speed is the limiting factor.
Before stalling I do suggest increasing the DSM Security Timeout to something longer than 5 minutes. (my office is secure so 65535 is completely safe for me).
Be patient with it.
“Migration.log” (in the “Plex” share) will contain progress as it does all its work.
Created /Plex/Library/Application Support/Plex Media Server
Edited permissions for plexmediaserver user
Copy-pasted content of shield plex folder into “Plex Media Server” folder
Next: install PLEX
Next: edit source of each library to new source (NAS vs. hard-drive)
A few follow-up questions:
My Plex server on shield was pointing to files on my external hardrive. I have my file on the NAS now. I likely will need to edit the source of each library. Would this be a problem?
I see several spk, assuming I should pick the one at the top?
Do I need everything in that “plex media server” folder? I really mainly want the playlists. Everything else I could afford to start from scratch.
Thanks a lot. I’m immensely grateful for the help! Will await your response prior to loading a new plex media server (either this spk or the one on the plex website)
Synology did not change anything about existing shared folder locations. All existing exported shares remain intact.
Select the new version, which should still match current PMS release, and then install the correct binary SPK for your NAS
Your “PlayLists” are part of the data and database of Plex Media Server. “Playlist” is a construct which points to several already-indexed music or video items. If you want everything to migrate, you must include the Entire contents of the ‘Plex Media Server’ folder . It’s All or Nothing. PMS can’t be “sliced and diced”.
The goal here is to “take an existing server instance, in its totality” and “move that entire instance to a new machine”… transparently. After it’s done and running, you can do what you wish from that new running PMS GUI.
re: Shield to NAS
Library for the Shield was on one single external hard drive (8TB) vs library for the NAS is on the NAS. What will happen when I install a new Plex server with the plex folder populated with metadata & all?
re: PLEX version
Which one from the thread would you recommend?
got a warning popup about access on top of install window
they both disappeared in a 1/10th of a second (no idea if the install completed properly) … past installed took longer, this felt like a glitch.
connected to plex but could see a legacy NAS plex server, deleted it, expected to have the same steps as before to follow (naming the server, claiming it etc) but didn’t
cleared browsing data
signed out of plex, tried to connect to it again - no option to claim new server
uninstalled new plex package (with signout and keeping data)
installed plex package again (steps 2 and 3 occurred again)
Not quite sure what to do now?
It does not look like the installation completed?
Is the content supposed to auto-populate? Is the path to source folders in the metadata that were migrated?
Please post the screenshot here. You may edit the post and remove later.
Your google link is closed access.
Not sure what you did at all. It takes about 15 seconds to complete a flawless installation on synology machine at the absolute best
Whatever that popup warning is/was – is probably key. I generate them in response to specific misconfiguration / needed action during installation as I validate all settings.
Sure thing. Posted the screenshots below. Maybe it did complete properly then, it was just very odd to see the popups appear and disappear.
My issue is I was seeing the name of an old NAS Plex instance (that was removed), so I removed it … and ever since then, I don’t get an option to pick a new name for the new server.
Whenever I click on the PLEX path from the package center, it tries to connect to my existing PLEX account that has my shield PLEX server in it. I tried signing out but it keeps going there.
second scenario: claiming NAS plex server with google account (but mix up between the 2 servers)
… but if I do claim server with my google account - it goes to my google account and seems to mix up the shield server and NAS server:
third scenario: after refesh, only seeing the new server (lost the shield one)
After refreshing multiple times – PLEX account is now only showing the new “PLEX on NAS” server. The Android Shield PLEX server disappeared from the web interface. Note that I have the shield plex app opened and it can still show the Shield Plex server.
Ideally I’d still be able to see both. Any tips on how to do that?
Image 2 - the “QuickConnect to” link is because you’re using the Synology FQDN name to get into the server and it’s not claimed. – More on that in a minute
Image 2 – It’s also just a standard security warning by Plex/web that it doesn’t recognize this URL and is giving you the Anti-Phishing warning just in case. It’s your server so there is no mystery here.
Image 3 - Migration.log - Everytthing went 100% normally. Total migration time about 3 minutes.
Image 4 - Is the new (what will be official production structure moving forward) as soon as Engineering releases my builds. QA has already approved the code. We’re waiting for them to include it in their next build.
Image 5 - This is the message sequence you see after migrating PMS into DSM 7.
a. Summary message “migration from /volume1/Plex” (other configurations are possible. This confirms which source location was used)
b. Shows you the log is available for review
c. Reminds you to now check permissions so user PlexMediaServer has permission to read media. (MANY people still think the username is “Plex” because they don’t read the documentation. It is now “PlexMediaServer”)
Everything here looks ok.
As first time to access the server following relocation from the shield,
I strongly suggest you use the IP address of the Synology because there is something strange in the URL Synology is providing you. I don’t use “QuickConnect” and get a standard IP address as I should.