Installed RC1, iocage jail root, forgotten, can't set it back. No more jails.

[diskdiddler]

I've had this problem since RC1 came out, several people tried to help but now it's all gone quiet.


My iocage jails were converted from warden and had an empty "release" flag, this broke me being able to reconfigure the iocage jail location.

My data, died appear to still be in the correct location, but freenas refuses to talk to it.

https://redmine.ixsystems.com/issues/52637 well discussed here.


Someone else is having it here also.

https://forums.freenas.org/index.ph...-rc1-and-jails-and-plugins-are-missing.70763/

 

[kdragon75]

I use the migration script in 11.1U6 and this left an "empty" string in the release field for me too. I was able to verify my jails versions by running freebsd-version and copying that into the jail config.json (/mnt/iocage/jails/<jail_name>/config.json) from here I was even able to run iocage upgrade <jail_name> -r 11.1-RELEASE to bring them all up to 11.1.

I just looked over the ticket listed in the other post. You may also need to use iocage fetch -r 11.1-RELEASE or what ever versions your using. If I understand correctly, iocage as setup in FreeNAS tries to use ZFS clones of the -RELEASE datasets as the base for new jails. Though I'm not sure why a migrated jail (a full independent dataset) would complain about the missing -RELEASE dataset but I have no clue how the middleware handles things...

 

[diskdiddler]

I use the migration script in 11.1U6 and this left an "empty" string in the release field for me too. I was able to verify my jails versions by running freebsd-version and copying that into the jail config.json

That advise is in the thread for the bug I reported and I have indeed done that.
I thought the command was slightly more complicated? Executing the .sh for each jail individually, to confirm the version of FreeBSD for jail /itself/ not just FreeNAS?
Regardless, it's been done.

(/mnt/iocage/jails/<jail_name>/config.json) from here I was even able to run iocage upgrade <jail_name> -r 11.1-RELEASE to bring them all up to 11.1.

My jails section is broken though, there are no jails listed - despite being in /mnt/iocage/jails/ (about 10 folders) NONE are in the list, so, I think iocage can't 'talk' to the jails?

I just looked over the ticket listed in the other post. You may also need to use iocage fetch -r 11.1-RELEASE or what ever versions your using. If I understand correctly, iocage as setup in FreeNAS tries to use ZFS clones of the -RELEASE datasets as the base for new jails. Though I'm not sure why a migrated jail (a full independent dataset) would complain about the missing -RELEASE dataset but I have no clue how the middleware handles things...

Bear in mind, I can't RUN any iocage commands, due to this.

Code:

root@freenas:~ # iocage list
Traceback (most recent call last):
  File "/usr/local/bin/iocage", line 10, in <module>
	sys.exit(cli())
  File "/usr/local/lib/python3.6/site-packages/click/core.py", line 722, in __call__
	return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/click/core.py", line 697, in main
	rv = self.invoke(ctx)
  File "/usr/local/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
	return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.6/site-packages/click/core.py", line 895, in invoke
	return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.6/site-packages/click/core.py", line 535, in invoke
	return callback(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/iocage_cli/list.py", line 81, in cli
	dataset_type, header, _long, _sort, plugin=plugins, quick=quick)
  File "/usr/local/lib/python3.6/site-packages/iocage_lib/iocage.py", line 1150, in list
	quick=quick
  File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_list.py", line 75, in list_datasets
	_all = self.list_all(ds)
  File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_list.py", line 153, in list_all
	conf = iocage_lib.ioc_json.IOCJson(mountpoint).json_load()
  File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_json.py", line 407, in json_load
	conf = self.json_check_config(conf)
  File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_json.py", line 910, in json_check_config
	with open(freebsd_version, "r") as r:
FileNotFoundError: [Errno 2] No such file or directory: '/mnt/iocage/releases/10.3-RELEASE/root/bin/freebsd-version'
root@freenas:~ #

 

[8-bit Yoda]

Have you tried if you can download that missing 10.3-RELEASE?

Code:

iocage fetch -r 10.3-RELEASE --noeol

 

[diskdiddler]

Have you tried if you can download that missing 10.3-RELEASE?

Code:

iocage fetch -r 10.3-RELEASE --noeol

You're the first to suggest this, I'll give it a shot and see what happens. I hope it's not as simple as that.

 

[diskdiddler]

Have you tried if you can download that missing 10.3-RELEASE?

Code:

iocage fetch -r 10.3-RELEASE --noeol

and there it is, thank you so much. Jeez.
I had to run it, a second time for FreeBSD 11.0 (as well as the 10.3 you noted)

Done, I'm back, holy crap. I thought they were all gone.


_NOW_ to figure out a comprehensive and through backup policy (and I've recently come to learn, snapshots are NOT good enough unfortunately, at all)

 

[kdragon75]

_NOW_ to figure out a comprehensive and through backup policy (and I've recently come to learn, snapshots are NOT good enough unfortunately, at all)

Snapshots are perfect for this. Setup a recursive one on the iocage dataset and then you can zfs send that anywhere including an archive file that you can again transfer anywhere you need.

 

[kdragon75]

I just looked over the ticket listed in the other post. You may also need to use iocage fetch -r 11.1-RELEASE or what ever versions your using

Just wanted to point out it did suggest using iocage fetch.

 

[diskdiddler]

Snapshots are perfect for this. Setup a recursive one on the iocage dataset and then you can zfs send that anywhere including an archive file that you can again transfer anywhere you need.

My root folder was lost, destroying my snapshots. I want a manual backup I can pick files out of.

 

[kdragon75]

The point is that you can use snapshots and maintain all zfs properties and move the data off the nas and have it independent of the root folder or other snapshots. If you just want the files, you should use rsync

 

[diskdiddler]

The point is that you can use snapshots and maintain all zfs properties and move the data off the nas and have it independent of the root folder or other snapshots. If you just want the files, you should use rsync

Thanks for your help. I've ended up discussing this here.
https://forums.freenas.org/index.ph...age-jail-s-backup-_not_-just-snapshots.70940/

I have some resistance to snapshots (as discussed there) and like the idea of other options too, welcome to chime in.
Otherwise this thread can die, thanks again to both of you.