Updated FreeNAS to TrueNAS Core STABLE 12.0 release - Plex server not running

Gimpymoo

Dabbler
Joined
Sep 10, 2018
Messages
39
Plex Media server does not start and I get the error below when trying to update…

Updating Jail
Error: Major ABI change detected, please run ‘upgrade’ instead.
I think I need to do this via the shell but unsure of the exact syntax needed.

I found this link:

14. Jails — TrueNAS®11.3-U2 User Guide Table of Contents (ixsystems.com)

Upgrade a jail by stopping it, opening the Shell and entering iocage upgrade name -r release , where name is the plugin jail name and release is the desired release to upgrade to.
Where do I find he release info syntax so I can tell the shell what I want it to upgrade to?

I tried:

iocage upgrade plex -r Truenas-12.0-RELEASE

But this gave the following error:

1604023194665.png


All was working fine till the update.

I am grateful for any pointers. Thank you.
 

Redcoat

MVP
Joined
Feb 18, 2014
Messages
2,925
The correct syntax you need is

Code:
iocage upgrade plex -r 12.1-RELEASE


assuming your jail IS called “plex”
 

rknaub

Explorer
Joined
Jan 31, 2017
Messages
75
Plex sabnzbd and radar all won’t load after update to 12.0. I’m not smart enough to fix it or to know what to do by myself. Just rolled back.
 

Gimpymoo

Dabbler
Joined
Sep 10, 2018
Messages
39

Gimpymoo

Dabbler
Joined
Sep 10, 2018
Messages
39
The correct syntax you need is

Code:
iocage upgrade plex -r 12.1-RELEASE


assuming your jail IS called “plex”

Thanks.

For some reason, that generates the error saying cannot find plex.json as per the op.
 

Gimpymoo

Dabbler
Joined
Sep 10, 2018
Messages
39
go to system, boot, select 11.3u5 or whatever latest you have, click the three dots, activate, reboot

Thanks. That saved me a load of hassle.

Happy to wait till the probs are nailed or someone has a definite "fix".
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
For some reason, that generates the error saying cannot find plex.json as per the op.
That seems to me that you haven't used the name of your jail... isn't it usually called plexmediaserver?

Plex sabnzbd and radar all won’t load after update to 12.0. I’m not smart enough to fix it or to know what to do by myself. Just rolled back.
Also, just to be clear, there's no "new" fix that will come... you just didn't finish the update by running the original command against the right jail name and iocage pkg <jailname> upgrade at the end of the update of the jail OS to upgrade and/or fix the packages inside the jail for the new OS.

You may need to assume that it's asking you for "y" + [ENTER] to proceed when it's showing you the list of packages that will be modified as the iocage pkg command seems to block that message somehow.
 

Gimpymoo

Dabbler
Joined
Sep 10, 2018
Messages
39

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Can you show the output of iocage list?
 

Gimpymoo

Dabbler
Joined
Sep 10, 2018
Messages
39
Can you show the output of iocage list?

Sure...

1604053590666.png


After rolling back the "working" 11.3.. I still get the file missing error when trying to force upgrade.

1604053689556.png


So, in the iocage>.plugins folder I have two folders..

github_com_freenas_iocage-ix-plugins_git
github_com_ix-plugin-hub_iocage-plugin-index_git

In the
Code:
github_com_ix-plugin-hub_iocage-plugin-index_git
folder I did have plexmediaserver.json so I renamed it to plex.json and ran
Code:
iocage upgrade plex -r 11.3-RELEASE


At least I now have 11.3 which is some progress but not sure about the original error on TrueNAS. Is it worth trying again now I have 11.3 release in the Jail and not 11.2?

Thanks.
 
Last edited:

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
And which version of the plugin did you install? (standard or beta/plexpass)

Also, have a look in that directory:
/mnt/Original/iocage/.plugins/github_com_freenas_iocage-ix-plugins_git/ and see if you have the files plexmediaserver.json and plexmediaserver-plexpass.json in there...
 

Gimpymoo

Dabbler
Joined
Sep 10, 2018
Messages
39
My Plex server is now updated with 11.3-RELEASE-p14 which I could not get to updadate to before.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
And you ran the pkg upgrade after?
 

Gimpymoo

Dabbler
Joined
Sep 10, 2018
Messages
39
And you ran the pkg upgrade after?

I ran iocage upgrade plex -r 11.3-RELEASE then ran the jail update from the webUI. Previously, this has not worked for a LONG time.

Some progress I guess.

Tempted to try TrueNAS again and see if fixing that makes any difference.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Tempted to try TrueNAS again and see if fixing that makes any difference.
Be aware that the rollback is more complex if the jail upgrade succeeds... but maybe then you won't want to roll back.
 

Gimpymoo

Dabbler
Joined
Sep 10, 2018
Messages
39
Be aware that the rollback is more complex if the jail upgrade succeeds... but maybe then you won't want to roll back.

As in running a 12.0 Jail in a 11.3 host?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
As in running a 12.0 Jail in a 11.3 host?
Right... you can't do that.

Although if you did an iocage snapshot on the jail before the upgrade, you could probably go back to that and all would be OK... like I said, more complicated,
 

Gimpymoo

Dabbler
Joined
Sep 10, 2018
Messages
39
I agree @sretalla , Restoring a snapshot should work.

As you say though, if it worked, I would keep it as it was.

It is possible the reason for the problem is that the jail was too out of date but as I said, it had not been able to update till now having fixed the problem with the naming of the .json.

I am tempted to move the Plex server onto a Windows box as this it would appear is more simplistic but I would only do so if I could import the current Plex database from Freenas and have Freenas/Truenas doing what it does best, store my data :D
 

Gimpymoo

Dabbler
Joined
Sep 10, 2018
Messages
39
Is this still the same on the current build?
 
Top