All plugins and their jails gone after upgrade 12U8 to 13-Release

[Christian K]

I upgraded from 12U8 to 13-Release, and noticed that all plugins are gone, along with their jails.
CLI confirms they are gone

root@truenas[~]# jls
JID IP Address Hostname Path

Is this supposed to happen? i was unable to quickly answer this by the release notes or upgrade documentation.

The plugins previously installed include:

• NextCloud
• UnifiController
• ZoneMinder

 

[Patrick M. Hausen]

jls shows only running jails. iocage list would be the proper way to list them. If that also returns an empty list, first try iocage activate <name-of-your-pool-with-the-jails>.

HTH,
Patrick

 

[Christian K]

Thanks for pointing this out. But it looks like they are actually gone

root@truenas[~]# iocage list
+-----+------+-------+---------+-----+
| JID | NAME | STATE | RELEASE | IP4 |
+=====+======+=======+=========+=====+
+-----+------+-------+---------+-----+
root@truenas[~]#
root@truenas[~]# iocage activate pool
ZFS pool 'pool' successfully activated.
root@truenas[~]# iocage list
Creating pool/iocage
Creating pool/iocage/download
Creating pool/iocage/images
Creating pool/iocage/jails
Creating pool/iocage/log
Creating pool/iocage/releases
Creating pool/iocage/templates
Default configuration missing, creating one
+-----+------+-------+---------+-----+
| JID | NAME | STATE | RELEASE | IP4 |
+=====+======+=======+=========+=====+
+-----+------+-------+---------+-----+

 

[Patrick M. Hausen]

What does zfs list say? Did you have more than one pool?

 

[Christian K]

Yes, I have two pools. but I am sure the jails were on the "pool" pool

root@truenas[~]# iocage activate SSD
ZFS pool 'SSD' successfully activated.
root@truenas[~]# iocage list
+-----+------+-------+---------+-----+
| JID | NAME | STATE | RELEASE | IP4 |
+=====+======+=======+=========+=====+
+-----+------+-------+---------+-----+
root@truenas[~]# zfs list
NAME USED AVAIL REFER MOUNTPOINT
SSD 10.7M 215G 104K /mnt/SSD
SSD/iocage 8.35M 215G 7.79M /mnt/SSD/iocage
SSD/iocage/download 96K 215G 96K /mnt/SSD/iocage/download
SSD/iocage/images 96K 215G 96K /mnt/SSD/iocage/images
SSD/iocage/jails 96K 215G 96K /mnt/SSD/iocage/jails
SSD/iocage/log 96K 215G 96K /mnt/SSD/iocage/log
SSD/iocage/releases 96K 215G 96K /mnt/SSD/iocage/releases
SSD/iocage/templates 96K 215G 96K /mnt/SSD/iocage/templates
SSD/plugins 96K 215G 96K /mnt/SSD/plugins
boot-pool 10.8G 189G 24K none
boot-pool/.system 22.5M 189G 1.65M legacy
boot-pool/.system/configs-deb14d0c5cbc43b8883f8af65d933a1e 4.50M 189G 4.50M legacy
boot-pool/.system/cores 24K 1024M 24K legacy
boot-pool/.system/rrd-deb14d0c5cbc43b8883f8af65d933a1e 13.3M 189G 13.3M legacy
boot-pool/.system/samba4 182K 189G 79K legacy
boot-pool/.system/services 24K 189G 24K legacy
boot-pool/.system/syslog-deb14d0c5cbc43b8883f8af65d933a1e 2.81M 189G 2.81M legacy
boot-pool/.system/webui 24K 189G 24K legacy
boot-pool/ROOT 10.7G 189G 24K none
boot-pool/ROOT/12.0-U4 180K 189G 1.18G /
boot-pool/ROOT/12.0-U5 174K 189G 1.18G /
boot-pool/ROOT/12.0-U5.1 188K 189G 1.18G /
boot-pool/ROOT/12.0-U6 188K 189G 1.18G /
boot-pool/ROOT/12.0-U7 176K 189G 1.20G /
boot-pool/ROOT/12.0-U8 203K 189G 1.20G /
boot-pool/ROOT/12.0-U8.1 187K 189G 1.20G /
boot-pool/ROOT/13.0-RELEASE 10.7G 189G 1.28G /
boot-pool/ROOT/Initial-Install 1K 189G 1.16G legacy
pool 2.63T 4.50T 96K /mnt/pool
pool/iocage 712K 4.50T 136K /mnt/pool/iocage
pool/iocage/download 96K 4.50T 96K /mnt/pool/iocage/download
pool/iocage/images 96K 4.50T 96K /mnt/pool/iocage/images
pool/iocage/jails 96K 4.50T 96K /mnt/pool/iocage/jails
pool/iocage/log 96K 4.50T 96K /mnt/pool/iocage/log
pool/iocage/releases 96K 4.50T 96K /mnt/pool/iocage/releases
pool/iocage/templates 96K 4.50T 96K /mnt/pool/iocage/templates
pool/nas 2.63T 4.50T 2.63T /mnt/pool/nas

 

