partitioning requires /boot when it is not needed (UEFI)
Bug #1809713 reported by
Robert Collins
This bug report is a duplicate of:
Bug #1785332: 18.04.1 can't put /boot on SW RAID or LVM.
Edit
Remove
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| subiquity |
New
|
Undecided
|
Unassigned | ||
Bug Description
Setting up a new server on a UEFI system, correctly detected as such, with manual partitioning (because I wanted bcache and RAID5 and LVM).
The filesystem setup UI refused to advance until I created a dedicated partition for /boot, but per psusi here https:/
Somewhat similar to https:/
| description: | updated |
Revision history for this message
| Michael Hudson-Doyle (mwhudson) wrote | #1 |
To post a comment you must log in.
The issue here (which is perhaps overblown) is that TTBOMK grub can't write to lvm/raid so the recording of successful/failed boots doesn't work. This means we can't drop the user into grub if you install a bad kernel. There surely is a better way of handling this (like always having a grub delay if /boot isn't a regular partition) but that's where we are.