I have PMS running on Raspberry PI 2!

@moe94 I wouldn’t get to troubled with this message I see the same on a working 9.16.3 when doing the command (service plexmediaserver status)

This is my log every time I try to start the service via a service restart.

plexmediaserver.service - LSB: Plex Media Server
Loaded: loaded (/etc/init.d/plexmediaserver)
Active: active (exited) since Fri 2016-03-25 03:29:12 UTC; 5s ago
Process: 4139 ExecStop=/etc/init.d/plexmediaserver stop (code=exited, status=0/SUCCESS)
Process: 4148 ExecStart=/etc/init.d/plexmediaserver start (code=exited, status=0/SUCCESS)

Now a question for the group…would there be any benefit to moving the entire plex server to a usb ssd? we get a lot of power glitches here in the great northwood that every once in awhile corrupts plex. Of Course I keep several backup, but was wondering if such an install might help protect PMS? Just have nothing but the os on the sd card. Any input appreciated.

And once again Thanks to the geniuses that came up with this port! Johnathan, Uglymagoo, And Blindpet And Thanks for the continued support in this thread!

Yes, definitely, a normal hard disk will suffice, you’ll still need an SD card to start the boot then the disk will kick in. Added advantage is that you can create another partition for your media.

See http://raspberrypihobbyist.blogspot.co.uk/2013/07/running-from-external-hard-drive.html

Regards

@NedtheNerd Thanks for the reply, that’s what I was thinking. I am out growing my 16Gsd cards and was trying to think of something different. No need for the media storage …on the network nas…so don’t need one to large. Now all I have to do is figure it out? Perhaps a 125 would be more than enough.

I have a 1Tb Hard Drive with 3 partitions, 20Gb for boot, 2Gb for swap (with RPi normal swap file disabled) and 960Gb for media. This is a portable setup as it has its own software wireless router and access point set up on the same boot drive, great for serving tablets and phones in the car and the cottage which has no internet connection where I use another RPi with Rasplex as the client connected to the TV.

Regards

Nice setup Ned…I was thinking in a few partitions and install a few sets of pms that way if anything happens switch servers and copy over the damage one…Maybe? Duh didn’t even notice the link Thank You!

I just helped a friend to integrate PMS into OpenELEC on his RPi3. As it turns out, the task is really easy. Just get the latest x64 PMS addon and replace the binaries in /lib with the binaries of my Debian or the Synology armv7 alpine package. Just take extra precautions to retain the symlinks (e.g. zip --symlinks) or dereference each symlink (e.g. cp -aL). Should also work on the RPi2 and similar devices.

Now something completely different: the plexmediaserver-installer package :slight_smile: The package bundles only the Debian maintainer scripts and not much more. During postinst the package retrieves the PMS binaries from plex.tv and copies them to /usr/lib/plexmediaserver. There is no cronjob or update script in the package. I will update the package as soon as there is a new PMS server available, just like before, but you will get the binaries now directly from plex.tv. I performed many tests myself, but you might want to wait till we have positive feedback from other brave testers :slight_smile:

The old package is removed automatically at the moment you install plexmediaserver-installer. Your meta data should survive the switch to the new package. You should backup your /etc/default/plexmediaserver if you had changed something there before.

How to switch:

apt-get update
apt-get install plexmediaserver-installer

If there are serious issues with this installer package I will also push 0.9.16.4 of the old package to my repo.

Have fun! :slight_smile:

Complete tutorial:

# become root
sudo su

# add my public key
wget -O - https://dev2day.de/pms/dev2day-pms.gpg.key | apt-key add -

# add my PMS repo
echo "deb https://dev2day.de/pms/ jessie main" >> /etc/apt/sources.list.d/pms.list

# activate https
apt-get install apt-transport-https

# update the repos
apt-get update

# install PMS
apt-get install plexmediaserver-installer

Complete tutorial for native ARM64 distributions:

# become root
sudo su
    
# add my public key
wget -O - https://dev2day.de/pms/dev2day-pms.gpg.key | apt-key add -
    
# add my PMS repo
echo "deb [arch=armhf]  https://dev2day.de/pms/ jessie main" >> /etc/apt/sources.list.d/pms.list

# activate https
apt-get install apt-transport-https

#enable armhf support
dpkg --add-architecture armhf    

# update the repos
apt-get update
    
# install PMS
apt-get install plexmediaserver-installer:armhf
1 Like

Hi uglymagoo,

Works perfect here!
Thx!

I updated a couple hours ago and it works great!
Thank you for doing this.

updated yesterday and running fine! Thanks and keep up the great work.

@uglymagoo this is great, does that mean you will no longer publish the regular packages?

Is this new installer basically automating the skeleton process?

@blindpet said:
@uglymagoo this is great, does that mean you will no longer publish the regular packages?

Yes, that is the plan. However, there will be an automatic transition to the new package (dummy, empty old package which depends on the new installer package). So existing repo users switch automatically to the new package. New users should use the new package (but it is not a problem if they do not)

Is this new installer basically automating the skeleton process?

Basically. I will provide an updated skeleton in the next days. I also cleaned the old maintainer scripts but still did not switch to systemd.

Thanks @uglymagoo so that means I don’t have to update the tutorial pages just yet then. If you need help testing the new skeleton manual method let me know.

Do you need to switch to systemd? All init.d scripts I’ve tested work on systemd systems.

@blindpet said:

Do you need to switch to systemd? All init.d scripts I’ve tested work on systemd systems.

Still LSB init scripts.

Had some trouble with armbian jessie latest+plexmediaserver-installer in banana pi. First had to increase the /tmp partition (default tmpfs with 256mb) or it wont install. But after install, creating,editing and deleting libraries sometimes gives error (your changes couldnt be saved) and sometimes make plex stop run, so i have to log in ssh and do systemctl restart plexmediaserver. Reverted back to plexmediaserver (0.9.16.3.1840) and now it is stable.

sorry about my bad english.

@fabianovsantos said:
Had some trouble with armbian jessie latest+plexmediaserver-installer in banana pi. First had to increase the /tmp partition (default tmpfs with 256mb) or it wont install.

Ok, I will reduce the /tmp usage in the next package revision.

But after install, creating,editing and deleting libraries sometimes gives error (your changes couldnt be saved) and sometimes make plex stop run, so i have to log in ssh and do systemctl restart plexmediaserver. Reverted back to plexmediaserver (0.9.16.3.1840) and now it is stable.

This might be a problem of PMS itself.

I just pushed the new packages to the repo. ‘apt-get upgrade’ is not sufficient, all of you need 'apt-get dist-ugprade` because of the new dependency. You might also have to restart the server afterwards with the init.d script (I changed some stuff). Good luck :slight_smile:

Does anyone need input this command? The switch worked fine on my rpi 3 so i wonder if i need to do anything else now? :slight_smile:

Hi uglymagoo, just tested your .deb package, it works fine! Thanks!

As a feedback, i also tried the new package in your last post (from apt). Installed ok, no problem with /tmp size. But after add 2 libraries, in the third, i got “your changes could not be saved” (something like this, because i’m using pt-BR language). After this, i got “the server bananapi is unavailable”.

Another thing, i saw all processes running as root user, not as plex user as it used to be.

thanks!