Synology NAS - Plex Media Server Failed to launch!

Server Version#: 1.18.5.2309-f5213a238
Player Version#: n/a

Previously, PMS (version 1.18.5.2309-f5213a238) works great at my Synology NAS, and was able to connect to NAS and watch videos at client Android TV Plex, ipad Plex, Android phone Plex.

Today, I have switched my hard disks to a different motherboard with different CPU, three hard disks may connect to SATA ports at different order onto new motherboard.

Previous: i5-4570, MSI B85-G43, DS3617xs @ DSM6.1.7
Now: i5-2500s, Intel dq67sw, DS3617xs @ DSM6.1.7 (re-using my old parts)

After installing same ver. of Plex Media Server at different motherboard and CPU, the PMS keep showing “Launch failed”. I can’t find any logs and have no idea what’s wrong, i am suspecting it may relates to the hard disks with different volume # or maybe about CPU?

I have tried almost everything, installing PMS to different disks, different version of PMS ver under intel x86_64, checked different authority under both admin or user’s accounts, SSH putty under root account to delete Plex Media Server folder and then reinstalled, all not working.

Launching PMS at Synology NAS looks like a dead end to me. A little help is appreciated.

Thanks!

Thanks for prompt reply, however there’are too much works to startover from scratch…:frowning:

All other apps remained from previous sinology system are working, even the similar Jellyfin, i don’t even have to reinstall them except Plex. I am just wondering why Plex is too special to reinstall entire system to launch,

There is no files under Plex/Library/Application Support/Plex Media Server.

Problem solved!

Deleted existing Plex user account and Plex folder, which was carried from previous installation before moving HDDs to new environment.

The new installation was failed (however it shows completed installation but required to Launch manually) due to existing Plex user, thus unable to launch.

I’m following up here to let you and everyone know that I’ve made hefty changes to both correct, and prevent, this type problem on Synology.

I found the root problem, which was very obscure, occurred when either the Plex user or share where recreated individually which is what happens when migrating from one Syno box to another.

I changed the package installation/upgrade sequence to:

  1. Check for the Plex user - create if needed
  2. Check for the Plex share - create if needed
  3. Assign share ACLs (Control Panel - Shared Folders - Plex - Permissions tab) to their default state . (The Plex share shouldn’t be accessed during normal operation)
  4. If changes were made in steps 1 or 2 above, set Linux file permissions

The result is:

When (re)installing the package:

  1. If the Plex user and share got out of sync with each other - it gets corrected
  2. If permissions for the Plex share were incorrect - they get corrected
  3. If there is any indication of a re-installation (from previous backup / recovery ) - it gets corrected.

What this ultimiately means is that the Plex share and user will NOT need to be recreated when migrating from one Synology to another; a huge waste of time and loss of data which I found unacceptable.

How it behaves:

If the Plex user changed,

  1. I change enough of the core permissions for Plex to get started,
  2. I launch a background task on the Syno to correct everything in the Plex share.
  3. The drives will rattle a bit until done (based on size of the metadata library)
  4. While it’s (re)setting everything, you might see some errors with posters or metadata. Please be patient with it while the Syno finishes the task.
  5. I didn’t want to forcibly make everyone wait for 2-3-5-10-20 (?) minutes while it performed this task.

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