FreeBSD-12.1p13 beadm-1.3.2 Action: `beadm create 12.2-RELEASE-p13rp Created successfully beadm activate 12.2-RELEASE-p13rp` Expected behaviour: boot environment 12.2-RELEASE-p13rp is activated Observed behaviour: Activation hangs in an uninterruptible wait state (D+): `root 62914 0.0 0.0 11892 3208 4 I+ 09:00 0:00.01 /bin/sh -e /usr/local/sbin/beadm activate 12.2-RELEASE-p root 62968 0.0 0.0 11892 3204 4 I+ 09:00 0:00.00 /bin/sh -e /usr/local/sbin/beadm activate 12.2-RELEASE-p root 62973 0.0 0.0 12952 3996 4 D+ 09:00 0:00.25 zfs promote zroot/ROOT/12.2-RELEASE-p13rp`
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=713c35324e0f47fd679a27aafad96645a431e550 commit 713c35324e0f47fd679a27aafad96645a431e550 Author: John Hixson <jhixson@FreeBSD.org> AuthorDate: 2021-04-10 04:20:17 +0000 Commit: John Hixson <jhixson@FreeBSD.org> CommitDate: 2021-04-10 04:27:57 +0000 sysutils/ipfs-go: Add patch file and pkg-message PR: 253590 Reported by: <swills@FreeBSD.org> sysutils/ipfs-go/Makefile | 1 + .../files/patch-repo_fsrepo_migrations_migrations.go (new) | 11 +++++++++++ sysutils/ipfs-go/pkg-message (new) | 9 +++++++++ 3 files changed, 21 insertions(+)
> zfs promote zroot/ROOT/12.2-RELEASE-p13 The beadm(8) only issues zfs(8) and zpool(8) commands so the question here is why the *zfs promote* command hangs?
Is that still relevant or should we close that?
Any other info here?
(In reply to Slawomir Wojciech Wojtczak from comment #4) This happens on a different machine when upgrading from 12.3p2 to 13.0. If I select the boot environment from the boot screen then the system does not properly load the zfs libs and then hangs. I can try to find time to do another upgrade to 13 on that system and report.
It sounds like a boot loader issue to me - not a beadm(8) issue.
Can we close that one?
(In reply to commit-hook from comment #1) ^Triage: bugmeister note: this commit does not seem to have to do with this PR.
^Triage: I'm sorry that this PR did not get addressed in a timely fashion. By now, the version that it was created against is out of support. Please re-open if it is still a problem on a supported version.