[Patrick M. Hausen]

zfs list?

 

[Samuel Tai]

Run iocage activate pool. There can be only one active pool for iocage at a time.

 

[Christian K]

zfs list?

Is included in my previous output

Run iocage activate pool. There can be only one active pool for iocage at a time.

root@truenas[~]# iocage activate pool
ZFS pool 'pool' successfully activated.
root@truenas[~]# zfs list
NAME USED AVAIL REFER MOUNTPOINT
SSD 10.9M 215G 104K /mnt/SSD
SSD/iocage 8.36M 215G 7.79M /mnt/SSD/iocage
SSD/iocage/download 96K 215G 96K /mnt/SSD/iocage/download
SSD/iocage/images 96K 215G 96K /mnt/SSD/iocage/images
SSD/iocage/jails 96K 215G 96K /mnt/SSD/iocage/jails
SSD/iocage/log 96K 215G 96K /mnt/SSD/iocage/log
SSD/iocage/releases 96K 215G 96K /mnt/SSD/iocage/releases
SSD/iocage/templates 96K 215G 96K /mnt/SSD/iocage/templates
SSD/plugins 96K 215G 96K /mnt/SSD/plugins
boot-pool 10.8G 189G 24K none
boot-pool/.system 22.0M 189G 1.65M legacy
boot-pool/.system/configs-deb14d0c5cbc43b8883f8af65d933a1e 4.56M 189G 4.56M legacy
boot-pool/.system/cores 24K 1024M 24K legacy
boot-pool/.system/rrd-deb14d0c5cbc43b8883f8af65d933a1e 12.8M 189G 12.8M legacy
boot-pool/.system/samba4 182K 189G 79K legacy
boot-pool/.system/services 24K 189G 24K legacy
boot-pool/.system/syslog-deb14d0c5cbc43b8883f8af65d933a1e 2.81M 189G 2.81M legacy
boot-pool/.system/webui 24K 189G 24K legacy
boot-pool/ROOT 10.7G 189G 24K none
boot-pool/ROOT/12.0-U4 180K 189G 1.18G /
boot-pool/ROOT/12.0-U5 174K 189G 1.18G /
boot-pool/ROOT/12.0-U5.1 188K 189G 1.18G /
boot-pool/ROOT/12.0-U6 188K 189G 1.18G /
boot-pool/ROOT/12.0-U7 176K 189G 1.20G /
boot-pool/ROOT/12.0-U8 203K 189G 1.20G /
boot-pool/ROOT/12.0-U8.1 187K 189G 1.20G /
boot-pool/ROOT/13.0-RELEASE 10.7G 189G 1.28G /
boot-pool/ROOT/Initial-Install 1K 189G 1.16G legacy
pool 2.63T 4.50T 96K /mnt/pool
pool/iocage 712K 4.50T 136K /mnt/pool/iocage
pool/iocage/download 96K 4.50T 96K /mnt/pool/iocage/download
pool/iocage/images 96K 4.50T 96K /mnt/pool/iocage/images
pool/iocage/jails 96K 4.50T 96K /mnt/pool/iocage/jails
pool/iocage/log 96K 4.50T 96K /mnt/pool/iocage/log
pool/iocage/releases 96K 4.50T 96K /mnt/pool/iocage/releases
pool/iocage/templates 96K 4.50T 96K /mnt/pool/iocage/templates
pool/nas 2.63T 4.50T 2.63T /mnt/pool/nas
root@truenas[~]#
root@truenas[~]# iocage list
+-----+------+-------+---------+-----+
| JID | NAME | STATE | RELEASE | IP4 |
+=====+======+=======+=========+=====+
+-----+------+-------+---------+-----+

 

[Apollo]

Most likely the SSD pool is used for Jail storage.
You can change where iocage jail storage is located by going in GUI under the "Jails" section.
On the right side side on the "Jails" menu, there is a Gear icon. Select it and a popup will present "Choose Pool for Plugin and Jail Storage".
Make your selection to the pool "POOL" and jails should be switched over and activated.

 

[Patrick M. Hausen]

Is included in my previous output

And that's everything you have there? Only the newly created iocage datasets on "pool" and "SSD" and absolutely nothing on "nas"? I am trying to spot where your jails might have gone, that's why I asked for a full list of everything.

I have never seen an update actively delete datasets ...

 

[Christian K]

Most likely the SSD pool is used for Jail storage.
You can change where iocage jail storage is located by going in GUI under the "Jails" section.
On the right side side on the "Jails" menu, there is a Gear icon. Select it and a popup will present "Choose Pool for Plugin and Jail Storage".
Make your selection to the pool "POOL" and jails should be switched over and activated.

Thank you for your suggestion, but the jail selection is already set to pool "POOL".

What strikes me in #3 is that when activating the iocage for pool "POOL", it creates the folders for jail storage, indicating there were not there before.

I manually checked all subfolders of both pools, i.e. /mnt/pool/iocage/* and /mnt/SSD/iocage/* , and they are all empty.
My only conclusion is they were purged during the upgrade.

 

[Christian K]

And that's everything you have there? Only the newly created iocage datasets on "pool" and "SSD" and absolutely nothing on "nas"?

No,

 

[Apollo]

Have you tried restarting your system using the previous Boot Environment which had iocage working.
It is possible the location of the iocage mount point isn't under any of the pool (I have seen this on previous version version of Freenas on one of my pool).

 

[Christian K]

Have you tried restarting your system using the previous Boot Environment which had iocage working.
It is possible the location of the iocage mount point isn't under any of the pool (I have seen this on previous version version of Freenas on one of my pool).

Good point, I just did that, after booting into 12U8.1 ...

root@truenas[~]# iocage list
+-----+------+-------+---------+-----+
| JID | NAME | STATE | RELEASE | IP4 |
+=====+======+=======+=========+=====+
+-----+------+-------+---------+-----+

Alright, just void. The zfs list has not changed, no new mount points.
So I used that opportunity in trying to reproduce. I reinstalled the plugin

root@truenas[~]# iocage list
+-----+-----------+-------+--------------+------------+
| JID | NAME | STATE | RELEASE | IP4 |
+=====+===========+=======+==============+============+
| 2 | nextcloud | up | 12.3-RELEASE | 172.16.0.2 |
+-----+-----------+-------+--------------+------------+

and rebootet into 13.0-REL again.
Now, the plugin survived. that is odd.

 

[Apollo]

Good point, I just did that, after booting into 12U8.1 ...


Alright, just void. The zfs list has not changed, no new mount points.
So I used that opportunity in trying to reproduce. I reinstalled the plugin



and rebootet into 13.0-REL again.
Now, the plugin survived. that is odd.Chanign

Changing from boot environment will not force the issue if issue did actuall happen.
You couyld try upgrading again to 13 when you are in your 12U8.1 environment and see if anything change. It may not.

PS. Along the line of Corral, people have lost theire dataset during some update. Mosty likely a different issue but, Just to keep that in mind.