Plex Media Server - Synology DSM 7 Preview - Issues ( Archive )

[ChuckPa]

I have reached out to Synology about this problem.

I’m at a loss to explain it as well.

It seems the Photos app has declared exclusive access, independent of shared folder permission, to itself.

What happens when the Synology Photos app is removed?

[gabhroo]

bizzare - i will give that a shot… I had stopped the service (Synology Photos) and rescan in plex w/ no luck.

If I uninstall Plex, and remove prior info - what am I loosing? Metadata that was downloaded, view history, etc? Thinking of doing the “non recoverable” option - and start from a clean Plex install.

[gabhroo]

@trumpy81 in doing so, will I then have two photo stores on my NAS, one for Synology app, and the other for Plex? Frustrating as videos has no issues - only photos.

[ChuckPa]

TO ALL FOLLOWING HERE:

Regarding the Synology photo shared folder

Please be patient a few more days while we wait for Synology to investigate and respond

[rob_in_SD]

Just wanted to say that the change to allow changing logfile locations at upgrade time is working fine. Just upgraded to PlexMediaServer-1.23.6.4810, and received the offer to move logs to location of my choice. I paused and made sure that the location of choice, /volume1/Public/PlexLogs existed and that PlexMediaServer had R/W permissions for the Public shared folder and anything below it.

Once that was done the upgrade continued as expected without error. Double-checked and all the logs were moved to the designated folder.

Thanks again @ChuckPa!
Robert

[atagert]

my upgrade went swimmingly. Followed the instructions and there was nothing unexpected or unclear. Thank You…

[ChuckPa]

DSM 7 Release Issues

Synology has finally advanced DSM 7.0 to Release status
– Complete with more changes.

In this thread we will focus and resolve any issues which result from the latest (DSM 7.0-41890) firmware.

Reference to existing DSM 7 package features and migration instructions can be found here with the migration procedure beginning with the second post of the thread.:

DSM 7 - Plex Media Server - Release Info & Migration instructions

Plex Media Server for Synology DSM 7 - Release This document is to share changes made with DSM 7 and resolve any unforeseen issues before you attempt migrating to DSM 7 for Plex use YOU ARE URGED TO READ THIS THREAD COMPLETELY BEFORE PROCEEDING OR ASKING QUESTIONS DO NOT INSTALL Synology BETA software UNLESS INSTRUCTED. This thread is a LIVING document. Expect it to change. Synology’s DiskStation Manager (DSM) has undergone significant changes in version 7.0. Many of those changes affected …

Read below and evaluate your status before proceeding.

[ChuckPa]

Abbreviated & customized DSM 7 migration procedure (for those who missed it)

This is a detail-rich process. It cannot be avoided due to DSM 7’s changes.

This is a 2-stage process.

The first attempt WILL FAIL – Expect it.

If all instructions are followed (screenshot instructions if needed) it does work.

1. Restart DSM again after upgrading from DSM 6

2. Now uninstall the DSM 6 package

3. Install the DSM 7 package (it will fail here and where the instructions begin)

4. Control Panel - Shared Folders - EDIT - Plex

5. Permissions tab

6. Select “System Internal User” (observe this screenshot)
   

   

7. Click CUSTOM (observe this screen pop up)
   

   

8. Assign Read/Write/Administrative control for PlexMediaServer
   

   

9. Click Done, Window closes and presents this window
   

   

10. Click “Apply to this folder, sub-folders, and files”

11. After the control panel finishes, OK/DONE out of the window

12. Attempt installation again.

13. Migration will vary per user depending on media indexed and NAS model

14. When successful, you will see
    

    

FULL PROCEDURE HERE:

DSM 7 - Plex Media Server - Release Info & Migration instructions

DSM 6 → DSM 7 Migration Process NOTE: Use the Plex package from Media Server Downloads | Plex Media Server for Windows, Mac, Linux, FreeBSD and More ONLY. Package Center is no longer compatible with Official Release DSM 7.0-41890 and above. Use the following steps then continue below as is appropriate for your configuration. Uninstall the DSM 6 Plex app Control Panel - Shared Folders - Verify the Plex share is spelled “Plex”. If not - Rename it to “Plex-temp” and then back to…

[ChuckPa]

Please feel free to voice your displeasure regarding DSM 7 directly to Synology

[ChuckPa]

WARNING:

IF DSM 7 is showing as an UPGRADE on the DSM 6 package –

In order to remedy

1. Confirm all metadata still exists in the Plex share
2. Uninstall the DSM 7 package
3. – Select the ERASE all of PMS option (erases the errant DSM 7 data)
4. After fully uninstalled,
5. Now install DSM 7 package again.

PLEASE READ

DSM 7 - Plex Media Server - Release Info & Migration instructions

DSM 6 → DSM 7 Migration Process NOTE: Use the Plex package from Media Server Downloads | Plex Media Server for Windows, Mac, Linux, FreeBSD and More ONLY. Package Center is no longer compatible with Official Release DSM 7.0-41890 and above. Use the following steps then continue below as is appropriate for your configuration. Uninstall the DSM 6 Plex app Control Panel - Shared Folders - Verify the Plex share is spelled “Plex”. If not - Rename it to “Plex-temp” and then back to…

I know –

1. I know this is painful
2. I would hope, by now, folks actually know to read thoroughly what has been documented
3. ASK before getting caught in a failed state. It is easily avoided.

[ChuckPa]

1. DO NOT INSTALL THE SYNOLOGY PACKAGE CENTER package file – it is incompatible with what DSM 7.0 accepts

