freebsd-update revert woes

I tried to upgrade 14.0p11 to 14.1-release but I got a failure and so I tied to revert and ended up losing a whole load of shared libraries - it looks like it tried to go back to a 13 version.
It seems safest to overwrite the mess that's there (I'm still scared to reboot) with an installation, having taken a copy of the customisations (and perhaps the pkg state?).

Is there a preferred way to do this?

I'm booting off a UFS volume on SSD, but my data is on a RAIDZ set of SATA disks, so I'm not in a position to use a ZFS revert.
It might be that I should look at having a single-drive ZFS boot volume so I can use the boot env stuff in future.
 
I'm wondering what kind of failure you got that prompted you to revert? After the first freebsd-update install only the kernel got updated. That's usually easy to revert without having to use freebsd-update rollback. Even on UFS that's an easy fix.
 
Just fire up the 14.1 update again and (this time) post the error message you get.
I'm a bit concerned because the system got into a state where pkg, ping etc were broken by missing shared libraries. I had done the upgrade from 14.0p7 to 14.0p11 ok, but there seemed to be a problem when following the instructions here: https://www.freebsd.org/releases/14.1R/installation/#upgrade-binary

It seemed that the upgrade was a no-op - I followed the process and seemed to remain on 14.0p11.

I noticed that normally I would have done:
freebsd-update -r 14.1-RELEASE upgrade
(ie with upgrade after the -r) and when I tried that, it seemed that more was happening but there was a checksum fail part way through.
At that point I did the rollback and everything broke.

I do have another server online (currently on p7 I believe - I'm away from them at present) and I'm currently thinking about options that don't involve a reboot since the system got into a poor state and I suspect it still is, hence my interest in resetting to a known good starting point. I recovered pkg with pkg bootstrap -f and ping by stealing some missing content (libcap* from memory) from the other server.
 
freebsd-update -r 14.1-RELEASE upgrade
(ie with upgrade after the -r) and when I tried that, it seemed that more was happening but there was a checksum fail part way through.
At that point I did the rollback and everything broke.
Common misconception here. The freebsd-update -r <version> upgrade stage only prepares everything, it does NOT make any changes to the current system. The actual upgrade process that changes files is with freebsd-update install (twice for minor upgrade, three times with major version upgrades). That's probably where you went wrong. Nothing was actually changed and you then did a rollback of the previous upgrade/update.

Lots of people seem to think the upgrade stage makes changes, probably due to the various merge requests. But this is just a preperation for the actual upgrade.
 
https://www.freebsd.org/releases/14.1R/installation/#upgrade-binary

… normally I would have done:
freebsd-update -r 14.1-RELEASE upgrade
(ie with upgrade after the -r) and when I tried that, it seemed that more was happening but there was a checksum fail part way through.

If you have not already done so, use single mode and force check – but do not repair – UFS volumes.

What's reported?

Also, please:

uname -p

At that point I did the rollback and everything broke. …

In this situation, the neatest way to gain a working installation of (patched) 14.1-RELEASE-p5 may be:
  1. official packages (following advice for pkgbase)
  2. clean up 13.x debris.
 
… ping by stealing some missing content (libcap* from memory) from the other server.

Code:
root@fourteen-pkgbase:~ # uname -KU
1401000 1401000
root@fourteen-pkgbase:~ # which ping
/sbin/ping
root@fourteen-pkgbase:~ # pkg which /sbin/ping
/sbin/ping was installed by package FreeBSD-runtime-14.1p5
root@fourteen-pkgbase:~ #

FreeBSD-runtime-14.1p5 (a vital package, IIRC) provides thirty libraries, seven of which are libcap_*

For your 14.0p11 case, the package would be FreeBSD-runtime-14.0p11.pkg.
 
Update: I finally got brave enough to reboot and sure enough it was in a bad way and the revert had taken me to 13.2.
I've got it back after a couple of upgrades to 14.0p11 but its failing to upgrade to 14.1, I'll start another thread. I do at least have a working system again.
 
Back
Top