Chuck: I have been following your Forum updates since you began them a few weeks ago. I am aware that the Releases you have given us via the Forum are NOT the “official” Plex releases and that any previous official Plex release could “break” your release if we try and go back to (install) the official Plex release (hope that sentence makes sense?).
But… this morning I noticed your most recent Release listed in the forum is 1.24.0.4921 (which I haven’t applied yet - I’m still on 1.24.0.4897) … This morning I also got a new Release notice through the Plex app on my Synology NAS that is listed as 1.24.0.4930 … and checking on the Plex.TV site, this same version is now listed as the newest “official” version.
My question: Is the 1.24.0.4930 official Plex a version that now incorporates all your fixes (e.g., making the PlexMediaServer visible and allowing Hyper Backup backup) and I (we) should now go to this version OR should I currently still install your version on the Forum (1.24.0.4921)??? I don’t want to break what is already fixed through your Forum releases??!!
Let me add to others who have praised you for ALL the work and “quick” fixes you have provided through the Forum. Like you, I am an “old” IT guy (me trying to be self-deprecating) now retired and based on all my life experience it is GREAT to get the service/support and quick turnarounds that you have provided us via the Forum!!! It’s NOT typical to get the “quality” of support you have provided us from most IT vendors (Support Lines, Help Desks) in today’s world!!! THANKS it is greatly appreciated!!
It looks like Engineering is rolling versions faster than I can keep up!
I will update yet again , OEY!
I’m sure you’re all aware of that “Crusty Old Guy” you’re afraid to or don’t want to talk to but are glad you did? That’s me!
I’ve been an engineer for 40 years now (HW & SW primarily with a whole lot of Systems Architecture & Systems Engineering) along the way.
Calling me an “I.T.” guy is not where my forte is. Embedded and on the platform is home for me whether that platform be sitting on the desktop, rack next to you, in the air, or in orbit.
I looked at the changes in this update from Engineering.
I will get a new update put together for everyone ASAP
my dumbass upgraded to the official build over the last forum preview and had to setup as a new server and I then removed the old unreachable one before I realized what I did -__-
oh well, band-aid has been ripped off, I’ll await for this to reach official branch and just stick with metadata inaccessible for now, start backing it up once this hits mainline
@ChuckPa disable upgrades or upgrade checks/notifications or something for you forum builds if you can would be my advice for others (aside for users to pay attention to what they’re doing )
What I would suggest for anyone who’s using the package that Chuck has uploaded here, is to use HyperBackup to make a backup of the PlexMediaServer shared folder so that if something does go sideways after, you can actually restore your data. If you’re not familiar with HyperBackup, it will allow you to back up files/folders to another NAS, a rsync server if you have one, an external USB drive, Synology C2 cloud, various destinations are available. I’d strongly suggest everyone make a backup when they can. I’ve tested making a backup, blowing all my libraries and metadata away and doing a restore - it does work correctly so I’d advise everyone to take advantage of this ability.
@philrigby yeah it’s not the end of the world - I had redone my server intentionally from scratch last year about and hadn’t had it all set back up (customization wise) since then - losing all my playlists (music and video) I had made since hurts though
I think I understand but just to confirm: The Version 1.24.0.4930 that you have now updated here on the Forum is NOT the same as the 1.24.0.4930 version that can be found on the Plex.TV website. Is that correct?
And because your Forum website version makes the PlexMediaServer folder/files visible (only with Admin User) and (I assume) the current “official” Plex.TV 4930 version does NOT make it visible WE SHOULD NOT UPDATE to the PLEX.TV version of 4930 BUT we should ONLY USE your 4930 version?? Updating to the Plex.TV 4930 version would only corrupt the fixes you have given us? Is that correct?
Finally, I think you previously said in the Forum that eventually your version which includes making the PlexMediaServer visible WOULD BECOME PART OF the OFFICIAL Plex.TV version releases … in other words, the official version and your version would eventually merge together and then there will only be one version and we would go to the Plex.TV website for future version updates from that point on as opposed to coming back to the Forum?? Is that correct?
Yup that’s pretty much all correct. Until Chuck announces otherwise, get your downloads from here as the new shared Plex folder parts aren’t in the official downloads from plex.tv yet. He’ll let us know when they are then we can go back to “regular” downloading.
I took the plunge with DSM7 upgrade this evening and got Plex working, with this forum preview packaging version, with very little issue - probably mostly because I have had weeks of background knowledge gathered from these forum posts.
My high level steps were:
Uninstall Plex from within DSM6
Download and install DSM7 (and wait for it to finish)
Install Plex for DSM7 (forum preview packaging .4930)
Interestingly this installed within a minute or so and there were no red error messages raised about permissions, only the blue message at the end of the install regarding granting PlexMediaServer user to media shares. Plex was happily running afterwards and the PlexMediaServer share had been created. However no migration had occurred - I knew it couldn’t have because I hadn’t set any permissions, so…
Uninstall Plex for DSM7 with full erase option.
Grant PlexMediaServer user the custom permissions to the Plex share, plus my media shares.
Install Plex for DSM7 once again. Migration happened this time, took about 20-25minutes.
@ChuckPa Just a quick message - no issues, no complaints, only a thank you. You’ve worked tirelessly to get this sorted for us all with amazing patience. That in the face off challenges arising from Synology’s new security structure alongside putting up with complaints and demands from some forum members. Great job done, it’s very much appreciated.
Thanks so much for all your work. I have really struggled since upgrading to DSM 7. I blindly did it, not considering how it might not be friendly to my Plex set up, so I wasn’t aware of the correct process for upgrading and migrating. I don’t know exactly what I did initially, but I have never been able to fix it and get it to migrate my Plex Media Server files over. I have the correct permissions as far as I know now, but it will not recognize my original Plex Media Server files and always wants me to add libraries and then it scans new metadata instead of migrating what I already have in my Plex share.
I was hoping I could install this version and manually copy my Plex Media Server files from the Plex share (PLEX/Library/Application Support/Plex Media Server) to this new location and that it would play nice, but I have hit a snag. It seems the install goes well and is running fine. I stop the server and copy/replace the Plex Media Server files from the Plex share. Once the files move over, I reset the Synology and then run the server again. For some reason, though, it keeps stopping itself about 10 seconds after it starts. It will say “Manually Stopped” even though I didn’t do anything to stop it. I click “Run” again and the same thing happens over and over. If I click “open” in that 10-second time window, it will open a new tab and say “This site can’t be reached” and that the address “refused to connect.” I can’t figure out what is going on and would very much appreciate some guidance. I am a relatively new Synology user, so I am a little inexperienced with all this.
Thinking you can outsmart the installer was not the correct decision here.
Clearly, you don’t have it right.
It has taken months to develop the scripting to get everything right for the DSM 7 platform environment which is radically different than DSM 6. (I have been working on this effort for 13 months now)
If you will kindly:
put all the files back in the “Plex” share in the proper structure
Uninstall , using the erase option
Install again and allowing a normal migration to occur
If, upon starting, the server cannot be found in Plex/web (don’t forget the CTRL-F5 refresh), we will reclaim it
Reclaiming:
Uninstall + KEEP option
Reinstall the same package + Plex Claim Token option
a. Click “Get Claim Token”
b. COPY claim token to browser
c. PASTE into GUI window
NEXT
Continue and let software reinstall and claim the server
15-20 seconds later, PMS responds with message confirming claimed status.
Thanks for the help. I have never been able to get it to conduct a normal migration. I haven’t touched my Plex share folder, so it should be in the proper structure as far as I can tell: /volume1/PLEX/Library/Application Support/Plex Media Server. I’m not sure why it isn’t getting detected…
Well, I think I just figured it out. It’s because my Plex share folder was in all caps: “PLEX.” I didn’t realize that the capitalization mattered. It came to me as I was typing it out. I think I followed a YouTube video when I set it up originally and they had it in all caps, so I thought that was the thing to do. I changed it to “Plex” which seems to be allowing the migration to happen, since the install is taking much longer than before. My Plex Media Server files are a pretty good size, so it’ll probably take awhile. I’ll update this if I run into any more issues, but I don’t think I will.
I wish I had thought of that sooner. Oh well, at least it was a simple fix, and I’m so glad I don’t have to start all over again with my metadata. Now to make sure it gets backed up.
Thanks again for your prompt help. It sounds like getting this all to work has been a bit of a nightmare for the past year+. Please know it is very appreciated. Cheers.
)
