Error trying to upgrade on FreeNAS

Plex Media Server Desktops & Laptops
1

I am trying to upgrade to 1.20.3 on FreeNAS using ports (as recommended by a Plex employee here before in the past) and I am getting this error:

--------------------------------------
/!\ ERROR: /!\

Ports Collection support for your FreeBSD version has ended, and no ports are

guaranteed to build on this system. Please upgrade to a supported release.

No support will be provided if you silence this message by defining

ALLOW_UNSUPPORTED_SYSTEM.

*** Error code 1

Stop.

make: stopped in /usr/ports/multimedia/plexmediaserver-plexpass

/!\ ERROR: /!\

Ports Collection support for your FreeBSD version has ended, and no ports are

guaranteed to build on this system. Please upgrade to a supported release.

No support will be provided if you silence this message by defining

ALLOW_UNSUPPORTED_SYSTEM.

*** Error code 1

Stop.

make[1]: stopped in /usr/ports/multimedia/plexmediaserver-plexpass

*** Error code 1

--------------------------------------

I am already using FreeNAS 11.3-U5 which is the latest production version of FreeNAS. So I am not sure to which version Plex wants me to upgrade because there is no newer version.

What should I do? Wait until someone from Plex decides to compile and push it via PKG updates? So I will have to live 6 months in the past forever?

2

Actually, when I upgraded to the last stable version via pkg I got an error about my kernel being mismatched. It said I needed to be on “11.4”. I went ahead and overrid it that time.

You probably need to post this topic on the FreeNAS forums, but I expect their response still be that you will need to update to TrueNAS Core, which is on RC status, which they claim is fine for home users.

Personally I’m waiting for RELEASE or maybe the first update before I think of changing over.

3

This is the procceedure I use to upgrade PMS on both of my FreeNAS boxes.


It has worked every time I have used it with no issues. Also since you rename the OLD PMS directory instead of overwriting it, you can revert back if there is something wrong with the version you just upgraded to.
4

Hum we still use 11.3 to build IIRC so this should still work (in the sense the PMS should run there).

The issue however is that the jail is not able to fetch ports because you have a older kernel/user-land than supported!

The jail is likely still on 11.1/2/3 and not 11.4, so perhaps all you need is to upgrade the jail with iocage, I’m not sure however if it will allow you to do so if the host is on 11.1/2/3 and not 11.4., I know it does not work for 11 to 12 i.e.

It also seems pkgng repos are experiencing issues, I was just trying to get u a direct link o the latest pkg but http://pkg0.bme.freebsd.org/FreeBSD:11:amd64/latest/All/ gives a 403.

5

Of course upgrading the jail was the first thing I tried.

6

Unfortunately Plex takes to long to push the packages via pkg, we are talking about months of delay. The pkg version was upgraded not long ago to 1.20.1. So not really a “Plex Pass:” version.

7

I don’t think the port of Plex to pkg is actually done by Plex themselves.

Current pkg version is 1.20.3.3437. That’s not old at all. I’m on 1.20.2.3402 myself. Just waiting for that latest version with the CVE patch to hit before I update again. Will likely be out on pkg in a week or so.

8

I think the problem is the latest version of Plex requires FreeBSD 11.4, but FreeNAS is still on 11.3. I wonder why they increased the requirement to a version that does not exist for the majority of their customers.

Yes, I know that technically you could upgrade your jail to 11.4 while still running 11.3 in the host, but I prefer to follow the recommendation to keep the host and jails version synchronized.

This again shows me poor Plex support to FreeNAS users.

9

I am on Plex 1.20.3.3483(which I think is the latest) and FreeNAS 11.3-U5 and the dashboard shows no updates are available.

10

Cool for you, but the “upgrade” procedure you posted is just a copy/paste of the contains of the package, so it won’t actually install the package. You decided it is good for you, some people might decide that’s not acceptable because there is no control of that it is in the system.

11

You’re correct. That is not an INSTALL procedure, it is an UPGRADE procedure once your jail has been established and working. To do the initial install, I just used the plugin install in FreeNAS and have then used this upgrade procedure ever since.

12

To me it is not an upgrade, it is overwriting files manually via copy/paste. To some people that might be acceptable, so some it isn’t.

13

It doesn’t OVERWRITE anything. You RENAME your current install directory so you can revert to it if the new version doesn’t perform as expected. You don’t loose any of your library metadata or settings because those aren’t stored in the directory you are renaming and replacing. I don’t know why you are nit-picking on semantics. If you don’t want to use the procedure, then don’t. I am only saying it has worked perfectly for me thus far.

14

Man, what a stubborn, at the end you have a bunch of files that are not under the version control system. How is that difficult to understand? I respect your opinion, if that’s good for you then be happy, but plenty of people won’t find copy/pasting binaries acceptable. It is the same as releasing a software as a TGZ file, some people will think it is good enough, some won’t… Plex is a COMMERCIAL software and I paid for a license, I do not think that copy/pasting binaries is acceptable.

