Synology: DSM 7 Installation Archive -- Archived from main thread

[ChuckPa]

Ok…

In DSM 7, the Plex shared folder is 100% free for you to use as you see fit.

PMS itself will reside in the new PlexMediaServer shared folder.

Since you want to otherwise start fresh,

Open FileStation,
Go into the Plex shared folder,

If you don’t have any media anywhere under Library – delete Library.
This will remove ALL of Plex’s metadata (a full wipe of the PMS server data so you can start fresh)

If you currently have media anywhere else in the Plex share, you can delete the “Plex” shared folder after you’re done reorganizing.

I get it right this time?

[dlleno]

I can create pms libraries and index my content.

[ChuckPa]

Once you’ve

1. Deleted the Plex metadata from the Plex share
2. upgraded to DSM 7.
3. Performed a “Manual Install” of the DSM 7 Plex app (plex.tv/downloads)
   (dsm 6 and dsm 7 aren’t compatible with each other)

Then you can do whatever you want.

My only reqest is, because we don’t have any special privileged on DSM 7,
is not to put things in / touch the PlexMediaServer shared folder.

[dlleno]

Ok so

1. Delete pms libraries
2. Un install plex
3. Migrate to 7
4. Restructure content
5. Install pms

?

[dlleno]

The sticky wicket is to delete all libraries while in dsm6 and before Uninstalling pms. No other manual folder deletes?

[ChuckPa]

CAREFUL.

1. You don’t have to delete any library sections within Plex.

2. We’re going to wipe out the DSM 6 Plex data itself.
   (This is where we delete Plex/Library (the server internal data)

3. The NAS will be clean and ready for DSM 7 and a new Plex install.

Is this what you want?

[dlleno]

Oh ok so while on dsm6 manually delete the plex library folder .

1. Uninstall plex
2. Remove the folder plex/library
3. Migrate to dsm 7
4. Move content to desired folder
5. Install pms

[ChuckPa]

YES, that’s it.

[dlleno]

Fantastic thank you! Get some rest!

[ChuckPa]

REST is a 4 letter word!

[dlleno]

What hsppens to the folder “plex” that still remains?

[ChuckPa]

You can delete the Plex shared folder if you want.

We have no need of it.

DSM forced us to change the username and package name so we make it consistent with all the other platforms

1. Username: plex → PlexMediaServer
2. PackageName: “Plex Media Server” → “PlexMediaServer” (internally)
3. Shared Folder: “Plex” → PlexMediaServer (and cleaned up the folder structure)

[mcclymoa]

I can helpYou have downloaded the ARM version of the Plex, however, as shown in your Info above, you have an Intel Atom CPU. You need to download the x86 64Bit Intel version.

Try that!

[degoal]

Last year, when I upgrade from DSM6 to DSM7, I ran the Beta Plex App available through the Package Center. At this moment I did not know about the official guidelines and procedure to upgrade described here DSM 7 - Plex Media Server - Release Info & Migration instructions
That said, everything was working fine with the Package Center App.

Since the data breach, I changed my password, and after that, cannot claim my server from the plex web player.

So I choose to remove my Beta install and go for the official one. I’ve followed all the migration process without any problem, but now, when I try to launch plex, I get this error.

Response code=“503” title=“Maintenance” status=“PMS is currently running startup maintenance tasks.”

Plex Media Server.log (6.3 KB)

Any idea ?

[ChuckPa]

Sounds like you have a few things going on.

1. Response code 503 is “Not Available”.
   – It was just released by the server team.
   – I don’t know if the apps have all caught up with that or not

2. Upgrading from 1.21.0.3744 to current is a wise move. It might take time.
   – Your server internal data will be moved from the Beta location to it’s final release home in the new "PlexMediaServer shared folder
   – Be patient while this completes else it will make a mess to clean up manually at the SSH command line level

3. Lastly, Recovering from the breech is now straight forward
   a. Uninstall the package with “Uninstall Only ; Keep” option
   b. Reinstall the same SPK file you downloaded from Plex.tv
   c. Select the “Install using Plex Claim Token” radio button
   d. Click “Get Plex Claim Token”
   e. A new browser tab will open with claim token. COPY it
   f. Return to the installer menu,
   g. PASTE the token in the small box (Looks like this)
   

   
   
   h. Click NEXT → DONE
   i. It will now install and claim.
   j. When done, it will confirm with “Claimed by: Your_Plex_username”

[degoal]

Thanks @ChuckPa ! You were right, the app needed time to start properly, it works like a charm this morning.
I’ve also claim the server as you suggest and everything works now. Thanks for such reactivity !

[ekalp]

@ChuckPa thank you for all the work done in these threads! I read through almost all 1000 replies and found the answers I needed to solve my NAS >> NAS move I was doing from DSM6 > DSM7.

[ChuckPa]

@ekalp

You could have just asked

lol

(I’ve only read some 5000 posts and replied to since this started last week; what’s one more )

[jmsoren5]

Hey @ChuckPa,
I’ve got something I’m sure you will know right away. I recently switched to a new router, went through your help guide of uninstalling and reinstalling to get a claim code. Have done that, and it still give me “not authorized”.

And Big Thanks in advance

[ChuckPa]

@jmsoren5

I’ve been bit by this one myself more times than I can count.

“Not Authorized” in Plex context happens most frequently when it can’t get to plex.tv and communicate. (DNS lookup / Gateway address incorrect for either or both )

The other thing which happens from this reset: The browser still holds all the old credentals – EVEN IF – you open a new Incognito tab.

Most browsers don’t completely clear their contents with new tabs.
Try:

1. Close the browser
2. Open fresh
3. Open Incognito
4. Now hit the Syno via http://lan.ip.of.syno:32400/web

That failing, can you manually grab a ZIP file of the “Logs” directory and then look for “resolve host” and call out plex.tv ?

I’ll look if you want me to