binary upgrade problems (8.1-RELEASE-p5 -> 8.2-RELEASE-p3)
freebsd-questions at veggiechinese.net
Wed Oct 5 19:49:36 UTC 2011
I'm having some problems after doing a:
freebsd-update -r 8.2-RELEASE upgrade (I had also done an upgrade from
8.1-p5 to p6 without rebooting; not sure if that's part of the problem).
I did the update, merged the config files, ran freebsd-update install,
rebooted, and then ran freebsd-update install; despite /boot/kernel and
/boot/kernel.old both having a recently updated kernel, one which has
FreeBSD 8.2-RELEASE-p3 #0: Tue Sep 27 18:45:57 UTC 2011
if I run strings on it, uname and sysctl report
8.1-RELEASE-p5 FreeBSD 8.1-RELEASE-p5 #0: Tue Sep 27 16:49:00 UTC 2011
root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
As you can see, I'm just running the generic kernel.
The system boots and most services run, though ipfw isn't loading
because of the kernel version mismatch. Trying to either rollback or
re-upgrade using freebsd-update isn't working (the update list it builds
is wrong -- specifically, the fetch_make_patchlist() function isn't
working right and is missing the filenames, so it wants to delete all my
Any thoughts on the simplest way to get everything synced up and happy
again without doing a binary upgrade from sysinstall? kernel and
kernel.old are currently the same thing; I did try doing a nextboot -k
kernel.old, but that doesn't change anything.
If it matters, my first reboot after the upgrade was to single user
mode (to do a fsck) rather than standard - wondering if this prevented
some automatic thing that happens on the first boot after the binary
upgrade from running....
It has been rebooted normally several times since then, though.
I've tried moving /var/db/freebsd-update out of the way and re-creating
it, but that didn't help (I've since moved the old one back).
More information about the freebsd-questions