Wuerde ich niemals denken! 
I have DSM 7 support, currently running 1.23.5.4717
Living on the razor blade ? LOL
Exactement! Mais la confiance règne, pas de soucis.
Thanks for clearing this. So i cannot use plex at this moment. And have to wait for a new release of DSM 7.
Here are my proposals for the sections relevant to DSM 7 I could identify.
I have replaced some correct french words/sentences by the ones used by DSM 7 for proper match and I have also provided more details where I found the current translation too short to be clear enough.
Text to remove is stroked, text to add is in italic::
Post Install/Upgrade/Migration - Installation complete media permissions reminder
“M-Install-Complete-Check-Permissions”) # (dsm-migration-tool)
{
echo “
Remarque: Si Plex ne peut pas accéder à votre média, vérifiez que l’utilisateur PlexMediaServer est autorisé dans le Panneau de configuration.
”
echo “Définissez les droits d’accès à vos dossiers multimédia partagés en procédant comme suit:
”
echo “1. Ouvrez le Panneau de configuration et sélectionnez Dossier partagé
”
echo “2. Sélectionnez le dossier partagé qui contient vos médias et cliquez sur Modifier
”
echo “3. Cliquez sur l’onglet Permissions
”
echo “4. Dans le menu déroulant, remplacez Utilisateurs locaux par Utilisateur du système interne
”
echo “5. Cochez la case Lecture/Ecriture de l’utilisateur PlexMediaServer.
”
echo “6. Cliquez sur le bouton Sauvegarder pour confirmer les nouvelles permissions.
”
echo “7. Répétez les étapes 2 à 6 pour chaque Dossier partagé auquel vous voulez que Plex Media Server accède.
”
} >> “$SYNOPKG_TEMP_LOGFILE”
;;
Postinstall/Postupgrade - LogPathname cannot be written to
“M-LogPath-No-Write-Access”)
{
echo “
ERREUR: impossible d’écrire dans ‘$2’. Vérifiez le chemin d’accès et les permissions. Veuillez réessayer.”
} >> “$SYNOPKG_TEMP_LOGFILE”
;;
Postinstall/PostUpgrade - Log option selected but no path given
“M-LogPath-No-Path-Specified”)
{
echo “
ERREUR: option de journal sélectionnée, mais aucun chemin d’accès n’est proposé. Veuillez réessayer.”
} >> “$SYNOPKG_TEMP_LOGFILE”
;;
# Preinstall/Postinstall - DSM 6 upgrade - Do not have Full Control of the shared fold
“M-Preinstall-Check-Failure”)
{
echo “ERREUR: les vérifications de préinstallation ont échoué.
”
echo “
ERROR: PlexMediaServer n’a pas le Contrôle total du dossier multimedia partagé existant.
”
} >> “$SYNOPKG_TEMP_LOGFILE”
;;
Thank you for those.
Would you please confirm I have them correct now?
Red = old
Green = updated
Would you please write them out so I may copy/paste?
I do not have a proper international keyboard here.
Here they are:
echo “Définissez les droits d’accès à vos dossiers multimédia partagés en procédant comme suit:
»
echo “4. Dans le menu déroulant, remplacez Utilisateurs locaux par Utilisateur du système interne
»
echo “7. Répétez les étapes 2 à 6 pour chaque Dossier partagé auquel vous voulez que Plex Media Server accède.
»
echo “
ERROR: PlexMediaServer n’a pas le Contrôle total du dossier multimedia partagé existant.
»
Thank you !
changes complete.
I will include them when I next update the Synology packaging.
(package development currently suspended due to DSM 7 feature instabilities).
I checked via SSH and the Plex shared folder is owned by plex with group users. I am logged in as user dave which is an Administrative user, but not the admin account.
Still, I cannot see the “Customize” button.
However — and perhaps this is a valuable data point (or not?). Whenever I modify the permissions on the Plex folder, I get the message that it is part of the Shared Folder Sync service. Maybe that’s part of my issue (and perhaps others)?
@DaveTheNerd You’ve clearly not read the following :DSM 7 - Plex Media Server forum preview
Shared Folder Sync service is something new in DSM.
It might very well be part of the problem.
Also, my procedure was written as installing from the admin user account (or user which you used when initially installing DSM.
For some strange reason, DSM treats Admin versus “Admin privileged users” differently. I’ve not yet isolated the difference but Synology has told me the “Customize” button is made visible to those Usernames which have the appropriate privilege level. This clearly is a “DSM privilege level” issue (which they’ve changed for almost everything)
I did read it, I promise! 
Now, perhaps I didn’t understand it properly, but I did read it. Is there something specific you’ve identified me missing? I really could use the assist!
Thanks, @ChuckPa. I originally tried with my dave user, which is the one I used to upgrade DSM. I disabled the admin user a month or so ago when DSM6 started pestering me about the security risks. So my first attempts at installing/upgrading were definitely with the same dave user that I used for the DSM7 upgrade.
Still, I can’t get the “Custom” column to appear. It appears for other Shares, just not the Plex share. Is there a workaround that I can do, even from SSH?
I have disabled Shared Folder Sync for that folder (and others, too). Didn’t seem to make a difference.
I think I just figured it out.
I will avoid pulling out the whips and chains for the guilty parties 
IF ACL’s have been broken on the Plex share (was set with chmod)
- there will be no customize
- DSM 7 migration will fail in all cases until ACLs are rebuilt.
THE CAVEAT
When DSM 6 installs, I reset the ACLs.
If they get broken again after (manually modified)
then I have no privilege to fix it under DSM 7.
THEREFORE
-
This is the test I am looking for:
synoacltool -get "$SYNOPKG_PKGDEST_VOL/Plex" | grep "user:PlexMediaServer:allow:rwxpdDaARWcCo:fd--") -
Remedy of this should therefore be (as ‘root’ user):
# Set the ACLs to standard
synoacltool -del $PLEX_LIBRARY_PATH
synoacltool -add $PLEX_LIBRARY_PATH group:administrators:allow:rwxpdDaARWc--:fd--
synoacltool -add $PLEX_LIBRARY_PATH user:admin:allow:rwxpdDaARWc:fd--
synoacltool -add $PLEX_LIBRARY_PATH user:plex:allow:rwxpdDaARWcCo:fd--
Notice how, under DSM 6, I set a very broad ACL for the Plex share ?
This is what gives me the foundation to work from under DSM 7.
When chmod xxx /volumeX/Plex is done, it breaks the ACLs.
1 Like
To all following here:
I would like to ask:
- If I back ported the DSM 7 storage structure to DSM 6,
- Implemented the DSM 7 GUI and multi-language support
- Such that migration into DSM 7 were already prepared
would that be desirable ?
2 Likes
Ahh! Ok. this makes sense. When things weren’t working, I used chown to recursively change the owner of Plex to PlexMediaServer.users, and that STILL didn’t work. But that’s because you’re looking for ACLs (which didn’t exist) instead of “raw”/linux ownership. And that’s fine.
I used your four commands plus one other (replacing $PLEX_LIBRARY_PATH with /volume1/Plex on my system):
synoacltool -add $PLEX_LIBRARY_PATH user:PlexMediaServer:allow:rwxpdDaARWcCo:fd—
That still didn’t work, though, but I found this article which indicated I might want to recursively apply these ACLs, so I used these two commands:
cd /volume1/Plex
find . -execdir synoacltool -copy /volume1/Plex/ {} \;
That took a while, of course, but then after that I ran the installer (which also took a while) and… boom! I’m up and running.
Assuming this all works correctly, is it safe to assume that my new/active Plex data is in /volume1/@apphome/PlexMediaServer and that /volume1/Plex will no longer be used (and I can remove it?). I see from the Migration.log file that it has been “cleaned”.
Thanks!!
