@chidinmairene space key to select your 4 disks to run Raid10 else choose a different raid if you don't have 4 disks

Looks like it : [image: 1632732118740-cf48c3bb-8803-4de2-83c8-294a4a986c71-image.png]

@johnpoz said in Upgrade OpenSSH 8.7: the version of ssh that comes with pfsense will be the one that is included with freebsd. When freebsd updates their version, then pfsense will update. Yeah its a bit dated.. Complain to freebsd about that ;) thanks much ;)

@steveits Thanks. I already tried all of those options. I have requested the link as you mentioned. Rich

@fireblade OK After a reinstall of pkg the signiture issue with pkg-static appears to be working pkg install -fy pkg

The easy solution: Create a pfSense VM with virtualbox Load packages and settings from your bare metal device Verify the config works as bare metal. Shut the VM down Restore: Use vboxmanage to convert vdi to vhd Use rufus to load the vhd on the ram device (taken out of the bare device mounted via usb) Place storage back, done. (and tested) I'm gonna test the reverse (take bare metal in to a VM) but have no doubts this will work. nb. cloning the storage device as backup also works.

Try to reimage the appliance with 21.05.1 ask support@netgate.com

Hmm, nothing unexpected logged there. You don't have any system logs from the time? Steve

@jimp yes sir, from the shell prompt.

I can find the sbin directory and the fsck command by using 'ls', but I can't seem to execute the command. I also can't use 'cd'. I tried /sbin/fsck but it didn't work.

@rico said in Config recovery dilemma on ZFS install: Good question, from my understanding it should be fixed in 2.5.2-RELEASE hmmm. Anyway, I Re- downloaded the 2.5.2 Image from Netgate to be sure that I have a recent Image. Its not a "Big Deal" cause I have always a actual config file but if the recovery would work it would save some time ...

The installer will delete any existing partitions. The only time I'm aware of that it won't do that is if you have an existing geom mirror defined. It will install into that instead. If you use the default options you should never see the above error. You would only see that if you removed the default configured root partition and do not add another one. You might hit that if, for example, you remove the swap partition and want to re-create root to fill the space. Steve

@bmeeks Thank you very much.

@wn As KOM says open a ticket. You should get free support as it's a Netgate device. ("zero to ping")

OK, closing out this thread and linking it to another. The root cause of the problem I reported is that on the MBT board, the ZFS module combined with the i915 HDMI module exhausts the available EFI staging area. I don't fully understand the details, but thanks to help from @stephenw10 the solution is relatively simple: just reinstall pfSense and use UFS for the file system rather than ZFS. I have confirmed this works with CE 2.5.1. If you want to see additional details, this thread has more information. So glad that this issue can finally be put to bed!

I ran a number of APU2 devices on ZFS. The memstick method was successful but slow, so I created my own dd image (via ubuntu live disk). and then used Etcher to create new SD Cards in order build the rest of the APU2 devices.

For anyone finding this in future, I am glad to report that my router upgrades were successful (thank you pfSense team and contributors). I did have to go from 2.4.4_3 to 2.4.5_1 first (on both the 7100 and the 3100). After the upgrade, I did not touch any of the plugins, changed the update branch to latest and rebooted again (just to be sure). Then I was able to go from 2.4.5_1 straight to 21.05 and it even then upgraded all the plugins to the latest for me. It did take me several hours because I had two routers to do, I had CARP failover and IPSec tunnels and I waited to make sure none of my alerting systems went crazy. But the actual upgrade process was suprisingly and refreshingly straight forward without any drama.

I wouldn't expect you to have to run an upgrade more than once. It may have updated the pkg repo itself and then found newer packages. It should have just done that without requiring any interaction though. When it says The process will require 4 MiB more space. that just means the updated packages will be 4MB larger than before the update. That's expected and not filesystem space issue. Steve