Restore a new ZFS install from a config file made on a UFS install
-
So I was able to upgrade to the ZFS install of the latest PFSense. I used the manual Restore method and everything seems alright (just wasn't that comfortable with the Autobackup and the other was so easy). I'll have to fully slot it in place of my current PFSense box to see if it's 100% working (and re-add my vlan) but seems good. One question: since I only have 1 hdd in the Del r210ii right now, is adding a mirror drive relatively easy? I assume it's from the command line and I'll need to learn a few ZFS commands, but guaging how easy to retrofit the mirror is (as opposed to building it that way from the start).
-
Hmm, interesting question, I've never tried.
My instinct there is that is would require reinstalling but ZFS is far more capable so....
More research needed.Steve
-
@rickybaker said in Restore a new ZFS install from a config file made on a UFS install:
I assume it's from the command line and I'll need to learn a few ZFS commands, but guaging how easy to retrofit the mirror is (as opposed to building it that way from the start).
Shouln't be a problem, though I haven't tried it myself: https://www.freebsd.org/doc/handbook/zfs-zpool.html the only thing that might be a bit risky is updating the bootcode with the correct one if you use UEFI boot. On the other hand, reinstalling pfSense with config recovery is likely to be equally as fast, if not faster.
-
@grimson said in Restore a new ZFS install from a config file made on a UFS install:
Shouln't be a problem, though I haven't tried it myself: https://www.freebsd.org/doc/handbook/zfs-zpool.html the only thing that might be a bit risky is updating the bootcode with the correct one if you use UEFI boot. On the other hand, reinstalling pfSense with config recovery is likely to be equally as fast, if not faster
Well shoot, i was thinking it would be easier than that. Oh well, guess I'll look into installing another harddrive and do this again:)
-
So, sorry to bump my old topic, but I was experiencing some issues with this install and I was wondering if it could be related to the ZFS I installed. I had it up and running on th enew Dell r210ii in my condo and tested it for weeks as my main router without issue. I unplug it and move it to the new house and it doesn't work (WAN gives an IP of 0.0.0.0). I troubleshoot for days before giving up and going back to my condo to grab the old ufs install of pfsense I used to run and that worked without issue. It theoretically should be identical to the ufs install besides the zfs, so I'm not sure what broke, but I'm about to reinstall pfsense and start over so I'd love to know if I should abandon zfs. (the reinstall and restore should identify if it's purely hardware of that NIC I suppose)...
-
That seems unlikely to be filesystem related. If it was I would expect some sort of error, if it couldn't read the dhclient conf fiel for example. But even so ZFS is less likely to have that sort of issue.
Steve
-
@stephenw10 said in Restore a new ZFS install from a config file made on a UFS install:
if it couldn't read the dhclient conf fiel for example. But even so ZFS is less likely to have that sort of issue.
I mean, it could be an error right? Or are you implying that reading 0.0.0.0 is indicative of normal (though unfortunate) behavior that belies there isn't an error. I haven't gotten around to reflashing pfsense, but I'm really hoping my NIC isn't shot...
-
I'm saying if there's a fault with the pfSense there it's probably not with reading the filesystem as much more would be broken then simply not pulling an IP address on WAN.
Check the DHCP logs.
Run a packet capture, make sure it's sending DHCP requests. See what, if anything, comes back.Steve
-
ok I'll look into how to do that immediately. Thanks for the suggestion
-
I would say zfs no question.
Its been in FreeBSD (the parent OS of PfSense), for a long time now and is stable on a kernel level, the filesystem is designed from the ground up with data resilience in mind.
Also since PfSense is primarily a network device in many cases there is hardly any i/o with writing of logs and graphs perhaps been the most intensive i/o expected. So even with zfs memory usage is not necessarily going to be large, on my 4 gig device I am using less then a gig of ram with zfs.
Ideally you want to use a mirror, but if you only have one storage, then as soon as possible post install I suggest setting copies=3 (providing you have the excess space), which will store each file written 3 times, to help with bit rot protection. (note tho this wont make copies of existing files only new files written, but typically the important stuff like rrd data, config files, logs etc. will be written to so will get the copies, losing things like binaries can be recovered on a new install anyway).
-
@chrcoluk said in Restore a new ZFS install from a config file made on a UFS install:
I would say zfs no question.
Its been in FreeBSD (the parent OS of PfSense), for a long time now and is stable on a kernel level, the filesystem is designed from the ground up with data resilience in mind.
Also since PfSense is primarily a network device in many cases there is hardly any i/o with writing of logs and graphs perhaps been the most intensive i/o expected. So even with zfs memory usage is not necessarily going to be large, on my 4 gig device I am using less then a gig of ram with zfs.
Ideally you want to use a mirror, but if you only have one storage, then as soon as possible post install I suggest setting copies=3 (providing you have the excess space), which will store each file written 3 times, to help with bit rot protection. (note tho this wont make copies of existing files only new files written, but typically the important stuff like rrd data, config files, logs etc. will be written to so will get the copies, losing things like binaries can be recovered on a new install anyway).
Thanks for that!! Where do I make the settings copies=3
-
If using default pfsense zfs installer, this should work.
zfs set copies=3 zroot
-
@chrcoluk said in Restore a new ZFS install from a config file made on a UFS install:
If using default pfsense zfs installer, this should work.
zfs set copies=3 zroot
Thanks, i wish this cleared it up more, but where exactly do I type this in? Can I do it after I've already installed pfsense or will I have to reinstall? I used the guided installer too, will I need to do something from the command line?
-
in the root shell
Its a live command, not even a reboot needed.
If you want to revert to default the command will be 'zfs set copies=1 zroot'.
-
@stephenw10 said in Restore a new ZFS install from a config file made on a UFS install:
Run a packet capture, make sure it's sending DHCP requests. See what, if anything, comes back.
So I figured out how to run a Packet Capture (still working on the DHCP logs, honestly I forgot until I came back to this post). This is what I got when I ran it on the WAN
I apologize for needing further assistance, but I'm not really sure how to decipher this (but it doesn't look right). Anything else I should do?
-
The logs are available in the GUI in Status > System Logs > DHCP tab. Look for dhclient entries on WAN.
That pcap shows all IPv6 packets so either it was filtered by IPv6 only or the WAN is not trying to pull an IP over v4. That fact there are no incoming v4 packets either makes it seem more like it was set to v6 only.
Steve
-
@stephenw10 said in Restore a new ZFS install from a config file made on a UFS install:
That fact there are no incoming v4 packets either makes it seem more like it was set to v6 only.
Well that's interesting. I'll try to run the logs tonight, Where would that "v6 only" setting most likely be set? in the set up for the interface? or on the modem? It's a Motorola MB7621 btw if that's useful. Would this not be a setting carried over when I restore from the backup of the currently-working zotac/barebones Ufs install?
-
In the packet capture. You can set filtering options there including 'Address Family: IPv6 Only'. It isn't set by default there though it would usually capture all packets so if that was not filtered then it's very odd to see no v4 traffic.
Try hitting DHCP lease renew or connect when the cap is running to at least send some v4 packets.
Steve
-
@stephenw10 said in Restore a new ZFS install from a config file made on a UFS install:
Try hitting DHCP lease renew or connect when the cap is running to at least send some v4 packets.
OK I will. I ran it without intentionally making any modifications to the pcap. Just selected WAN and started it. Is there a length of time that's recommended to run it? Is it possible I just stopped it too soon? I will do the DHCP lease renew when it's running and the second suggestion is DHCP lease CONNECT?
-
That looks like you ran it for 10s only so it's possible nothing happened there. I would run for a few minutes at least. If you set the pcap to IPv4 only that will make it easier to read. You should also increasr the maximum capture size to, say, 1000 packets.
Steve
