Server Version#: 1.24.2.4973-7000
I’ve had various versions running on DSM7 for a few months and it’s been fine. I generally update it whenever one is available. Have a DS918+
I saw 1.24.2.4973-7000 is now available so went through the normal Manual Install update process.
This time it is stuck on the Updating window. The circle is still spinning but it’s been like this for an hour now. What can I do?
Nothing to worry about – but yes it’s annoying.
There have been a few cases where DSM puts the new “PlexMediaServer” shared folder on a new volume -or- is copied instead of moved.
I do not yet understand what triggers it.
In my scripting, I tell it to move. DSM has decided to copy then delete. NO idea why.
All I can say is to let it finish. You will not lose data
BUT
you might lose data if you interrupt / reboot the NAS.
I am sorry about this. This part is out of my control
Same issue here. I just updated to Plex Media Server 1.24.2.4973 on my DS920+ and it’s stuck on updating as well. I can see the NAS is writing a a bunch of data to the HDD.
Very strange behavior.
I saw the same issue on my instance, took about 20 minutes to complete the update working fine now. It was notable because usually the upgrade takes only 90 seconds for me when I do them.
For reasons I do not understand,
The script performs a ‘move’ operation (a rename) to place the hidden server info into the new “PlexMediaServer” shared folder which exists on the same volume.
I do not understand why, for some, that becomes a COPY operation. I’ve not yet determined the pattern.
If anyone can look at
Where PMS (the package) is installed (Package Center)
Where the PlexMediaServer shared folder gets created (Control panel)
If they are not the same, – PLEASE ping me ?
Thanks
Mine took awhile but totally worth it now that I can use Hyper Backup again!!
Rechecking something… give me a minute please
Nope. I cannot break it.
Moved all my data back to old internal struture
PMS data on volume 2 ; Attempt to Install to volume 1 ; Flagged as wrong volume
Installed 1.22.3 (old structure) on volume 2; picked it right up
Upgraded to 1.24.2.5000 - boom & done. new PlexMediaServer share created and populated.
Still need to figure out what condition I’m missing.
I’m here experiencing this (or was… it finished while I was writing this message). In case it’s helpful, the move command I see (saw) running is:
mv /volume1/@apphome/PlexMediaServer/Plex Media Server /var/packages/PlexMediaServer/shares/PlexMediaServer/AppData
The PlexMediaServer folder gets created on Volume 1 (the only volume I have).
Everything seems fine and running now. Took about an hour to complete.
This is a huge mystery and , I suspect, a DSM 7 bug.
Standard linux rules:
So what’s what’s DSM 7’s problem? 
I believe everyone but I’ll be darned if I can recreate and capture it.
Trumpy has an idea – investigating
Hello, the upgrade on my DS920+ took about 15 minutes to complete.
I don’t think that Plex Media Server folder was visible there before the upgrade and although I told it to keep the Plex_Logs location I had before, it created a log folder under PlexMediaServer\AppData\Plex Media Server\Logs.
I suppose if I don’t see new logfiles written to my Plex_Logs location but into the new location I may delete the Plex_logs folder? I’ll keep watching the coming days where he writes his log files.
All seems to be running fine though.
Hope this helps 
I have also updated to 1.24.2.4973. It finished in about 10 minutes on my DS1520+.
The command was also a mv command so why it’s copying the files first and then deleting, I don’t know.
Is it possible that Synology somehow treats it as a different volume (even though it’s not)? Perhaps due to differences in mounting points? Perhaps doing a mv "/volume1/@apphome/PlexMediaServer/Plex Media Server" "/volume1/PlexMediaServer/AppData/Plex Media Server" might give better results? Or is this impossible from inside the installer? I don’t know how Synology mounts all the folders & devices.
No problem! Hope you can figure it out. 
In any case, I have a rather big Plex-folder due to lots of index and chapter files and it went quite fast, so I’m happy!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