2. @EdgeU2 you MUST read the DSM 7 information. It has completely changed.

DSM 7 - Plex Media Server - Release Info & Migration instructions

Plex Media Server for Synology DSM 7 - Release This document is to share changes made with DSM 7 and resolve any unforeseen issues before you attempt migrating to DSM 7 for Plex use YOU ARE URGED TO READ THIS THREAD COMPLETELY BEFORE PROCEEDING OR ASKING QUESTIONS DO NOT INSTALL Synology BETA software UNLESS INSTRUCTED. This thread is a LIVING document. Expect it to change. Synology’s DiskStation Manager (DSM) has undergone significant changes in version 7.0. Many of those changes affected …

3. Of special interest is post #6 — The Migration instructions.

[ChuckPa]

User plex is of no use anymore. DSM 7 obsoleted it … else I’d have reused everything.

I couldn’t even keep the “Plex” shared folder. (which is why this crazy dance to get your data out of it )

After migration, The Plex shared folder is free to do as you wish … Delete it ? Put media there? Have Fun!!!

[ChuckPa]

Yes — Backup / Restore / Import are on my agenda.

I did not dare to start that work while DSM 7 was in design flux.

You all see how much it’s changed from 41222 to 41882/41888/41890.

NON BINDING

You can make a backup if you want to but I still need to finalize the scripting.

Scheduled Task – or do it from the shell —

1. Stop Plex
2. command line

sudo bash
cd /var/packages/PlexMediaServer/home
tar cf /volumeX/share_name/PlexBackup.tar “./Plex Media Server”

Yes, a gross hack but does give you a backup.
Yes, you can put this in a scheduled task.

YES, I’ll get packaging updated so start-stop-status can be called in isolation (it currently is bound to the synopkg controller)

EDIT: 4-Aug-2021; Resolved by ""Packaging 2.0"

[ChuckPa]

@geffaoliveira

ONLY this DSM 6 → DSM 7 path is painful.

FROM THIS POINT FORWARD

We return to normal updates / upgrades.

This was necessary because:

(as I point out in the documentation)

1. The username change was forced. Could not access the existing share as user plex. User plex is not accessible to the app anymore.

2. Application storage is now in a isolated spot ( /var/packages/PkgName/home )

3. We no longer have ‘root’ access. DSM is very very strict

4. DSM must grant permission for all requested resources.

[ChuckPa]

@SandmanXX

45-60 minutes is my estimate… Music has a lot of information carried with it in the metadata.

[ChuckPa]

Remember,

There are two phases.

Phase 1 is where you set the Custom permissions to allow PlexMediaServer to have Full Control. This can take a long time by itself.

Phase 2, the actual migration, is when all the metadata is examined, file by file, for correctness . I had to do this because some older agents wrote full path names which don’t migrate. I have to make certain everything, for every possible user, is now relative addressed. It’s a lot of work for a single thread to do. This is what can take the most time.

[ChuckPa]

1. Normal installation is the default.

2. New is literally that — ERASE whatever you have and Start Fresh. (DSM 7 style)

3. Lost Server - For when PMS loses its credentials (which can happen). You don’t need to do all funky stuff at the command line / edit Preferences.xml because I do it for you under program control. You give me the claim-xxxxxx token value from the ‘Get Plex Token’ and I do the rest.

4. One thing I wanted to handle - Installing remotely or across subnet boundaries. The Plex Claim Token method does exactly that. You give it the credentials (which only you can). I take those credentials and marry the server to that account.

When it complains it does not have Full Control, it means the DSM ACL (how this works) isn’t correct. This is part of DSM 6 - 7 migration. It’s the one-time task.

In the future, should you ever restore an old DSM 6 backup, you will “migrate again”.
(messy thought but why it’s there)

[ChuckPa]

1. The default location for all DSM 7 applications is /var/packages/PACKAGE_NAME/home

2. Under this, PMS retains the traditional, Plex Media Server/Logs structure

3. The final path is therefore /var/packages/PlexMediaServer/home/Plex Media Server/Logs

You may be hard pressed to make this work even with this knowledge because of the significantly increased security enforcement in DSM 7.

[ChuckPa]

To All Following Here:

This post is to alert everyone to a major change coming to Plex on Synology DSM 7.

I am going to try providing you with:

1. Revival of the Plex shared folder
2. Storing PlexMediaServer in Plex/AppData/Plex Media Server
3. The shared folder will be created by DSM 7 if not present
4. If present, it will grant R/W access for the Server to run.

Initial testing is successful but further testing is required.

Testing to date has verified:

1. Fresh installation -
2. Reinstalling (not upgrading yet) PMS where the data still resides in the internal storage area.
3. Migrate DSM 5 & 6 using Plex share and plex share.
4. Upgrade with data residing in internal storage area
5. Upgrade with all data in AppData location

I have a few more changes to complete and then general testing (Forum Preview) will be ready.

I will be conducting my own internal testing before posting SPKs for anyone.
The above test points (4 & 5) will be operational when Forum Preview begins.

Would anyone be interested in participating in this testing?

[Gipi49]

Hi @ChuckPa,
will it means that the migration process will be shorter/faster ? Because if you remember one of my post in this tread, my migration is still running since July 12th (Plex shared folder of 433GB …) and I will try anything to revive my Plex library ASAP since it’s my main entry point to my media.
If it can facilitate the process, can you make advices on how to stop the migration process safely without breaking the Plex folder in order to test the new method, or is it to late for me ?

Regards, appreciate your efforts to bring as many mitigation possible with this new DSM7 nightmare