Synology 7 Upgrade - Lost All History

Server Version#: PlexMediaServer-1.24.5.5173-8dcc73a59-x86_64_DSM7.spk
Player Version#:

I have been putting off upgrading my DSM1019+ to DSM7 for obvious reasons. The Plex upgrade path looked much safer these days for I finally bit the bullet and upgraded. Yes, I followed the directions

  • Uninstall old Plex
  • Update DSM
  • Install new Plex

The instructions said to expect a failure the first time due to permissions issues. Mine did NOT. Mine was successful on the first try. Great. However…

Yes it installed to a new directory on my NAS, but it did NOT import anything from my old directory. I have ZERO “watched” history and all that for ALL my users (only three, but not the point).

Can I simply stop the Plex service, rename new “PlexMediaServer” to .bak ro whatever, renamer the old “Plex” directory and assign permissions accordingly?

Thank you.

M.

When you upgraded – Did you click “Repair” or install the Package Center version?

That’s the only way it will give you an empty install.

It’s easy to recover. I only need to know what happened and what state it’s currently in.

I did neither. There was nothing to repair as I uninstalled Plex before the DSM upgrade, and I manually download and installed Plex. I didn’t use the Synology App Store version.

M.

WOW.

Can you tell me what you see in FileStation?

What’s in the “Plex” shared folder?

Do you have a “PlexMediaServer” shared folder ?

I wanted to also add that I am have the same issue as mpalermo73. I just followed the latest instructions and started my install of 1.24.5.5173 about an hour ago. When it came to the step:

  1. The installer will expect the new username “PlexMediaServer” to already exist and have Full Control of the Plex share. It will not so the first attempt to install will fail.
    This is expected.

I did not receive an error and instead saw this:

I continued following the instructions with adding permissions and attempted to install plex 1.24.5.5173 again and received the same install successful screen as above.

After all permissions were changed, I also uninstalled the plex app on DSM7 through PackageCenter using the App Only deletion option. I then reinstalled v. 1.24.5.5173 with the same result.

I currently see the following in the folders:
PlexMediaServer: 1.9 MB with 109 files. AppData is the first subfolder.

Plex: Size is calculating with 70,000+ files and counting. Library and tmp_transcoding are the first subdirectories.

Thanks for any help on this.

@apoptosis81

Please go inspect the Plex shared folder.

  1. Is there a Library folder ?
  2. If so, and you drill down, do you see Plex Media Server ?

Yes, this is what I see:
IMG_9189

Bingo,. it did not migrate.

  1. Package Center
  2. Uninstall w/ Erase option
  3. Install the same SPK again (downloaded from plex.tv/downloads)

A blank (empty) install with no history occurs when either.

  1. PMS from Synology Package Store is installed (that beta is no longer conpatible)

  2. “Repair” is invoked after upgrading from DSM 6 with PMS still installed.

The problem stems from:

  1. The beta stores in the Synology internal area. This wasn’t acceptable.
  2. As of PMS 1.24.2.4973, I was able to make the ‘PlexMediaServer’ shared folder work reliably for everyone (DSM 7.0-41890 was final release status)
  3. Anything caught in the old storage must be moved out from there first – then deleted – to make way for the proper migration from the plex share.

The logic works this way:

Installer looks for:

  1. An existing installation in PlexMediaServer shared folder?
  • Install software only
  • Don’t overwrite the existing data there
  • Exit install successfully
  1. Nothing in PlexMediaServer shared folder
  • Look in hidden internal area
  • Move that to ‘PlexMediaServer’
  • Exit install successfully
  1. Nothing in PlexMediaServer, look for a DSM 6 installation to migrate
  • Validate permissions
  • Process all the internal DSM6 → DSM 7 links and metadata changes
  • Move the files to ‘PlexMediaServer’
  • Clean out Plex-generated files from ‘Plex’ share.
  1. Must be a completely new installation , setup fresh

Thanks Chuck. I did the full erase and attempting to install right now. The install wheel is currently spinning, so it looks like migrating is happening.

Similar to what mpalermo73 said above, I uninstalled the Plex app while still running DSM6. I then updated to DSM 7, restarted DSM7, and then manually installed the new Plex app v.1.24.5.5173 downloaded from the link in the guide. I never attempted to install Plex on DSM7 through the Package Store and never selected a “Repair” option.

I just never got the failure that is referenced in the guide when trying to install v.1.24.5.5173 on DSM7 the first time. I can grab any logs if you are interested to see why migration didn’t seem to trigger the first time.

@ChuckPa I can provide more details from my install, but @apoptosis81 is saying exactly the same thing that I would be.

I have “two” full Plex directories. The old “PLEX” and the new “PlexMediaServer”.

I’m reading both of your updates about uninstall with delete and all that. I can give that a shot after some backup… :smiley:

root@nas:/volume1# du -hs PLEX/ PlexMediaServer/
29G     PLEX
11.1G    PlexMediaServer

M.

That’s troubling to me. If there is an underlying problem, I need to fix it ASAP.

