Another botched DSM6 to DSM7 upgrade

Hi All,

A while back I incorrectly installed the Package Center’s Beta on our Holiday Home’s Synology NAS which ran DSM7. It worked but I have never been able to upgrade the package. I’m keen to do this now and fix the error.

I’ve followed a number of guides on here unsuccessfully:

I have completely erased Plex (non-recoverable) as the watched metadata is not important.

I have followed the instructions in link 1 about (ie: sudo bash) however the step which should take time - completed very quickly.

I have tried to fresh install with 1.30 and also 1.29 from the second link but the manual install fails each time. In fact it freezes the NAS.

I’m lost as to what to try and do next. Is there code to just completely delete everything related to Plex via SSH?

Model: DS415+
DSM: 7.1.1-42962 Update 3

If you had PMS 1.21.0-3744 (beta) running with DSM 7, you did not botch the DSM 6 to 7 upgrade. Plex was working. You were just running an old version.

When you uninstalled Plex with the erase option it should have removed the program and the Plex Data Folder from your system.

Please do the following:

  1. If any version of Plex Media Server is installed, uninstall it with the erase option using Synology Package Center.

  2. If the PlexMediaServer shared folder exists, delete it via Synology Control Panel → Shared Folder.

  3. Reboot the NAS.

  4. ssh into the NAS.

  5. sudo bash (become root)

  6. cd /volume*/@apphome/PlexMediaServer

  7. ls -l (list the contents of the folder)

  8. Is there anything in the folder? If so, please paste the listing into the thread, supply a screenshot, etc.

1 Like

Ok - good to know. The Package Center Beta is what I was r

Hi @FordGuy61 - followed all steps and came back as “total 0”

Screenshot 2023-01-04 123558

Thanks for the reply. Plex Media Server is removed from your system.

Now try to re-install.

The DS415+ has an Atom 64-bit CPU, so you want the Intel 64-bit, DSM 7 version of Plex.

Use the PlexMediaServer-1.29.2.6364-6d72b0cf6-x86_64_DSM7.spk file that @ChuckPA previously posted here (the second link of the three you listed above).

Make sure the file name matches exactly. No (1) etc like Windows places on duplicate downloads.

Perform a manual installation using Synology Package Center.

The Atom C2538 is a very low power CPU. It may take some time for the installation to complete. Let the process run to completion. Do not interrupt it.

After the installation is complete, you should be able to claim the server.

From a system on the same network as the NAS, point a private/incognito browser window at the IP address of the Synology. The private window bypasses any browser plug-ins that might interfere.

For example, if the NAS’ IP address is 10.1.2.3, use http://10.1.2.3:32400/web.

Do not click the “open” button in Syno Package Center, use a domain name, Synology Quick Connect, etc. You must use the IP address to claim the server (it is a DSM 7 thing).

Give it a try and report back how things go.

Ok… after 4 hours it’s still sitting on…

“Processing…please wait”

Where do you see this message? Still in Package Center? When trying to login post installation?

I installed Plex on my DS414, a low powered ARM based system. It took about 5 minutes for Package Center to complete, then another 3 - 4 minutes before I could login via Plex Web.

Don’t interrupt it . It must complete.

If you can help it – don’t let the page refresh (Package Center will lose its place)
( If this happens, watch in Resource Monitor until the CPU and volume is idle again ).

What’s happening is your files are being moved.
If interrupted, we end up with a broken installation / mess.

We can also verify it’s busy by using Resource Monitor.

The volume should be busy.

Immediately after pressing manual install.

Idle timer was changed to 65,000 minutes previously and remains unchanged. Computer is plugged in and power settings changed to not disconnect.

Will update in the morning.

Before you go…

Please check Resource Manager - Overview tab - Volume.

Do you see any activity?

If so, that is Plex moving files.

If not, then DSM is stuck. Hit F5 to refresh the web browser. Then see where things are at.

Max of 78kb/s every few seconds…

Press F5 to refresh the browser window.

If Plex were relocating files there would be more disk activity.

Done and nope. No more action.

Do you have more than one volume on the NAS?

Any chance Plex was ever installed someplace different than Volume 1 (the default location)?

Here’s what’s throwing me…

  1. The Plex installation defaults to volume 1.
  2. With Plex 1.21.0.3744, the Plex data folder is located in @apphome/PlexMediaServer.
    That directory is empty (you checked it earlier).
  3. Current versions of Plex use /PlexMediaServer as the Plex Data Folder.
    You deleted that folder earlier.
  4. Any existing Plex Media Server installations should now be removed
  5. The installer says “Processing,” which means “upgrading.”
    It would say “Installing” if it was a new installation.

So, the installer is acting like it is upgrading an old installation.

The Plex installer will search on all volumes for old Plex Data Folders to migrate/upgrade. If it finds one, it will begin the migration/upgrade process. If it does not, it starts the process to create a new server.

But all Plex installations have been removed, so what is it upgrading?

That’s the conundrum and why I’m asking about non-Volume 1 installations.

Answer back when you get a chance.

I need to think on this a bit and consult with some folks. I’m in US CT and it is getting late. I’ll check with folks in the morning and be in touch.

This is solvable. Just have to figure out what went sideways and how to correct it.

Just the single volume.

I’ve even checked with people at home with the NAS there (DS920+) and the PlexMediaServer folder is under the Volume1 in Shared Folder (did that upgrade correctly). Confirming no such folder exists under this NAS.

I’m open to any solution that doesn’t require me to delete the media that I’d have to re-copy. This NAS is exclusively used for Plex.

I greatly appreciate the support. I’ve been stumped for ages!

Checking in. Did the installation complete?

If not…

Try logging in to the Plex server anyway, using the IP address of the NAS: http://nas_ip_address:32400/web.

Wondering if the install completed, but Synology DSM never updated to show such, and maybe you can login anyway.

If no luck, let’s see if the log files show anything.

Stop the installation and/or stop Plex Media Server if it shows running.

The NAS should have the PlexMediaServer shared directory. In File Station, navigate to /PlexMediaServer/AppData/Plex Media Server. Right click on the Logs directory, compress to Logs.zip, and attach the zip file to the thread (drag it into the message window, it will insert at the cursor location).

Nope. Still sitting on the same screen. I’ve killed the process now.

I don’t have Plex installed at all now. So there is no PlexMediaServer folder for log files.

Do I reinstall the beta again?

Synology updated Package Center sometime today. The beta is no longer available (a good thing). It now has 1.29.2.6364 (in the US anyway, not sure if available globally yet).

Try installing 1.29.2 again. If available via Package Center you can use it or perform a manual install.

The installation really should complete in just a few minutes.

If it does not complete in 10 - 15 minutes, stop the installation.

If there are any log files post them and we can take a look.

If there are no log files, then I’ll ask @ChuckPA to assist, as this is stretching my knowledge of Synology DSM.

1.29.2 via Package Center has successfully installed on first attempt. Just rebuilding libraries now.

I can update to 1.30… is that worth trying as well?

Great to hear that Plex is installed and working.

Do not update to 1.30.0 or 1.30.1.

Both have a TrueHD / Dolby Digital Plus transcoding bug. Audio transcoding will fail after several minutes. The workaround is to choose a different audio track if one is available.

Both have a bug when analyzing music for loudness. The server will crash. The workaround is to disable the feature in Settings → Library.

1.29.2 is very stable. Suggest you stay there until the 1.30.x releases stabilize.

Thanks for your patience and support along the way. It’s been greatly appreciated :slight_smile:

I’ll stay on 1.29 and follow the forums and release notes as to when to update.

I never transcode so hopefully that’s why I have had no issues with my other NAS at home on 1.30