15

I think you need to go back and read your own thread again.

The reason you can’t upgrade is because Ports support for FreeBSD 11.3 has ended. That’s an operating system restriction and Plex, Inc has nothing to do with it.

A Plex employee is literally telling you they still build on 11.3 - so your assumption that Plex has raised the system requirements is bunk.

This reads to me as you’re still operating on the Quarterly repository schedule used by default in jails. If you’d change your jail to use the Latest repository source you’d see these newer versions everyone is getting.

@phoneguyinpgh is right, too. 1.20.3.3783, the latest stable version, is out now on pkg. In fact, it’s out on both the latest and quarterly schedules. I updated my system tonight via pkg.

You need to go read up on FreeBSD and support lifecycles. Here, I’ll save you the Googling.

FreeBSD 11.3 support ended September 30th. That’s why Ports is saying to move on, and pkg-ng is saying the same thing:

root@plex-3:/ # pkg update
Updating FreeBSD repository catalogue...
[plex-3] Fetching meta.txz: 100%    916 B   0.9kB/s    00:01
[plex-3] Fetching packagesite.txz: 100%    6 MiB 780.0kB/s    00:08
Processing entries:   0%
Newer FreeBSD version for package rest:
To ignore this error set IGNORE_OSVERSION=yes
- package: 1104001
- running kernel: 1103000
Processing entries: 100%
Ignore the mismatch and continue? [Y/n]:

There is no FreeNAS 11.4 and there never will be.
If saying “Yes” to the above on pkg-ng is too much, or:

…isn’t acceptable, put on your big-boy pants and go upgrade your system.

16

Of course when I posted this 1.20.3 was not yet in pkg, but not it is, so I have updated already, thanks for pointing that out.

And of course I will upgrade someday to TrueNAS, but requiring to upgrade to a completely new product who was released literally last week is not an acceptable solution either. Specially after the FreeNAS 10 (Corral) drama.

Anyway, it is all good, for now.

17

I spoke too soon, yes, 1.20.3 is now in pkg … because now 1.20.4 was released. Man, this is a bad joke.

18

@Havohej I think there’s a lot of confusion here due to a lack of understanding FreeBSD and FreeNAS.

Let me try to help a bit… FreeNAS is based in FreeBSD but like many NAS systems based on linux, they are not 100% the same.

The standard method to get and update packages in FreeNAS is via plugins (Which use iocage jails and point to a specific pkg repo).

Many NAS vendor use similar methods, be it plugins or packages in a “store”… This is super normal and usually stability is preferred for good reasons and that means you wont always be on the latest version (even if its stable they still have their own QA processes and this takes time).

You’re “cheating” and levering the fact that FreeNAS still allows use of ports or pkg-ng and if you create a standard jail and point it to freebsd repos, but in doing that you need to understand how this works.

FreeNAS uses an OLDER FreeBSD base, at least always 1 year behind, and often, even more, no one is forcing you to upgrade… you are the one requiring it.

And honestly, that’s ok, if you want to always have the latest you just have to be aware of that. FreeBSD 12.x exists WAY longer than the new TrueNAS system that is now based of FreeBSD 12.
The only true way to be sure the latest ports/pkg will work is by using the latest FreeBSD…

FreeBSD 12.2 dropped today (or it’s close to if I’m not mistaken), 12.0 was released in December 2018, just so you get an idea how behind FreeNAS can be (I do believe they plan to change this a bit with TrueNAS, but there will always be a gap)

So tl;dr if you want to be on latest always use FreeBSD not FreeNAS, or if you do use FreeNAS try to at least be in the latest there too (which many times will mean the one that just got released)

There realy no one requiring anything here, not plex and not FreeNAS.

19

Please allow the port maintainer a little bit to update the port and the build machines in the CI to do their work… the beta version (which was just released) will be available shortly I’m sure, at most it will take a couple days.

20

Thank you for the long post, I appreciate it. Now the things from my point of view:

  • I use FreeNAS because Plex says you support FreeNAS. It has been for long time in the list of OS you support, with different mechanisms to install it during the past years.

  • Someone from Plex here in the past told us not to use the FreeNAS plugins and to update via a homemade script provided by such Plex Employee. Then it was suggested not to use the script anymore and to use Ports instead. The procedure to use Ports was provided by a Plex employee here. It is not that I want to use Ports, I would prefer not to use it and simply update via pkg, but the updates are too slow. It seems the Plex Pass package follows the non-Pass speed, which is ironic.

  • Suggesting to move to FreeBSD is not really a solution, we the FreeNAS users use tons of other functionality FreeNAS provides and FreeBSD does not. Plex is just one of the things we run in our boxes, and probably the most PITA to maintain. Most of other things are maintenance free. Ironic that the paid software is the headache.

Again, thanks for your time, I know you are the one who has always replied to our FreeNAS questions and this is highly appreciated. My complains are not against you personally.

1 Like