Update went wrong

[Basil Hendroff]

Do you have an offline backup of the data eg. on a local PC drive? Btw, are you aware your server hardware is not ideal? It's probably ok as an experimental platform, but if you intend to get serious with FreeNAS, I wouldn't be relying on it? Check the basic hardware requirements for FreeNAS at https://www.freenas.org/hardware-requirements/

 

[csearle]

Im mainly using it as an Media Server..

 

[Basil Hendroff]

There are some pretty serious guides out there to retrospectively create a mirror, for example, https://dawning.ca/2017/freenas-11-add-a-drive-to-create-a-mirrored-zfs-volume/. However, they are not for the faint-hearted.

Seeing as we're talking about 1.5TB of data, the easiest approach for you might be to blow away the two pools and then recreate a single 2TB mirrored pool. However, before even contemplating this approach, the first step is to ensure you have an adequate backup of the data. Note also that if you decide to go down this path, you will need to be prepared to recreate any jails you have set up.

 

[csearle]

Im already having issues setting up plugins and jails I deleted all my old datasets from the Legacy side and from the new 11.2 Side the only dataset I can't delete is the iocage Date set..

I thought If I deleted those datasets id be able to start from sorta fresh with out wiping out all my data and starting fresh

 

[csearle]

Do you have an offline backup of the data eg. on a local PC drive? Btw, are you aware your server hardware is not ideal? It's probably ok as an experimental platform, but if you intend to get serious with FreeNAS, I wouldn't be relying on it? Check the basic hardware requirements for FreeNAS at https://www.freenas.org/hardware-requirements/

Im backing up to an external HD right now

 

[Basil Hendroff]

I'm also concerned that it isn't going to take you long to fill up the remaining 0.5 TB of free space on the mirror, so this is going to be a very short term fix. I'm going offline now. It might be daytime where you are, but it's way past midnight here. Anyway, focus on getting a complete offline backup of your data for now. Given there are quite a few posts on the forum discussing issues with 11.2, you may also want to consider sticking with 11.1 for a while longer.

 

[csearle]

thank you!!! I guess im luck that I still have an installer file with 11.1 on it

 

[Basil Hendroff]

Btw, FreeNAS takes a performance hit if your pool exceeds 80% capacity. You're probably already there and you should consider replacing the 2TB disks before you create the mirror.

 

[csearle]

I undrastand that, I was a complete noob and put my complete movie collection on one of the drives to make it easier to copy back and forth from drive to drive. I have Backed up all my data on to the external Hard Drive. Thinking about it last night I think it would be better to have my movie collection on an external drive and keep my NAS smaller, It was recommended that I should get serious about NAS, when I first found about Freenas it was in 9.xx.xx still and anyone could run any kind of hardware on it. Im still thinking like that.. Im using the Freenas just for Plex, transmission and Time Machine.. is there a way to use one drive and have it duplicate onto the the second drive???

 

[Basil Hendroff]

I think it would be better to have my movie collection on an external drive

The data on your external drive serves as a snapshot of the data that is on your NAS at a point in time. In simplistic terms. FreeNAS operates on storage that is internal to the NAS, not external to the NAS.

when I first found about Freenas it was in 9.xx.xx still and anyone could run any kind of hardware on it

Not true. There has always been a recommended minimum hardware spec. Like I said earlier, what you've got is probably ok as an experimental platform, but if you're depending on it, which it looks like you are, your hardware will be expected to meet the basic hardware requirements for FreeNAS https://www.freenas.org/hardware-requirements/. If you choose to cut corners, forum members are less likely to be empathetic to a problem you are experiencing and your post may be ignored.

is there a way to use one drive and have it duplicate onto the second drive???

That is exactly what a mirror does. The added benefit of a mirror is disk redundancy. If one of the disks fails, your NAS will continue to operate. Thereafter, if the second disk fails, your NAS fails catastrophically. So it's important to replace the first failed disk as soon as you become aware of it.

In this thread, you've been made aware that you're on pretty shaky ground in terms of your FreeNAS hardware and software configuration. You're free to ignore the advice you've been provided as long as you're prepared to deal with the consequences of ignoring that advice.

 

[csearle]

I don’t want to ignore the advice and I don’t plan to.. I’m just looking for help, if I was wasn’t trying I wouldn’t be here.

I’m sure I’m not the only one on here managing with the parts I find or parts that come my way.. I could go with my rant on how ram and WD-red drives are out of my league..

 

[csearle]

So I took peoples advice from this thread and I Started from scratch I deleted pools and datasets, I set up both drives a mirror 0 so I could have some redundancy in my system.. I set up a few datasets and learnt allot from other threads and you tube videos.. Im no expert on this NAS system..

