Summary: | bectl fails to activate temporally a boot environment | ||
---|---|---|---|
Product: | Base System | Reporter: | larafercue <larafercue> |
Component: | bin | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | Closed FIXED | ||
Severity: | Affects Some People | CC: | allanjude, kevans, lwhsu, tsoome |
Priority: | --- | ||
Version: | CURRENT | ||
Hardware: | amd64 | ||
OS: | Any |
Description
larafercue@gmail.com
2020-08-04 07:45:49 UTC
Adding a couple more folks that might immediately recognize this, due to other work in the error. I'm assuming this is not a UEFI boot? I think that would have failed earlier. And this is an unmodified -CURRENT, or -CURRENT with new OpenZFS from the CFT? Have you used bectl avtivate -t before? can you run: zpool status zroot to get disk device name, then: hexdump -C /dev/diskname | less, search 2000 and paste 5-10 lines from it. Then try zfsbootcfg "", does it get errors? if not, try bectl activate -t again. A commit references this bug: Author: tsoome Date: Wed Aug 5 14:08:45 UTC 2020 New revision: 363910 URL: https://svnweb.freebsd.org/changeset/base/363910 Log: zfs_keys_nextboot array is missing ZPOOL_CONFIG_POOL_GUID and ZPOOL_CONFIG_GUID As we do check the incomint nvlist, we either need to list all possible keys or use wildcard. PR: 248462 Reported by: larafercue@gmail.com Sponsored by: Netflix, Klara Inc. Changes: head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c |