Synology DS414j - DSM 6.2.1-23824 Update 4 - How to install Plex?

Plex Media Server NAS & Devices
1

Hi,

I’ve got a Synology DS414j with DSM 6.2.1-23824 Update 4. I have tried three different ways to install plex, but all of them gives an error that it’s not compatible with my NAS.

  1. Official stable version from Plex website (1.14.1.5488-cc260c476)
  2. The version from Synology Package Center (1.13.4.5271-200287a06)
  3. Build from: Much faster (hopefully), smaller (mostly) and better PMS builds preview (1.15.0.573-123756e9a) (1.15.0.659-9311f93fd) which explicitly mentions that it’s for the ds414j - ARMv7_Neon (x15 Series (excluding DS115j, RS815), x16 Series (excluding DS216se), x17 Series, x18 Series, and DS414j)

I can’t install any of them. I know the ds414j is a ‘special’ Synology NAS, being the only one with the Mindspeed Comcerto C2000 CPU, but I’ve read that quite a few people are in fact running Plex on it, and now (again) that Plex mentions the model in a specific build, I thought it would work. Anyone have an idea?

Thanks

3

Hi trumpy81 and thanks for replying.

I had already followed those instructions, but I did it again just to be sure. Please see the screenshots.

PlexMediaServer-1.15.0.659-9311f93fd-armv7hf_neon.spk downloaded with Firefox.

Manual install via Synology Package Center.

37
37859×564 44.6 KB
53
53969×516 45.3 KB
02
02692×491 32.4 KB

5

Hi, thanks, but I got the same error with that file.

7

Hi, that file didn’t work either.

SSH:d in to the NAS, but the command didn’t return anything. Pasting it here (just removed my username/host).

:/$ cd /lib
:/lib$ ls -la | grep libc*
:/lib$
9

Hi, no didn’t run as root first. But now I did, with same result though.

:/lib$ sudo su

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

Password:
ash-4.3# cd /lib
ash-4.3# pwd
/lib
ash-4.3# ls -la | grep libc*
ash-4.3#
11

Thanks!

13 
ash-4.3# cd /volume1/
ash-4.3# ls -al
total 60
drwxr-xr-x   9 root  root  4096 Feb  9 16:27 .
drwxr-xr-x  22 root  root  4096 Feb  9 15:49 ..
drwxr-xr-x   3 root  root  4096 Feb  9 15:57 @appstore
-rw-------   1 root  root  6144 Feb  9 15:50 aquota.group
-rw-------   1 root  root  8192 Feb  9 15:50 aquota.user
drwxr-xr-x   6 admin users 4096 Feb  9 15:50 @database
drwxrwxrwx+  3 root  root  4096 Feb  9 16:27 @eaDir
d---------+  6 root  root  4096 Feb  9 16:35 nasfiles
drwxr-xr-x   2 root  root  4096 Feb  9 15:50 @S2S
-rw-------   1 root  root  5120 Feb  9 15:53 synoquota.db
drwxrwxrwt   5 root  root  4096 Feb 13 08:25 @tmp
drwxr-xr-x   2 root  root  4096 Feb  9 15:57 @webdav
15

No problem, not in such a rush. Yep, gurus need their sleep. Thanks for helping.

16

Chatting with Trumpy before I hit the bed…

Please run this command with root.

ls -la /lib64 | grep libc

it will look like this (top lines)

admin@moesern:/lib64$ ls -la libc*
-r-xr-xr-x 1 root root 1714384 Sep  7 04:55 libc-2.20-2014.11.so
lrwxrwxrwx 1 root root      11 Oct 25 18:20 libcap.so -> libcap.so.2
lrwxrwxrwx 1 root root      14 Oct 25 18:20 libcap.so.2 -> libcap.so.2.22
-rw-r--r-- 1 root root   23072 Sep  7 04:55 libcap.so.2.22

and must show 2.14-xxxx or newer else we aren’t going anywhere when I figure out what synology did to the 32 bit installer but my guess is it’s a 32-bit issue

17

Hi, thanks.

Funny thing, I thought I understood how ‘grep’ worked. But maybe I don’t. It’s empty with grep but with a ls -la libc* it’s not.

–

ash-4.3# ls -la /lib64 | grep libc
ash-4.3#

–

