Comment 6 for bug 1766945
Revision history for this message
| GERARDO GUIDARELLI (k+ulu42) wrote RE: [Bug 1766945] Re: (EFI on top of legacy install) choosing "replace" or "resize" options in partitioning may lead to an install failure | #6 |
I realized the issue on my end shortly after the bug report… yep accidentally booted the efi bootloader instead of the normal one.. tried installing again after booting the proper disc selection and worked … thanks for the feedback..
_______
From: <email address hidden> <email address hidden> on behalf of experimancer <email address hidden>
Sent: Friday, April 27, 2018 7:52:47 PM
To: <email address hidden>
Subject: [Bug 1766945] Re: (EFI on top of legacy install) choosing "replace" or "resize" options in partitioning may lead to an install failure
No, th fix #3 does not work, nor the GRUB or EFI boot loader setup fail,
Ubuntu 18.04 can not be installed with this, the bug is still there.
--
You received this bug notification because you are subscribed to a
duplicate bug report (1767260).
https:/
Title:
(EFI on top of legacy install) choosing "replace" or "resize" options
in partitioning may lead to an install failure
Status in partman-efi package in Ubuntu:
Confirmed
Status in ubiquity package in Ubuntu:
Confirmed
Bug description:
If I have existing data on disk built by a previous version of Ubuntu
(in BIOS (legacy) mode, or a previous Windows install, and no EFI
system partition on disk; the installer presents three choices:
- Replace $existing and reinstall. (if a previous Ubuntu install was found)
- Resize and install
- Erase disk and install.
The first two options will attempt to complete the installation in EFI
mode (as they should) but do not create an EFI system partition, which
is required as a place to put shim and grub on disk for booting. The
installer will then crash / fail as grub-install fails to find the ESP
when copying the bootloader.
The last option works correctly, it creates the ESP as it erases the
entire disks and proceeds with new partitioning.
To manage notifications about this bug go to:
https:/