2.2.2 -> 2.2.3 NanoBSD APU required hard power cycle
vynce last edited by
I auto-updated a remote APU from 2.2.2 to 2.2.3 last night (NanoBSD running on an SD card). The unit either didn't reboot or didn't start up properly after rebooting. Either way, it was not accessible over the network. A hard power cycle got it running again though. I noticed that the case was pretty warm, so it was probably stuck in a high-power state (?). The upgrade log is attached. Let me know if I can provide any other info.
skinnert last edited by
When I auto-upgraded my APU from 2.2.2 to 2.2.3 I also had the device eventually hang and lockup requiring a hard reboot.
Except when mine came back up I was getting a Kernel not found error.
Using my original 2.0 thumb drive I was able to boot up a shell and get into /tmp/hdrescue and run:
tar xzpf /tmp/hdrescue/kernels/kernel_SMP.gz –exclude loader.conf -C /tmp/hdrescue/boot/
The above command I found from this thread: https://forum.pfsense.org/index.php?topic=46725.0
I'm now able to boot back into 2.2.2 but most of my packages are hosed in an inconsistent state. At least now I can grab some configs and kernel modules before doing a fresh 2.2.2 install.