You need to follow my instructions.
System error 0 means you missed a step in the “Full Control” permissions.
(probably didn’t Apply to this folder , sub folders, and files)
Don’t forget to uninstall & Erase.
Went through the whole thread, but came back to this as it was the simplest to follow and made perfect sense.
Followed it as expected and everything went perfectly fine.
The only issue I had, was that on step 7. a (Uninstall the failed Plex package - ERASE option), this was not possible as there was no package to install. So, there was a bit of a worried click on the manual uninstall, but everything continued on without issue.
Thank you for your detailed attention to this issue. You’ve been extremely helpful.
Thanks for noting for others.
Some folks manage to get the package installed --in spite of…
I will update the instructions …
having issue with photos only for not loading. System internal user plexmediaserver has r/w access.
Jul 07, 2021 22:44:11.444 [0x7fa429f12b38] ERROR - Failed to create iterator to “/volume1/photo/K”: Permission denied
Jul 07, 2021 22:44:11.498 [0x7fa42b388b38] ERROR - Couldn’t check for the existence of file “/volume1/photo/K/.grab”: boost::filesystem::status: Permission denied: “/volume1/photo/K/.grab”
Jul 07, 2021 22:50:57.768 [0x7fa42c499b38] INFO - AutoUpdate: no updates available
Jul 07, 2021 22:51:03.188 [0x7fa42c342b38] ERROR - Unknown metadata type: folder
You’re getting lockout conflicts from DSM.
It was an issue in DSM 6, now it appears to be a full block.
If you don’t have the Synology apps installed –
As first step:
- Stop Plex
- move all the photos to a different shared folder or sub-folder
- when empty, delete the default photo shared folder
- create a new photo shared folder in its place.
- Grant Internal User PlexMediaServer permission.
- Move the photos back.
- Start Plex
- Cross fingers and hope it works. If not, create a new shared folder for your photos (e.g. “Photos”)
creating new share works but how can i make that default photo folder for synology photos. synology photos defaults to system folder photo
If you recreated the photo share, does DSM still prevent Plex from reading it?
( I did something like that long ago. If I remember correctly, creating a new one fixed it for both).
I can understand if it’s a problem.
If it doesn’t work right; Delete the empty share, reinstall photo station and let it create the shared folder. (I saw video station do the same tonight)
All my content was unavailable due to this file permissions issue. Finally up and running.
Can’t find how to pm on here @ChuckPa so let me thank you wholeheartedly for all your support here. Just amazing and a credit to the wider Plex team.
I turned off PM so that my haters couldn’t message me
Glad it’s working
1 Like
Hi Everyone,
I upgraded dsm yesterday and followed the permission instruction issued by the team. It all went well.
The plex installer has been “installing” for 14h now, after a 10h attempt yesterday. Hard to see what is being done and, based on the 500-1000 item per minute documented above in the thread, it should be finished long ago (8h based on the number of items I have).
Looking at the resource monitor, I see that Postgres (internal service) continues to work. Is it the one involved in the plex migration process? If not, what should I look for? Many other files indexing processes are working in parallel (photo, cloud, audio and video), so that those may have slowed the plex install…
Thanks for your lights 
Arnaud
I had one user run 16 hours and was ALMOST done when we interrupted it.
In the Plex share — “Migration.log” will show you what’s happening.
What it’s doing now is –
For every metadata file you have
- Check if it’s a Link (from the old agents) - change the link to new format.
- Change all the file permissions.
I estimated 2 minutes per 1000 metadata files.
this means, at this rate, all files included, you have some 850,000 metadata files ?
( A big library – a lot of indexed items ?? )
do not fear..
- It will NOT hang
- It WILL finish
If you got all the permissions right .. it’ll be good.
If you missed something , you will probably get “System error 0”.
If that happens, go through the most important steps again..
( Look at this post – This is the important one )
https://forums.plex.tv/t/synology-dsm-7-release-plex-installation-issues/719845/596
If you need to do that…
- Do the permissions manually
- try installing again.
- If it fails to migrate
a . – Verify data still in the Plex share
b. – uninstall with ERASE option
c. – then install again.
DSM 7 is a very “Detail Rich” migration process. It’s is a one-time ordeal.
I tried my best but this is the best I could do.
1 Like
My migration went well, all libraries working perfectly except for Photos, which is pointed at /photo folder that is controlled by Synology Photos…
Is there any way to make that work?
PlexMediaServer internal user has read and write permissions to the shared folder, but still nothing. I cannot edit “custom” permissions for photo shared folder, assuming because the permissions are controlled by Synology Photos. But within Synology Photos, I gave “Plex” user Management permissions, but I cannot assign permissions to “PlexMediaServer” internal user as it is missing from the user dropdown list.
Any help would be appreciated!
Just for the sake of clarity is it safe to remove the plex user and shared folder once migration is completed?
I just did the migration, it worked as described here - after I set the necessary permissions for the internal system user PlexMediaServer the installation went on and completed successfully - I didn’t get any indication that the metadata was migrated but it’s all there and working - in the old Plex metadata folder is only the Migration.log.
Thanks a lot for the extensive support!
Finally three questions:
- does the system user PlexMediaServer need write access to the folder with the media or is read access sufficient (as I had with the DSM 6 version)?
- I can safely delete the old Plex user?
- how do I secure the metadata in the future? With the Synology Hyperbackup where I have backed up the Plex folder so far, this no longer works…
@ChuckPa Just followed your instructions, From DSM 6.2.4-25556 to DSM 7.0-41890 using PMS 1.23.3.4707-ebb5fe9f3. Everything worked a treat! Love your work and the details provided!!
@MikeDelta and All following here:
-
I’m waiting to hear back from Synology about connecting PMS to HyperBackup as a registered app/source.
-
Independently, I’m working on a script/Scheduled Task to use in the interim.
-
I’m chatting with Engineering to see how we can do something for Synology which is
a. Platform agnostic
b. Built into PMS so it runs as “program code” and not “script code”.
1 Like
Hi @ChuckPa After issues where no TV recordings were stored and existing videos could not be deleted through Plex clients (despite correct permissions for PlexMediaServer account rights on the Video share and the Plex share),
I decided to do a fresh installation (uninstalled Plex, removed Plex account, deleted the Plex shared folder, installed PlexMediaServer-1.23.4.4775).
Now I ended up with Plex package showing “running”, but the Plex shared folder was not re-created (not show with shell ls either), and plex server cannot be reached (I guess it’s not really running).
Retried several times cleaning and re-installing - but without success.
P.S.: Please apologize if this post is at the wrong place - I am new here.
Hi!
Trying to install Plex 1.23.4.4775 into DSM 7.0-41890 and getting an error the package requires DSM 7 or older.
Already removed the Plex from DSM6, reboot the Synology, downloaded the package again from Plex…
Any idea how to proceed from here?
Thanks!
The design of DSM 7 changed. Plex on DSM 7 changed with it. (we had to)
- There is no “Plex” username anymore
- There is no “Plex” shared folder anymore
If you’re trying to force a full restart from scratch –
- Install the DSM 7 package one last time
- Uninstall – Select the ERASE option.
The package scripting menus have control of the cleanup for you.
You only need let the NAS run long enough to complete removal of the old data before shutting it down for complete cleanup.
You can install a fresh DSM 7 installation while the old is being removed.
I expected that could happened and planned for it.
