Bug 248462 - bectl fails to activate temporally a boot environment
Summary: bectl fails to activate temporally a boot environment
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: CURRENT
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-04 07:45 UTC by larafercue@gmail.com
Modified: 2020-08-05 14:09 UTC (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description larafercue@gmail.com 2020-08-04 07:45:49 UTC
When I try to use the command `bectl activate -t default` if fails with the following output:


ZFS_IOC_NEXTBOOT failed: Unknown error: 1030
Did not successfully activate boot environment default
for next boot

Info about my system:

uname -a: FreeBSD sbox-home-lab.home 13.0-CURRENT FreeBSD 13.0-CURRENT #2 r363788: Mon Aug  3 14:59:45 UTC 2020     root@mbox.home-lab.home:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64

Any idea why is this happening?
Comment 1 Kyle Evans freebsd_committer 2020-08-04 11:25:42 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?
Comment 2 Toomas Soome freebsd_committer 2020-08-04 11:47:25 UTC
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.
Comment 3 commit-hook freebsd_committer 2020-08-05 14:09:17 UTC
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