It's in the .system dataset, which by default is put on the first pool you create. It's generally mounted at /var/db/system/configs-longhexnumber.
Would this not be the new one as the boot USB is new and built from scratch as the 'old' boot USB hangs as stated below.
Now that I am thinking about it, I am not sure if getting this and uploading it as the config will help me.
The old boot drive was (is?) working, it is just hanging at command: zpool set cachefile=/data/zfs/zpool.cache DriveSpace.
If I get a config and get it applied to the new FreeNas boot USB that I have created, will it not just hang there also?
Maybe it would be better to import the volumes - doing a zpool import from the CLI gives me the following:
pool: DriveSpace
id: long number
state: ONLINE
status: the pool was last access by another system
action: the pool can be imported using its name or numeric.... etc etc...
config:
DriveSpace ONLINE
raidz2-0 ONLINE
gptid/lots of numbers ONLINE
gptid/lots of numbers ONLINE
gptid/lots of numbers ONLINE
gptid/lots of numbers ONLINE
gptid/lots of numbers ONLINE
cache
gptid/lots of numbers
gptid/lots of numbers
pool: Super
id: long number
state: ONLINE
status: the pool was last access by another system
action: the pool can be imported using its name or numeric.... etc etc...
config:
Super ONLINE
raidz1-0 ONLINE
gptid/lots of numbers ONLINE
gptid/lots of numbers ONLINE
gptid/lots of numbers ONLINE
cache
gptid/lots of numbers
Given that, what do you think would be my best options?
Sure I would have to rebuild 3 VM's but I can do that, and add a couple of users and access across the network, but that is not that much work.
Comments?
Thanks so much all!
IW