I come from the days Freenas was easier to use and install where we could use any network and video card and any drives. Im mainly using this NAS as a Media Share, device. I'm not to worried about losing TV shows or Movies files they can be easily replaced.

My main goal was to set up PLEX and TRANSMISSION I had a few complications but I came threw on top after reading some threads on here..

Im going to Run What I Brung

 

[AltecBX]

The config db file is named freenas-v1.db and is located at: /data
However, if that directory is located on the USB boot device that is failed, this may not help at all.
You can recover a copy that is automatically saved for you in the system dataset, if the system dataset is on the storage pool.
For people like me, I moved the system dataset to the boot pool, this is no help, but the default location of the system dataset is on the storage pool.
If you do a fresh install of FreeNAS on a new boot media, and import the storage pool, you should find the previous config db at this path:
/var/db/system/ plus another directory that will be named configs-****random_characters****.
Mine looks like this:
View attachment 28739
Inside that long random number named directory is the history of all you old configs, like this:
View attachment 28740
It is kind of tricky to cd into one of those directories because you must "escape" some of the characters, so the command looks like this:
cd FreeNAS-11.1-U7\ \(b45bfcf29\)/
Inside there, is a history of the config databases named by date like this:
View attachment 28741

I hope this can help someone.

Hi Chris, I'm trying to follow this but get lost after root@FreeNAS[/var/db/system]# .

 

[Chris Moore]

Hi Chris, I'm trying to follow this but get lost after root@FreeNAS[/var/db/system]# .

Here is what the path looks like on my system, but the long random numbers in this will be different for your system:
cd /var/db/system/configs-7f5b34811f49423b82ac573d9dd30fdd/FreeNAS-11.1-U7\ \(b45bfcf29\)/

and this is the directory at the end of that:

Code:

root@Emily-NAS:~ # cd /var/db/system/configs-7f5b34811f49423b82ac573d9dd30fdd/FreeNAS-11.1-U7\ \(b45bfcf29\)/
root@Emily-NAS:/var/db/system/configs-7f5b34811f49423b82ac573d9dd30fdd/FreeNAS-11.1-U7 (b45bfcf29) # ll
total 5365
-rw-r-----  1 root  wheel  411648 Jan 28 03:45 20190128.db
-rw-r-----  1 root  wheel  411648 Jan 29 03:45 20190129.db
-rw-r-----  1 root  wheel  411648 Jan 30 03:45 20190130.db
-rw-r-----  1 root  wheel  411648 Jan 31 03:45 20190131.db
-rw-r-----  1 root  wheel  411648 Feb  1 03:45 20190201.db
-rw-r-----  1 root  wheel  411648 Feb  2 03:45 20190202.db
-rw-r-----  1 root  wheel  411648 Feb  3 03:45 20190203.db
-rw-r-----  1 root  wheel  411648 Feb  4 03:45 20190204.db
-rw-r-----  1 root  wheel  411648 Feb  5 03:45 20190205.db
-rw-r-----  1 root  wheel  411648 Feb  6 03:45 20190206.db
-rw-r-----  1 root  wheel  411648 Feb  7 03:45 20190207.db
-rw-r-----  1 root  wheel  411648 Feb  8 03:45 20190208.db
-rw-r-----  1 root  wheel  411648 Feb  9 03:45 20190209.db
-rw-r-----  1 root  wheel  411648 Feb 10 03:45 20190210.db
-rw-r-----  1 root  wheel  411648 Feb 11 03:45 20190211.db
-rw-r-----  1 root  wheel  411648 Feb 12 03:45 20190212.db
-rw-r-----  1 root  wheel  411648 Feb 13 03:45 20190213.db
-rw-r-----  1 root  wheel  411648 Feb 14 03:45 20190214.db
-rw-r-----  1 root  wheel  411648 Feb 15 03:45 20190215.db
-rw-r-----  1 root  wheel  411648 Feb 16 03:45 20190216.db
-rw-r-----  1 root  wheel  411648 Feb 17 03:45 20190217.db
-rw-r-----  1 root  wheel  411648 Feb 18 03:45 20190218.db
-rw-r-----  1 root  wheel  411648 Feb 19 03:45 20190219.db
-rw-r-----  1 root  wheel  411648 Feb 20 03:45 20190220.db
-rw-r-----  1 root  wheel  411648 Feb 21 03:45 20190221.db
-rw-r-----  1 root  wheel  411648 Feb 22 03:45 20190222.db
-rw-r-----  1 root  wheel  411648 Feb 23 03:45 20190223.db
-rw-r-----  1 root  wheel  411648 Feb 24 03:45 20190224.db
-rw-r-----  1 root  wheel  411648 Feb 25 03:45 20190225.db
-rw-r-----  1 root  wheel  411648 Feb 26 03:45 20190226.db
-rw-r-----  1 root  wheel  411648 Feb 27 03:45 20190227.db
-rw-r-----  1 root  wheel  411648 Feb 28 03:45 20190228.db
-rw-r-----  1 root  wheel  411648 Mar  1 03:45 20190301.db
-rw-r-----  1 root  wheel  411648 Mar  2 03:45 20190302.db
-rw-r-----  1 root  wheel  411648 Mar  3 03:45 20190303.db
-rw-r-----  1 root  wheel  411648 Mar  4 03:45 20190304.db
-rw-r-----  1 root  wheel  411648 Mar  5 03:45 20190305.db
-rw-r-----  1 root  wheel  411648 Mar  6 03:45 20190306.db
-rw-r-----  1 root  wheel  411648 Mar  7 03:45 20190307.db
-rw-r-----  1 root  wheel  411648 Mar  8 03:45 20190308.db
-rw-r-----  1 root  wheel  411648 Mar  9 03:45 20190309.db
-rw-r-----  1 root  wheel  411648 Mar 10 03:45 20190310.db
-rw-r-----  1 root  wheel  411648 Mar 11 03:45 20190311.db
-rw-r-----  1 root  wheel  411648 Mar 12 03:45 20190312.db
-rw-r-----  1 root  wheel  411648 Mar 13 03:45 20190313.db
-rw-r-----  1 root  wheel  411648 Mar 14 03:45 20190314.db
-rw-r-----  1 root  wheel  411648 Mar 15 03:45 20190315.db
-rw-r-----  1 root  wheel  411648 Mar 16 03:45 20190316.db
-rw-r-----  1 root  wheel  411648 Mar 17 03:45 20190317.db
-rw-r-----  1 root  wheel  411648 Mar 18 03:45 20190318.db
-rw-r-----  1 root  wheel  411648 Mar 19 03:45 20190319.db
-rw-r-----  1 root  wheel  411648 Mar 20 03:45 20190320.db
-rw-r-----  1 root  wheel  411648 Mar 21 03:45 20190321.db
-rw-r-----  1 root  wheel  411648 Mar 22 03:45 20190322.db
-rw-r-----  1 root  wheel  411648 Mar 23 03:45 20190323.db
-rw-r-----  1 root  wheel  411648 Mar 24 03:45 20190324.db
root@Emily-NAS:/var/db/system/configs-7f5b34811f49423b82ac573d9dd30fdd/FreeNAS-11.1-U7 (b45bfcf29) #

 

