Bug 214615 - Cannot create a new boot environment on GELI encrypted disks
Summary: Cannot create a new boot environment on GELI encrypted disks
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: Allan Jude
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-18 02:44 UTC by George V. Neville-Neil
Modified: 2020-07-11 15:23 UTC (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description George V. Neville-Neil freebsd_committer freebsd_triage 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 freebsd_triage 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 freebsd_triage 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 freebsd_triage 2020-07-11 15:23:38 UTC 
This works since FreeBSD 12.0