I’ve not made any changes to the scripting for several weeks now (across multiple PMS versions).

Might I ask both of you to SSH into the Syno

sudo bash    
synoacltool -get   /volume1/Plex         (use whichever volume you have 'Plex' on)

I’m looking for this output.

bash-4.3# synoacltool -get /volume1/Plex
ACL version: 1 
Archive: has_ACL,is_support_ACL 
Owner: [root(user)] 
--------------------- 
	 [0] group:administrators:allow:rwxpdDaARWc--:fd--  (level:0)
	 [1] user:plex:allow:rwxpdDaARWcCo:fd--  (level:0)
	 [2] user:admin:allow:rwxpdDaARWc--:fd--  (level:0)
bash-4.3# 

@mpalermo73

You want to keep the PLEX one, right?

I also just found your problem.

  1. You renamed (or moved) Plex and named it PLEX.
  2. The current release of the package doesn’t look for that name.
  • I have a change I sent to QA for that. it’s in testing now.

The solution for you – You’ll laugh

  1. In Control Panel - Shared Folders
  2. Rename PLEX share → “Plex-Temp”
  3. Rename it back to be Plex (exact UpperCase P with lowercase lex)

Empty out PlexMediaServer shared folder -OR- just delete it.

Now uninstall and install again.

The installer will finally find your “Plex” shared folder and migrate

AND

I owe you both an apology… I forgot about that failure case (since it’s not released software yet)

Sure no problem. Should I let my install finish before doing this?

I’m still seeing the spinning installation wheel after doing the full uninstall with erase and manual install. This seems good as the first time I attempted the install it finished in about 15 seconds as it wasn’t doing the migration I assume. Based on my file count, my migration will probably take at least 3-4 hours.

@apoptosis81

If it’s “Installing” then it found your data…

Open a new tab, Open “Plex/Migration.log” in the Syno text editor.

You’ll be able to see where it’s at in the process.

3-4 hours isn’t tooooooo bad. One user endured 2 weeks (480 GB of metadata)

This is what I had to do because , under DSM 7, applications are not permitted to acess the synoshare tool.

    SourceShare=""
    [ "$(echo /volume[1-9]*/[Pp][Ll][Ee][Xx]]/Library/Application\ Support/Plex\ Media\ Server)" != "/volume[1-9]*/[Pp][Ll][Ee][Xx]/Library/Application Support/Plex Media Server" ] && \
      SourceShare="$(echo /volume[1-9]*/[Pp][Ll][Ee][Xx] | awk '{print $1}')"
bash-4.4# synoacltool -get /volume1/PLEX
ACL version: 1 
Archive: has_ACL,is_support_ACL 
Owner: [root(user)] 
--------------------- 
         [0] group:administrators:allow:rwxpdDaARWc--:fd-- (level:0)
         [0] user:plex:allow:rwxpdDaARWcCo:fd-- (level:0)
         [3] user:docker:allow:rwxpdDaARWc--:fd-- (level:0)
         [4] user:guest:allow:r-x---a-R-c--:fd-- (level:0)
bash-4.4# synoacltool -get /volume1/PlexMediaServer/
ACL version: 1 
Archive: has_ACL,is_support_ACL 
Owner: [root(user)] 
--------------------- 
         [0] group:administrators:allow:rwxpdDaARWc--:fd-- (level:0)
         [1] user:PlexMediaServer:allow:rwxpdDaARWc--:fd-- (level:0)
         [2] user:admin:allow:rwxpdDaARWc--:fd-- (level:0)
         [3] user:plex:allow:rwxpdDaARWc--:fd-- (level:0)

I had added the plex user on PlexMediaServer to see if that would’ve helped. It didn’t…

@mpalermo73

PlexMediaServer doesn’t have Full Control. Close but not there.

You missed some of the permissions flags.

bash-4.4# synoacltool -get /volume1/Plex
ACL version: 1 
Archive: has_ACL,is_support_ACL 
Owner: [PlexMediaServer(user)] 
--------------------- 
	 [0] user:PlexMediaServer:allow:rwxpdDaARWcCo:fd-- (level:0)
	 [1] everyone::allow:r-x---a-R-c--:fd-- (level:0)
	 [2] user:admin:allow:rwxpdDaARWc--:fd-- (level:0)

You need to set the permissions again using FileStation.

Here’s the procedure.

Please pay special attention to this step

https://global.discourse-cdn.com/plex/optimized/4X/9/d/e/9de3d74a74ddcbe007e13f0c0b003728941c1f86_2_690x448.jpeg

PlexMediaServer doesn’t have Full Control. Close but not there.

You missed some of the permissions flags.

I didn’t do anything. The initial install did “everything” and was successful the first try. I ran the manual install of PlexMediaServer-1.24.5.5173-8dcc73a59-x86_64_DSM7.spk. With exception of adding the user plex to try and fix it, you are seeing what the install script did.

We don’t use user Plex in DSM 7.

We use PlexMediaServer now. (DSM 7 forced us to change).