Bug 214615

Summary:	Cannot create a new boot environment on GELI encrypted disks
Product:	Base System	Reporter:	George V. Neville-Neil <gnn>
Component:	kern	Assignee:	Allan Jude <allanjude>
Status:	Closed FIXED
Severity:	Affects Only Me	CC:	allanjude, grahamperrin, mshirk, tm
Priority:	---
Version:	CURRENT
Hardware:	Any
OS:	Any

Description George V. Neville-Neil freebsd_committer

2016-11-18 02:44:24 UTC

I have a sytem with ZFS on top of GELI on a single disk.  When I use beadm to create and activate a new boot environment I see this:

% sudo beadm create -e default upgrade
Created successfully

% sudo beadm activate upgrade
cp: /tmp/BE-upgrade.pOdFvGjn/boot/zfs/zpool.cache: No such file or directory

% beadm list
BE      Active Mountpoint                Space Created
default NR     /                          4.2G 2016-11-17 17:55
upgrade -      /tmp/BE-upgrade.pOdFvGjn 184.0K 2016-11-18 02:43

%

Comment 1 Allan Jude freebsd_committer

2016-11-18 02:48:01 UTC

Boot Environments do not work with GELI when you boot UEFI (yet). Eric McCorkle is working on GELI boot support for UEFI

Comment 2 Allan Jude freebsd_committer

2018-06-17 03:18:41 UTC

Ian is working on broadening my GELIBoot work to all platforms, including amd64/UEFI and arm64

Comment 3 Allan Jude freebsd_committer

2020-07-11 15:23:38 UTC

This works since FreeBSD 12.0