Question regarding updating from DSM6 to DSM7

I’m currently running DSM6 on my 2 NAS devices and want to upgrade both to DSM7. I’m reading through this guide, but what I don’t see mentioned; do I have to uninstall Plex before upgrading to DSM7, or do I just start the upgrade, let it run, and follow the guide from there?

Wanting to make sure nothing goes wrong, so trying to plan ahead :slight_smile:

@MrWaxWeazle

Preference is to Uninstall the DSM 6 app before the upgrade

When you do this, the how-to and screenshots will make more sense.

1 Like

Gotcha, thanks!

Is it best to back-up the Plex folder before starting as well, or is that not necessary?

I didn’t get any error messages as shown in the guide.
I only got the above screenshot.
Though, after installing and changing permissions as mentioned in the screenshot, do I just configure the server again through the PMS package, or should it automatically pick it all up like before?

After installation, and without configuring the server again, the media from this NAS is not showing on my Plex.

Go look in the Plex shared folder.

When the installer can’t see your DSM 6 installation, it creates a new DSM 7 installation ( there won’t be any errors on a fresh install )

Do the following:

  1. FileStation
  2. Plex shared folder
  3. Navigate Library/ Application Support / Plex Media Server

If you can do that --AND-- you see all the metadata folders

then, nothing migrated (which is normal situation until we give permissions to)

I can indeed access all that and it’s all there. How do I properly trigger the migration now? Is it the reinstallation part, or is that not necessary considering I didn’t have the aforementioned error message in the guide?

Let me get you the instructions… ONE SECOND please :slight_smile:

Here’s the instructions. (a lot of what I’m writing is already spelled out in the FAQ)

  1. Stop Plex
  2. Uninstall the DSM 7 Plex app — choose the DELETE option
    – It will empty the new PlexMediaServer shared folder and make it ready.
    – We are deleting it because it’s rogue. We want the package installer to move all your existing data to DSM 7 as it installs again (it does this by default)
  1. Now, starting with “Scenario 2”, scroll down and you’ll see where you grant Administration (ALL), Read(ALL), and Write(ALL) permission to “This folder, sub-folders, and files” for EVERYTHING in the Plex shared folder (where your existing metadata is)

  2. This will take time to complete – dependent on how much media you have indexed.

  3. It’s of paramount importance that “PlexMediaServer” show as having Full Control of all files in the “Plex” shared folder before we start installing the DSM 7 app again.

  1. Once you’re sure you’ve got all the permissions right, Go ahead and install the DSM 7 Plex app again. “Normal installation”.

  2. It will sit at “Installing” for a while. (about 3 minutes for each 1000 files you have indexed into PMS)

  3. Don’t refresh the page or restart the Syno – it’ll make a mess

  4. Instead, open a new tab to the Syno,

  5. Go to the Plex shared folder.

  6. you’ll find (after about 3 minutes), the file “Migration.log”.

  7. This is where the installation writes all the progress for each step of converting your DSM 6 metadata & configuration to the new DSM 7 version.

  8. When Installation is complete, you will find that “Plex/Library” is gone.

  9. All your metadata will have been moved to the “PlexMediaServer/AppData/Plex Media Server” structure.

Be patient. Pay attention to the mind numbing details.

Don’t hesitate to ask questions… Just don’t panic

1 Like

@ChuckPa

First NAS worked like a charm! However, my second NAS (with my TV shows on it) is running into an issue.

I’ve installed everything and the migration seems to have gone well?
Though - I can’t access the TV shows on my Plex, nor can I open the app from my NAS; it shows me the following XML file.
I do have a lot more files for my TV shows, but I do believe migration is already finished…
Migration.log (693 Bytes)
migration."

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Response code="503" title="Maintenance" status="Plex Media Server is currently running database>
<link type="text/css" rel="stylesheet" id="dark-mode-custom-link"/>
<link type="text/css" rel="stylesheet" id="dark-mode-general-link"/>
<style lang="en" type="text/css" id="dark-mode-custom-style"/>
<style lang="en" type="text/css" id="dark-mode-native-style"/>
<style lang="en" type="text/css" id="dark-mode-native-sheet"/>
</Response>

@ChuckPa

A little update; I’ve done a bit more looking into it, and I’ve come across the realisation that it manually stops the server every time after I try to open it.

I’ve tried reinstalling a few times (with KEEP option); sometimes I get the XML file I mentioned in my previous post, and other times it just says “refuses to connect”. I’m not entirely sure what’s causing the issue though. I’ve not found a solution as of yet.

The migration completed according to the migration.log file.

If you get the 503 Maintenance message, “Plex Media Server is currently running database,” then let it continue.

Plex is updating the database structure, which is common when PMS updates, and it is taking awhile.

If you stop Plex Media Server before the task completes, it will start up again the next time you start PMS.

If you are jumping between PMS versions, you are just making the task take longer (and possibly risking db corruption), since Plex as to start from the beginning to adjust to the db format for that version.

Unfortunately, the web page does not auto-update when the task is complete. You can try reloading the page or closing / re-opening the browser.

The process should take just a few minutes.

If after ~10 minutes you still cannot access Plex Media Server, then stop PMS, using File Station, navigate to the Plex Data Folder, compress the Logs directory, and attach the ZIP file to the thread.

1 Like

Ahh… Thanks for the info!

I’ve let it run for half an hour in the past few hours, but it was still not running. Once again tried reinstalling it and got the same message - however, this time, suddenly it started working perfectly fine :slight_smile:

Thanks for the help both! :smiley:

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.