New Boot Drive, Config File lost, need help

[Kenfolk]

For starters I'm on build FreeNAS-11.1-U4. My old USB boot drive literally burned out, was extremely hot to the touch and upon cooling down wouldn't be recognized on any machine I plugged it into so I'm guessing it is totally dead. So I just finished installing to a new USB drive, went to upload my saved config file and come to find out it is corrupt. I get errors when trying to upload it, and when I click on it on my computer it says it is damaged. I am really, really, really hoping I'm not totally screwed here and have to start over as I had over 30TB of data that I don't want to have to re put back on there and reconfigure everything. Is there anything I can do? Any way to salvage this? I need some major help

 

[Jailer]

It's available on the pool but I can't remember where it's located and cant find my last post regarding it. @danb35 should be able to assist.

 

[MrToddsFriends]

A collection of backups of config files (*.db) created automatically every day at 03:45 usually is available in the system dataset. Depending on the configuration of your system the system dataset resides on a data pool (which would be a good thing) or on freenas-boot (which would be a pity if that died together with your USB drive).

On a running system where volvar/.system/configs-[long-hex-number] is mounted to
/var/db/system/configs-[long-hex-number]:

Code:

root@blunzn:/var/db/system/configs-[long-hex-number] # ls -altr | tail -7
drwxr-xr-x   2 root  wheel  28 Jan 18 03:45 FreeNAS-11.1-RELEASE (dc7d195f4)
drwxr-xr-x   2 root  wheel  36 Feb 21 03:45 FreeNAS-11.1-U1 (f7e246b8f)
drwxr-xr-x   2 root  wheel  30 Mar 21 03:45 FreeNAS-11.1-U2 (c636d1f4b)
drwxr-xr-x   2 root  wheel   4 Mar 23 03:45 FreeNAS-11.1-U3 (bbd4bcb95)
drwxr-xr-x  42 root  wheel  42 Mar 24 03:45 .
drwxr-xr-x   2 root  wheel  65 May 25 03:45 FreeNAS-11.1-U4 (89e3d93bc)
drwxr-xr-x  10 root  wheel  13 May 25 04:49 ..
root@blunzn:/var/db/system/configs-[long-hex-number] # ls -altr FreeNAS-11.1-U4\ \(89e3d93bc\)/ | tail -7
-rw-r-----   1 root  wheel  407552 May 20 03:45 20180520.db
-rw-r-----   1 root  wheel  407552 May 21 03:45 20180521.db
-rw-r-----   1 root  wheel  407552 May 22 03:45 20180522.db
-rw-r-----   1 root  wheel  407552 May 23 03:45 20180523.db
-rw-r-----   1 root  wheel  407552 May 24 03:45 20180524.db
drwxr-xr-x   2 root  wheel	  65 May 25 03:45 .
-rw-r-----   1 root  wheel  407552 May 25 03:45 20180525.db

Of course [long-hex-number] as stated above is is a placeholder for a long hex number. volvar occurring once above is just the name of a pool. Hope this helps.

 

[MrToddsFriends]

Remember that it's "just" your config that might be lost if really no backup config file is available any more. If all else fails you should be able to import your data pool and redo your config manually from within a fresh FreeNAS installation.

 

[Kenfolk]

I hate to say it, but what you said didn't make any sense to me. Where do I figure out that long hex number? Also even after figuring out that and inputting that command, how do I get to the config backup itself if it exists?

 

[MrToddsFriends]

Also even after figuring out that and inputting that command, how do I get to the config backup itself if it exists?

Let's start with another detail: Do you know whether the system dataset resides on the boot pool or on the data pool (one of the data pools if more than one exist)?

For general information about the daily config backups see also (in the paragraph starting with "Save Config", does not answer your questions)
http://doc.freenas.org/11/system.html?#general

 

[Kenfolk]

I honestly don't remember ever messing with that setting, so more than likely it was backuping up to whatever is the default. I used Uncle Fester's guide when I set everything up and I don't recall it mentioning changing any settings for backing up the config (though if it did then I did change it).

 

[Kenfolk]

So quick update, I decided to just go ahead and run through the wizard and just set everything back up again. I did notice my jails folder was still there with my torrent client, is there any way I can use that folder to re setup my jail? I was seeding some 200 torrents that I don't want to go through again if at all possible

 

[MrToddsFriends]

While I can't help with your torrents please take a minute to check your system dataset settings.
http://doc.freenas.org/11/system.html?#system-dataset

The system dataset pool should not be located on freenas-boot if this boot pool consists of one USB stick (or two mirrored ones) as this causes a lot of write activity on these media (and thus wear and tear as well as heat).

 

[Kenfolk]

I'm definitely going to change that. I'm betting it was being written on the USB sticks since I've had a handful of them go bad over the past year which I thought was odd. I've also gone from a USB stick to a small SSD.

 

[Ericloewe]

No need to bet. Input your data pool. Is the system dataset there? If not, nothing lost. Otherwise save yourself the effort of rebuilding the configuration from scratch.