Re: FreeBSD 12.4: EFI: geli + UFS won't boot - fix available

From: David E. Cross <>
Date: Thu, 15 Dec 2022 21:46:10 UTC
On 12/14/22 20:10, David Cross wrote:
> The drafts never made it out, doesn’t seem there is a distinction there
>> On Dec 14, 2022, at 3:08 PM, Andreas Kempe <> wrote:
>> On Wed, Dec 14, 2022 at 02:51:51PM -0500, David Cross wrote:
>>>>> On Dec 14, 2022, at 12:11 PM, Andreas Kempe <> wrote:
>>>> On Sun, Dec 11, 2022 at 08:29:18PM -0700, Warner Losh wrote:
>>>>>> On Sun, Dec 11, 2022, 8:10 PM David Cross <> wrote:
>>>>>> One would hope. This is now the third time this has been reported. At
>>>>>> least. I even personally wrote a draft en for it (for 13.1). And 2 other
>>>>>> ENs yet to see a release, also with bugs and patches and fixes committed to
>>>>>> -CURRENT
>>>>> EN s are hard to do as a developer. We do very few of them. Since they are
>>>>> hard, I just don't bother. That needs to change...
>>>> If ENs are difficult to do, would it at least be possible to add a
>>>> notice under Late-Breaking News with a warning? To me, having a system
>>>> that won't boot is a quite nasty surprise.
>>> I wrote  draft ENs for these already. Give me a few and I’ll send them on again
>> Thank you! I misinterpreted you as your drafts having been rejected.
>> Best regards,
>> Andreas Kempe

Sorry for the previous top-posting.  I will get better.

Anyway, here are the 3 draft ENs I wrote earlier, submitted 8/30/2022.  
All 3 were actually reported by other people (I just happened to hit 
them independently), all 3 had patches submitted and were in GIT in 

While all 3 affect 'nonstandard' options (geli root disk isn't standard, 
compiling with other options isn't standard), all of these things are 
supposed to work, and the patches involved are trivial.  The geli one 
itself is such a HUGE problem it has to be addressed IMO.  When I wrote 
these drafts 12.4 wasn't a thing, so they need to be updated.  Also 
there are sections that need to be corrected also, I was trying to do 
the heavy lift of describing the problem, workarounds, impact, etc.  
Things like the specific patches need to come from git after merges/etc.