I wanted to inform you about an issue I have now when I use APU with Pfsense.
The storage solution inside the APU is SSD from your store.
Many customers that had an electric power down failure are not able to reboot the APU. If I connect a serial cable in order to see what is coming, I can see that Pfsense is loading after that it seems that a file is corrupted or missing and the APU reboot.
I didn't have this issue in the past with ALIX and COMPACT FLASH cards.
the exact error message would be helpful in order to help you. You don't even mention if you refer to an APU1 or APU2. Why I mention this? After power failure my APU1 often comes back with a corrupt /var file system which requires manual fschecking, while my APU2C4 up to now always came up OK, content with the automatic fsck.
I don't run PFsense but that seems to be close enough to OpenBSD, which I'm running, to release a shot in the dark: fsck /dev/sdxy - the error message should give a hint which file system has to be checked manually.
have a nice day,
This is with APU2 and SSD M-SATA from the pcengine store.
The issue for me is when there is a power failure, because pfsense is most of the time the router on my customer site, I cannot connect remotely anymore...
The only solution is to come on site, connect a serial cable in order to see that pfsense failed to boot et the apu restart all the time. After that I plug again USB Key with pfsense installer in order to perfom new install on ssd.
This is my third case this week. I'm trying to received from my customer the "brocken pfsense".
Welcome to pfSense 2.3.2-RELEASE (Patch 1) on the 'pfSense' platform...
No core dumps found.
Creating symlinkpanic: ufs_dirbad: /: bad dir ino 1284097 at offset 512: mangled entry
cpuid = 1
KDB: enter: panic
[ thread pid 21 tid 100094 ]
Stopped at kdb_enter+0x3e: movq $0,kdb_why
db:0:kdb.enter.default> textdump set
db:0:kdb.enter.default> capture on
db:0:kdb.enter.default> run lockinfo
db:1:lockinfo> show locks
No such command
db:1:locks> show alllocks
No such command
db:1:alllocks> show lockedvnods
please. You might get better help there. Also you might ponder to install a sort of UPS. APUs are easily run off lead batteries which are charged with a small wall-wart type of power supply. To avoid problems with batteries discharging to around 10.5 Volts you may want to connect an up-converter to the battery, let's say convert to 15 Volts and a down-converter to that one to get down to 12 Volts after that. That way you insure a constant voltage of 12 Volts. Works fine here. Good converters are TRACO but there are cheaper ones often found on surplus market. There are also ready to deploy constant voltage battery converters off the shelf:
I'm only using the nanobsd (embedded) version of pfSense on the APUs. maybe this release is less prone to filesystem corruption? I'm running a few APUs with pfSense in the field and none of them gave me any trouble so far...