Router can't find kernel after update from 2.3.1_5 to 2.3.2
-
Today I applied the update and now the router will not boot. Connecting up to the terminal I get the messages below. Not sure, short of reinstalling, how to fix.
No /boot/kernel/kernel
FreeBSD/x86 boot
Default: 0:ad(0,a)/boot/kernel/kernel
boot: No /boot/kernel/kernelFreeBSD/x86 boot
Default: 0:ad(0,a)/boot/kernel/kernel
boot: 0No 0FreeBSD/x86 boot
Default: 0:ad(0,a)0
boot: No 0FreeBSD/x86 boot
Default: 0:ad(0,a)0
boot: -
I can't help you, but I will add that this happened to me too. The only way I could resolve it was by re-installing from a 2.3.2 image and restoring my backup which I took before the upgrade.
My hardware is an APU1D4. It was originally installed with 2.1.5 and has been incrementally upgraded all the way through 2.3.1_5, in case that also helps anyone figuring out what causes this.
Since this is my only router, I had to update quickly so unfortunately all of the evidence has been wiped. :(
-
This issue is many times linked to using a CFCard with the nano-install and running out of space. Which image are you using and how much storage do you have?
-
I am (and have been) running the "memstick USB serial console" version which installs to the internal disk. The internal disk on my APU was a Intel 525 mSATA (30G) which as far as I can tell has never gone more than 5% full on the filesystem. I've always used the GUI to do upgrades so I'm presuming it always picked "regular" install and not the nano version.
How much free space should I have? Looking at my filesystem now, it appears that only 20G or so got allocated this time:
[2.3.2-RELEASE][root@pfsense.localdomain]/root: df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/ufsid/5797cc85f80bc19c 19G 558M 17G 3% /
devfs 1.0K 1.0K 0B 100% /dev
/dev/md0 38M 180K 35M 0% /tmp
/dev/md1 58M 18M 35M 35% /var
devfs 1.0K 1.0K 0B 100% /var/dhcpd/dev -
Having the same problem.
But this device is using SSD drive. -
same problem here, hdd, 32bit