ash-4.3# pwd
/lib64
ash-4.3# ls -la libc*
-r-xr-xr-x 1 1000 1000 1271456 Oct 26 15:55 libc-2.20-2014.11.so
lrwxrwxrwx 1 root root      11 Feb  9 15:42 libcap.so -> libcap.so.2
lrwxrwxrwx 1 root root      14 Feb  9 15:42 libcap.so.2 -> libcap.so.2.22
-rw-r--r-- 1 root root   22904 Oct 26 15:55 libcap.so.2.22
lrwxrwxrwx 1 root root      17 Feb  9 15:42 libcares.so -> libcares.so.2.2.0
lrwxrwxrwx 1 root root      17 Feb  9 15:42 libcares.so.2 -> libcares.so.2.2.0
-rwxr-xr-x 1 root root   68384 Oct 26 15:54 libcares.so.2.2.0
-rwxr-xr-x 1 root root  377784 Oct 26 15:54 libced.so
lrwxrwxrwx 1 root root      15 Feb  9 15:42 libcom_err.so -> libcom_err.so.2
lrwxrwxrwx 1 root root      17 Feb  9 15:42 libcom_err.so.2 -> libcom_err.so.2.1
-rwxr-xr-x 1 root root   14264 Oct 26 15:57 libcom_err.so.2.1
-r-xr-xr-x 1 1000 1000   30952 Oct 26 15:55 libcrypt-2.20-2014.11.so
lrwxrwxrwx 1 root root      18 Feb  9 15:42 libcrypto.so -> libcrypto.so.1.0.0
-r-xr-xr-x 1 root root 2175976 Oct 26 15:56 libcrypto.so.1.0.0
lrwxrwxrwx 1 root root      24 Feb  9 15:42 libcrypt.so.1 -> libcrypt-2.20-2014.11.so
lrwxrwxrwx 1 root root      20 Feb  9 15:42 libc.so.6 -> libc-2.20-2014.11.so
lrwxrwxrwx 1 root root      23 Feb  9 15:42 libcupsfilters.so -> libcupsfilters.so.1.0.0
lrwxrwxrwx 1 root root      23 Feb  9 15:42 libcupsfilters.so.1 -> libcupsfilters.so.1.0.0
-rwxr-xr-x 1 root root  113744 Oct 26 15:58 libcupsfilters.so.1.0.0
lrwxrwxrwx 1 root root      17 Feb  9 15:42 libcupsimage.so -> libcupsimage.so.2
-r-xr-xr-x 1 root root   30808 Oct 26 15:58 libcupsimage.so.2
lrwxrwxrwx 1 root root      16 Feb  9 15:42 libcupsmime.so -> libcupsmime.so.1
-r-xr-xr-x 1 root root   31072 Oct 26 15:58 libcupsmime.so.1
lrwxrwxrwx 1 root root      12 Feb  9 15:42 libcups.so -> libcups.so.2
-r-xr-xr-x 1 root root  509296 Oct 26 15:58 libcups.so.2
lrwxrwxrwx 1 root root      16 Feb  9 15:42 libcurl.so -> libcurl.so.4.4.0
lrwxrwxrwx 1 root root      16 Feb  9 15:42 libcurl.so.4 -> libcurl.so.4.4.0
-rwxr-xr-x 1 root root  403064 Oct 26 15:58 libcurl.so.4.4.0
lrwxrwxrwx 1 root root      13 Feb  9 15:42 libcurses.so -> libncurses.so
-rw-r--r-- 1 root root      18 Oct 26 15:56 libcursesw.so
ash-4.3#
18

that’s the nice thing about linux, multiple ways of doing the same thing

ls -la /lib64 | grep libc

and

ls -la /lib64/libc*

with both show us the libc named files there

:smiley:

19

Yep, that’s what I thought. So I don’t understand why

ls -la /lib64 | grep libc

doesn’t return anyting and

ls -la /lib64/libc*

returns the list of files.

20

@trumpy81 @ChuckPa any more ideas?

22

I went into the code.

That CPU is a comcerto2k which means it needs the armv7hf_neon package in the new build system.

Existing build system is:

https://downloads.plex.tv/plex-media-server/1.14.1.5488-cc260c476/PlexMediaServer-1.14.1.5488-cc260c476-arm7.spk

23

Hi, thanks for replying.

I tried installing the version you just linked, but got the same result: “This package is not supported on the platform of DiskStation or is incompatible with the current DSM version.” :frowning:

25

Hi and thanks for replying.

I tried the old version you linked and it didn’t work. Same result.

I might try a reset at a later point, but it sounds strange as I just bought the NAS a week ago. Only thing I’ve done is install DSM and create my RAID. I haven’t rebooted it yet though, since I’m still copying files to it, so I’ll try to reboot it and try a few of the Plex-packages I’ve tried recently and report back.

Thanks for helping though! Hopefully it will be resolved.

27

Yep, I know it’s not a new model :slight_smile: I just meant that I bought it and installed it a week ago, so I couldn’t have messed it up too bad (yet) :wink:

But, yep, if I get around to reset it, I’ll report back, thanks!

28

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