not yet where I live. My DS418j development system does not see it.
No longer applicable.
41890 is now available in Eastern Europe too. Docker almost looks more appealing, though.
1 Like
I have an idea…
As first step –
- Restart DSM
- Verify you still don’t have a ‘custom’ permissions button for the Plex share.
- Create a new shared folder –
Plex2 - Give it basic - normal permissions as you create it.
- After creation – Verify it has a
custombutton. - STOP, do NOT continue if it does not – that’s a DSM bug.
- rename “Plex” share to be “Plex-old”
- rename “Plex2” share to be “Plex”
- Move the contents of “Plex-old” to “Plex”
- Now remove & ERASE (uninstaller option) the existing DSM 7 installation.
- Install DSM 7 package and follow the instructions.
NOTES:
- Moving the contents of the Plex share will take time because DSM likes to “Prepare”
- The migration itself will also take time.
Would you still recommend holding off on upgrading to DSM 7 RC?
yes yes yes
hurray
It works.
this process has worked.
Thank you thank you
For all the joy, unfortunately I can not load the old settings. Is there still a possibility?
“Old Settings” ???
Everything which was in the “Plex” shared folder has been migrated.
Whatever you had before – you have now.
All migration did was:
- Make certain old agent errors were corrected.
- Ownership changed from
PlextoPlexMediaServerper new DSM rules. - All data moved.
If, somehow, it does not see you as the owner, the fix is simple.
- Uninstall & KEEP all data.
- Re-install, using the “Use Claim Token” option.
- The installer will communicate with Plex.tv and establish you as the owner again.
Again, many many thanks.
Now it works again.
I have currently installed the version 4707.
Everything is great.
Thanks a lot
Procedure
- Uninstall DSM 6 package first
- Upgrade DSM to DSM 7
- Restart DSM after upgrade completes
- Install Plex and “migrate”
- Read about all the changes in DSM 7
So it is ok to update to Version: 7.0-41890 from DSM 6 with those steps? Seems simple enough?
1 Like
Hello,
I have updated to the version DSM 7.0-41890. Unfortunately I read about the problems here in the forum only afterwards.
The migration from Plex worked and most of it works. Music and videos I can play.
However, I have a problem with the photos. The folders and previews are displayed correctly. But when I try to view the image large, the image cannot be displayed. I suspect a problem with permissions. The shared folder photos has the permission plexmediaserver. What else can I do?
I guess that in Synology Photos I also have to share the internal system user “plexmediaserver” again. But there I can only manage normal users.
A new migration is not possible, because I have already deleted the old Plex folder (I have noticed that with the pictures in large only later).
Thanks
Christian
Looking at the Release Notes for 41890, not a whole lot has been changed (at least from what they’re publicly saying, anyway).
Because of all the changes occurring for DSM 7,
I suggest you use File Station to manually reset the permissions for all the photos.
They sometimes retain the wrong ownership even though the parent shared folder has permission. (this happens fairly easily when copying photos over from a Mac or Windows).
In DSM 7, we CREATE (add) user PlexMediaServer permission for it.
Please look here.
Don’t forget the Apply to this folder, sub-folders, and files button.
I have searched for a long time. For me, the change screen for the permissions looks different.
But now it works:
- the filter must be changed from all to any. Only then you can see the user plexmediaserver.
- the photo folder had to be converted to Windows ACL. Only then you can change the permissions in the filestation. ( Earlier the permissions in the photostation had to be adjusted).
@Christian58, it’s been noted in other posts that using Synology Photos in Plex doesn’t work properly due to the way it handles permissions. You may break Photos by trying to get them to show in Plex.
Hi,
I have successfully installed(updated) Plex on DSM7 via (Beta Channel in Package center).
It is Version 1.21.0.3744, can I update it manually or it will break?
Thank you
If you previously performed the full migration of PMS from the old Plex share to the new DSM 7 structure –
Yes, you can perform a normal package upgrade.
You only need to be concerned if PMS still has metadata (the “Plex Media Server” folder still exists under “Library / Application Support”)
2 Likes
Hi, I have a higher version of plex something 1.22.x, it will be fine to upgrade to dsm7 version? Or it will break something? Thanks
A higher version than 1.23.4.4712-1f0ed4aea ?
Ignore the Synology Package Center .
It has not caught up yet.
Download from plex.tv/downloads and perform a Manual Install.
Ok. Thanks.
1st off; upgraded to DSM 7 this morning and that was fast and easy other than a couple of weird proxy shenanigans with some Docker containers that have nothing to do with Plex. Upgrading Plex went smooth as silk per instructions above, and it’s running better than ever. I swear it seems 2x as fast to load my libraries now. Maybe it’s in my head but either way I’ll take it.
My actual reason for posting though… mentioned above - Backup and Restore is on the agenda.
I had been using Hyper Backup via Synology to backup my Plex install, since I use it already to back up assorted shares to B2 storage. Since Plex had to move to the @apphome directory which can’t be seen in the share list, any chance it will be approved as an “Application” via Hyper Backup in the future?
Alternatively, any non-binding info to be shared regarding the backup method(s) being explored?
Thanks for being so responsive and helping us with this DSM 7 upgrade!
I am also looking into installing DSM 7 and while reading the instructions in the other thread that you linked, I could see that one of the changes to PMS was removing the ability to run plug-ins. I am not a huge Plex power-user, but I enjoy Sub-Zero plugin for automatic subtitles download for newly added media. Does that change apply to Sub-Zero plugin and if yes, is there any workaround to get it running again?
