Well, I was unable to change VIMAGE or assign an actual interface, it simply will not allow me to do anything... I can click the checkbox on the VIMAGE in the jails configuration and it will not uncheck. I cannot start the plugin, it simply states "some error occured". The configurations appear to still be there, storage is correctly assigned, even though I deleted the failed upgrade and then later installed and deleted the plugin several times.
I did not get ANY useful information when using tail /var/log/messages in the Jail's own terminal, but in FreeNAS terminal, I got the following:
[root@freenas ~]#
[root@freenas ~]# tail /var/log/messages
Jul 16 17:09:23 freenas kernel: epair1a: promiscuous mode enabled
Jul 16 17:09:23 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Jul 16 17:09:23 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Jul 16 17:09:23 freenas devd: Executing '/etc/pccard_ether epair1b start'
Jul 16 17:09:23 freenas devd: Executing '/etc/rc.d/dhclient quietstart epair1a'
Jul 16 17:09:24 freenas mDNSResponder: mDNS_Execute: SendResponses didn't send all its responses; will try again in one second
Jul 16 17:09:24 freenas mDNSResponder: mDNS_Execute: SendResponses didn't send all its responses; will try again in one second
Jul 16 17:09:24 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 00000008014D0D60 freenas.local.
(Addr) that's already in the list
Jul 16 17:09:24 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 00000008014D1180 118.100.168.192
.in-addr.arpa. (PTR) that's already in the list
Jul 16 17:09:34 freenas manage.py: [freeadmin.navtree:631] An error occurred while unserializing from
http://192.168.100.118/plugins
/syncthing/5/_s/treemenu: No JSON object could be decoded
[root@freenas ~]#
It appears something has gone wrong.... And unlike a normal install of a Linux distribution where I could simply nuke and pave, I believe that the faulty settings or whatever they are, are stored somewhere in the storage pool and not on the thumb drives, right? Is there some why of restoring the default install so I can re-install plugins and redo my configurations?
For what it's worth, my hardware consists of a quad core Intel atom based Asrock board with 16Gb of ecc ram and 5 2TB drives. Unfortunately, I did not set up snapshots of the entire storage pool, but rather just the individual datasets to protect their stored data, or perhaps I could have rolled it back that way?
My Transmission plugin is still going strong, as was the Syncthing plugin until my failed update.