UEFI + Secureboot + guided full disk encryption -> new system fail to boot after install.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debian-installer (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
grub2-signed (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Fresh install on a physical system.
UEFI (in non legacy mode)
Secureboot ON
NetInstall via PXE
Select 'guided partitioning - LVM+encryption' as disk formatting stage.
Installation goes fine (except for the know problem with GRUB_ENABLE_
Rebooting into the newly installed system, it immediately drop to a GRUB prompt.
Upon investigation, it looks like crypto GRUB modules are not present, preventing GRUB to access the main disk and boot the system.
Install without encryption works fine.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: debian-installer (not installed)
ProcVersionSign
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Sun Nov 27 05:58:20 2016
EcryptfsInUse: Yes
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
MemoryUsage:
total used free shared buff/cache available
Mem: 16291844 197412 15683596 9636 410836 15807000
Swap: 16629244 0 16629244
ProcEnviron:
LANG=en_IE.UTF-8
TERM=linux
LANGUAGE=en_IE:en
PATH=(custom, no user)
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: debian-installer
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.70
dmi.board.name: N3700-ITX
dmi.board.vendor: ASRock
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
I have a similar issue when I upgraded to Ubuntu 19.10. I was thinking it was a Grub2 issue. /bugs.launchpad .net/ubuntu/ +source/ grub2/+ bug/1851031
https:/