The problem was resolved by manually activating the BE created by the update process.
OP --->
I am by now enured to the difficulties caused by upgrading FreeBSd. However, this latest experience completely baffles me. I tried to upgrade a bare metal host from 13.1 to 13.2 and the console scroll-back shows this:
After logging on following the reboot there is no indication whatsoever that an update was applied. The
So what has happened?
OP --->
I am by now enured to the difficulties caused by upgrading FreeBSd. However, this latest experience completely baffles me. I tried to upgrade a bare metal host from 13.1 to 13.2 and the console scroll-back shows this:
Code:
[root@vhost05 ~ (master)]# freebsd-update upgrade -r 13.2-RELEASE
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 13.1-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Fetching 2 metadata patches.. done.
Applying metadata patches... done.
Fetching 1 metadata files... done.
Inspecting system... done.
The following components of FreeBSD seem to be installed:
kernel/generic kernel/generic-dbg world/base world/lib32
The following components of FreeBSD do not seem to be installed:
world/base-dbg world/lib32-dbg
Does this look reasonable (y/n)? y
Fetching metadata signature for 13.2-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Fetching 1 metadata patches. done.
Applying metadata patches... done.
Fetching 1 metadata files... done.
Inspecting system... done.
Fetching files from 13.1-RELEASE for merging... done.
Preparing to download files... done.
Fetching 5592 patches.....10....20....30....40....50....60....70 . . .
[/code
[SPOILER="abridged upgrade dialogue"]
. . .
Applying patches... done.
Fetching 587 files... ....10....20....30....40....50....60....70....80....90....100...
. . .
Attempting to automatically merge changes in files... done.
The following file could not be merged automatically: /etc/ssh/moduli
Press Enter to edit this file in vi and resolve the conflicts
manually...
. . .
The following changes, which occurred between FreeBSD 13.1-RELEASE and
FreeBSD 13.2-RELEASE have been merged into /etc/motd.template:
--- current version
+++ new version
@@ -3,11 +3,11 @@
Release Notes, Errata: https://www.FreeBSD.org/releases/
Security Advisories: https://www.FreeBSD.org/security/
FreeBSD Handbook: https://www.FreeBSD.org/handbook/
FreeBSD FAQ: https://www.FreeBSD.org/faq/
-Questions List: https://lists.FreeBSD.org/mailman/listinfo/freebsd-questions/
+Questions List: https://www.FreeBSD.org/lists/questions/
FreeBSD Forums: https://forums.FreeBSD.org/
. . .
Does this look reasonable (y/n)? y
The following files will be removed as part of updating to
13.2-RELEASE-p9:
/boot/kernel/iwlwifi-Qu-b0-hr-b0-68.ucode.ko
/boot/kernel/iwlwifi-Qu-b0-jf-b0-68.ucode.ko
/boot/kernel/iwlwifi-Qu-c0-hr-b0-68.ucode.ko
. . .
/usr/tests/usr.bin/timeout
The following files will be added as part of updating to
13.2-RELEASE-p9:
/bin/nproc
/bin/timeout
/boot/kernel/bcm5974.ko
/boot/kernel/dpdk_lpm4.ko
. . .
/var/db/mtree
/var/run/bhyve
The following files will be updated as part of updating to
13.2-RELEASE-p9:
/bin/[
/bin/cat
/bin/chflags
. . .
/var/db/etcupdate/log
/var/db/mergemaster.mtree
/var/db/services.db
To install the downloaded upgrades, run "/usr/sbin/freebsd-update install".
[root@vhost05 ~ (master)]# /usr/sbin/freebsd-update install
src component not installed, skipped
Creating snapshot of existing boot environment... done.
Installing updates...
Kernel updates have been installed. Please reboot and run
"/usr/sbin/freebsd-update install" again to finish installing updates.
[root@vhost05 ~ (master)]# shutdown -r now
Shutdown NOW!
shutdown: [pid 36525]
*** FINAL System shutdown message from root@vhost05.hamilton.harte-lyne.ca ***
System going down IMMEDIATELY
System shutdown time has arrived
[root@vhost05 ~ (master)]# Connection to vhost05.internal closed by remote host.
Connection to vhost05.internal closed.
[root@vhost01 ~ (master)]# sshta vhost05.internal
!!Warning!! - Any deliberate attempt to access this resource without
legitimate authorization is a criminal offence
(R.S.C. 1985, c. C-46 - Section 342.1).
no sessions
. . .
[root@vhost05 ~ (master)]# freebsd-version
13.1-RELEASE-p2
[root@vhost05 ~ (master)]# freebsd-update install
src component not installed, skipped
No updates are available to install.
Run '/usr/sbin/freebsd-update fetch' first.
[root@vhost05 ~ (master)]# beadm list
BE Active Mountpoint Space Created
12.3-RELEASE-p1 - - 2.5M 2022-01-12 13:08
13.0-RELEASE-p6 - - 113.0M 2022-01-13 08:28
13.0-RELEASE-p6-2022-01-13-pkgs - - 2.3G 2022-09-20 22:09
13.1-RELEASE-p2 NR / 809.0G 2022-09-23 14:31
13.1-RELEASE-p2_2024-01-09_174142 - - 494.0G 2024-01-09 17:41
[root@vhost05 ~ (master)]# history | tail -100
. . .
4804 2022-09-23 12:52:59: for HDD in {0..3}; do gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada${HDD}; done;
4805 2022-09-23 13:28:42: more $(command -v freebsd-update)
4806 2022-09-23 14:30:08: beadm list
4807 2022-09-23 14:30:33: uname -a
4808 2022-09-23 14:30:59: pkg upgrade
4809 2024-01-09 17:49:45: freebsd-version
4810 2024-01-09 17:50:02: freebsd-update install
4811 2024-01-09 17:59:10: ht
4812 2024-01-09 17:59:27: beadm list
4813 2024-01-09 18:01:48: ht
4814 2024-01-09 18:03:30: beadm list
4815 2024-01-09 18:05:59: beadm activate 13.1-RELEASE-p2_2024-01-09_174142
4816 2024-01-09 18:06:51: freebsd-version
4817 2024-01-09 18:07:01: freebsd-update install
4818 2024-01-09 18:07:24: beadm activate 13.1-RELEASE-p2
4819 2024-01-09 18:09:04: beadm activate 13.1-RELEASE-p2_2024-01-09_174142
4820 2024-01-09 18:09:39: beadm activate 13.1-RELEASE-p2
4821 2024-01-09 18:09:45: ioget
4822 2024-01-10 08:44:51: exit
4823 2024-01-10 09:21:01: beadm list
4824 2024-01-10 09:22:08: history | tail -100
[root@vhost05 ~ (master)]#After logging on following the reboot there is no indication whatsoever that an update was applied. The
freebsd-update install finds nothing to install. The history file only records events following 2024-01-09 17:49:45:. The immediately preceding history entries are from 2022. None of the cli commands entered relating to the update remain. Note that a beadm snapshot taken at 2024-01-09 17:41 exists but is not activated and does not run following a reboot.So what has happened?
Last edited:
