PC Engines apu2 experiences
-
@logan5247 this really should get its own zfs thread, it has nothing to do with the apu2
-
@vamike I agree, but quickly in summary, you're always running the one without the @ sign - that's the current live version. You can see that the size of the "backup" of zroot is nothing. The size of zroot/ROOT/default's backup is bigger. zroot doesn't include the other, effectively, "partitions".
-
@dem said in PC Engines apu2 experiences:
@vollans I did a quick test in a virtual machine to figure out what the commands would be. This appears to work:
On a running 2.4.5-p1 system:
zpool checkpoint zroot
Booted from the 2.5.0 installer and in the Rescue Shell:
zpool import -f -N --rewind-to-checkpoint zroot zpool export zroot poweroff
I would like to know how you booted from the 2.5.0 installer using a virtual pfsense machine and got to the Rescue Shell?
-
@qinn In VirtualBox I put the file
pfSense-CE-2.5.0-RELEASE-amd64.iso
in the virtual optical drive and booted to this screen, where I selected Rescue Shell: -
@dem Thanks for the quick reply, I understand that.
What I would like to know is how you get to the Virtual pfSense from here as the virtual pfsense machine is not running and access the checkpoint you made?Btw I am using VM workstation!
-
@qinn Sorry I wasn't clear: I put the installer image into the virtual optical drive of the same virtual pfSense instance that I checkpointed, so the installer has access to the same virtual disk and can locate the checkpointed
zroot
pool.Edited to add: My goal was to simulate booting an apu2 from the
memstick
image in order to rewind a checkpoint, but I don't have a spare apu2 to test with. If I actually ran pfSense in a virtual machine I would use virtual machine snapshots before any upgrade. -
@qinn I never would have guessed this was somehow specific to the apu2
-
-
@dem so he should start another thread so that people actually interested in apu2 experiences can find those without digging through unrelated zfs support questions
-
@vamike I agreed it wasn't relevant here 2 days ago, and stopped responding.
-
Why pfsense 2.5 shows "AES-NI CPU Crypto: No" when in 2.4.x there was YES on APU2? Also on 2.5 there is in other line: Hardware crypto AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS
-
@sikita said in PC Engines apu2 experiences:
Why pfsense 2.5 shows "AES-NI CPU Crypto: No" when in 2.4.x there was YES on APU2?
Anything to do with this problem? If so, it appears to be fixed in 2.5.1.
-
@bigsy Ok, thank you. Seems to be GUI bug and does not involve using HW crypto.
-
@sikita I am on pfSense 2.5.0 and here it says:
Do you have AES-NI enabled?
-
Can anyone share there System / Advanced / Networking on a APU2
Mine are
as these are the defaults, grabbed them from a VM installation, which is not quit the same setup.
The old and not anymore recommend settings from https://teklager.se/en/knowledge-base/apu2-1-gigabit-throughput-pfsense/ are quit different!
...and there is a new settings present in 2.5.0. " hn ALTQ support"
Could anyone elaborate on all these or there settings?
-
There are no hn NICs on any APU so it makes no difference. You can disable it.
Steve
-
I performed all the bootloader and other tweaks mentioned in various threads throughout the years on my <= 2.45-p1 installation and now I don't remember what they all are. It would be great if somebody could post what things to look for (to remove?) when you update your apu2 from 2.4.5 --> 2.5.0.
At the moment because of the performance issues, I'm not upgrading.
-
@valnar said in PC Engines apu2 experiences:
when you update your apu2 from 2.4.5 --> 2.5.0.
Hi,
With that, I would wait a little longer
here,....you will find a lot of useful info if you even decide to upgrade...
https://teklager.se/en/knowledge-base/
https://teklager.se/en/knowledge-base/apu2-1-gigabit-throughput-pfsense/+++edit:
and of course
https://pcengines.github.io/ -
Smooth update to pfSense 2.5.1 CE
-
Updated to bios coreboot v4.13.05.