[AltecBX]

Here is what the path looks like on my system, but the long random numbers in this will be different for your system:
cd /var/db/system/configs-7f5b34811f49423b82ac573d9dd30fdd/FreeNAS-11.1-U7\ \(b45bfcf29\)/

and this is the directory at the end of that:

Code:

root@Emily-NAS:~ # cd /var/db/system/configs-7f5b34811f49423b82ac573d9dd30fdd/FreeNAS-11.1-U7\ \(b45bfcf29\)/
root@Emily-NAS:/var/db/system/configs-7f5b34811f49423b82ac573d9dd30fdd/FreeNAS-11.1-U7 (b45bfcf29) # ll
total 5365
-rw-r-----  1 root  wheel  411648 Jan 28 03:45 20190128.db
-rw-r-----  1 root  wheel  411648 Jan 29 03:45 20190129.db
-rw-r-----  1 root  wheel  411648 Jan 30 03:45 20190130.db
-rw-r-----  1 root  wheel  411648 Jan 31 03:45 20190131.db
-rw-r-----  1 root  wheel  411648 Feb  1 03:45 20190201.db
-rw-r-----  1 root  wheel  411648 Feb  2 03:45 20190202.db
-rw-r-----  1 root  wheel  411648 Feb  3 03:45 20190203.db
-rw-r-----  1 root  wheel  411648 Feb  4 03:45 20190204.db
-rw-r-----  1 root  wheel  411648 Feb  5 03:45 20190205.db
-rw-r-----  1 root  wheel  411648 Feb  6 03:45 20190206.db
-rw-r-----  1 root  wheel  411648 Feb  7 03:45 20190207.db
-rw-r-----  1 root  wheel  411648 Feb  8 03:45 20190208.db
-rw-r-----  1 root  wheel  411648 Feb  9 03:45 20190209.db
-rw-r-----  1 root  wheel  411648 Feb 10 03:45 20190210.db
-rw-r-----  1 root  wheel  411648 Feb 11 03:45 20190211.db
-rw-r-----  1 root  wheel  411648 Feb 12 03:45 20190212.db
-rw-r-----  1 root  wheel  411648 Feb 13 03:45 20190213.db
-rw-r-----  1 root  wheel  411648 Feb 14 03:45 20190214.db
-rw-r-----  1 root  wheel  411648 Feb 15 03:45 20190215.db
-rw-r-----  1 root  wheel  411648 Feb 16 03:45 20190216.db
-rw-r-----  1 root  wheel  411648 Feb 17 03:45 20190217.db
-rw-r-----  1 root  wheel  411648 Feb 18 03:45 20190218.db
-rw-r-----  1 root  wheel  411648 Feb 19 03:45 20190219.db
-rw-r-----  1 root  wheel  411648 Feb 20 03:45 20190220.db
-rw-r-----  1 root  wheel  411648 Feb 21 03:45 20190221.db
-rw-r-----  1 root  wheel  411648 Feb 22 03:45 20190222.db
-rw-r-----  1 root  wheel  411648 Feb 23 03:45 20190223.db
-rw-r-----  1 root  wheel  411648 Feb 24 03:45 20190224.db
-rw-r-----  1 root  wheel  411648 Feb 25 03:45 20190225.db
-rw-r-----  1 root  wheel  411648 Feb 26 03:45 20190226.db
-rw-r-----  1 root  wheel  411648 Feb 27 03:45 20190227.db
-rw-r-----  1 root  wheel  411648 Feb 28 03:45 20190228.db
-rw-r-----  1 root  wheel  411648 Mar  1 03:45 20190301.db
-rw-r-----  1 root  wheel  411648 Mar  2 03:45 20190302.db
-rw-r-----  1 root  wheel  411648 Mar  3 03:45 20190303.db
-rw-r-----  1 root  wheel  411648 Mar  4 03:45 20190304.db
-rw-r-----  1 root  wheel  411648 Mar  5 03:45 20190305.db
-rw-r-----  1 root  wheel  411648 Mar  6 03:45 20190306.db
-rw-r-----  1 root  wheel  411648 Mar  7 03:45 20190307.db
-rw-r-----  1 root  wheel  411648 Mar  8 03:45 20190308.db
-rw-r-----  1 root  wheel  411648 Mar  9 03:45 20190309.db
-rw-r-----  1 root  wheel  411648 Mar 10 03:45 20190310.db
-rw-r-----  1 root  wheel  411648 Mar 11 03:45 20190311.db
-rw-r-----  1 root  wheel  411648 Mar 12 03:45 20190312.db
-rw-r-----  1 root  wheel  411648 Mar 13 03:45 20190313.db
-rw-r-----  1 root  wheel  411648 Mar 14 03:45 20190314.db
-rw-r-----  1 root  wheel  411648 Mar 15 03:45 20190315.db
-rw-r-----  1 root  wheel  411648 Mar 16 03:45 20190316.db
-rw-r-----  1 root  wheel  411648 Mar 17 03:45 20190317.db
-rw-r-----  1 root  wheel  411648 Mar 18 03:45 20190318.db
-rw-r-----  1 root  wheel  411648 Mar 19 03:45 20190319.db
-rw-r-----  1 root  wheel  411648 Mar 20 03:45 20190320.db
-rw-r-----  1 root  wheel  411648 Mar 21 03:45 20190321.db
-rw-r-----  1 root  wheel  411648 Mar 22 03:45 20190322.db
-rw-r-----  1 root  wheel  411648 Mar 23 03:45 20190323.db
-rw-r-----  1 root  wheel  411648 Mar 24 03:45 20190324.db
root@Emily-NAS:/var/db/system/configs-7f5b34811f49423b82ac573d9dd30fdd/FreeNAS-11.1-U7 (b45bfcf29) #

I have 2 folders that start with configs but they're empty. Look at attached pictures.

 

[Version3]

well, the idea did 'work' in that in started populating backups in one of those folders in /var (as in the post above), but it only has a backup with today's date on it. I'm guessing it wasn't storing this data where I'd like previously, so there is nothing to pull over and surface.

I appreciate the help... I'll just have to manually set up users and install Plex again and let it run as it does. I'm just glad I didn't lose all of my data.

 

[Version3]

well, the idea did 'work' in that in started populating backups in one of those folders in /var (as in the post above), but it only has a backup with today's date on it. I'm guessing it wasn't storing this data where I'd like previously, so there is nothing to pull over and surface.

I appreciate the help... I'll just have to manually set up users and install Plex again and let it run as it does. I'm just glad I didn't lose all of my data.

We rally should have the ability to delete our own posts for at least a few minutes; this was posted to the wrong thread. Apologies.