Bug 242848 - Failed install with large (1GB) EFI partition
Summary: Failed install with large (1GB) EFI partition
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: 12.0-RELEASE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-24 02:06 UTC by Matthew Woehlke
Modified: 2019-12-27 17:57 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Woehlke 2019-12-24 02:06:41 UTC
Attempting to install FreeBSD with a 1GB EFI partition results in a system that cannot boot.

I created the following partitions:
  size type mount label
   1GB efi  (n/a) boot
  20GB swap (n/a) swap
  93GB ufs  /     root

Installation appears to succeed, however the machine is incapable of booting.

(I was only able to get the system booting by using partly guided partitioning and accepting the 200MB boot partition that wanted to create. https://wiki.freebsd.org/UEFI suggests there may be a limit to the maximum size the EFI partition may have?)
Comment 1 Ed Maste freebsd_committer 2019-12-26 20:06:53 UTC
What specifically happens when you try to boot the system with a 1G EFI partition?
Comment 2 Matthew Woehlke 2019-12-27 16:29:15 UTC
> What specifically happens when you try to boot the system with a 1G EFI partition?

"Nothing"... I either get bounced back into BIOS setup or the BIOS boot menu, or I get a black screen and have to reboot. I'd guess the EFI partition is not readable by the BIOS.
Comment 3 Ed Maste freebsd_committer 2019-12-27 17:33:04 UTC
Are you able to boot other operating systems on that hardware with a 1G EFI partition (created by the other OS's installer)? I wonder if the UEFI implementation just cannot handle large partitions?
Comment 4 Matthew Woehlke 2019-12-27 17:57:00 UTC
That could be, though IIUC, USB sticks are a single EFI partition that is well over 1GB. But USB might be handled differently.

Is there any easy way to test without reformatting the OS drive? (I have the system in production now, so I probably can't do disruptive tests, and I don't have a spare HDD/SSD for testing.)

FWIW, it's a Gigabyte motherboard. I can look up the exact model, but my guess would be their BIOS is sufficiently homogeneous that any recent Gigabyte board will act the same in this respect.