Bug 16236

Summary: Option Use full space doesn't add /boot/efi when absent
Product: Mageia Reporter: papoteur <yvesbrungard>
Component: InstallerAssignee: Thierry Vignaud <thierry.vignaud>
Status: RESOLVED OLD QA Contact:
Severity: major    
Priority: Normal CC: lohmaier+mageia, marja11, mhrambo3501
Version: 5Keywords: NEEDINFO
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: report.bug re: comment 3

Description papoteur 2015-06-28 11:05:12 CEST
Description of problem:
Virtualbox in UEFI mode, already partitioned, but without ESP.
At partitioning step, the option "Use full space" stops with the message "There is no /boot/efi partition".
We can think that if we ask the installer to deal with the partitioning, it can deal with creating the ESP.
It works fine with the option "Custom/automatic"
Version-Release number of selected component (if applicable):
DVD x86_64


Reproducible: 

Steps to Reproduce:
Comment 1 Christian Lohmaier 2015-06-29 12:54:27 CEST
confirmed problem on real hardware (Dell XPS 13)

using "use full disk" (i.e. erase existing partitions) also failed because it couldn't clear all partitions, most likely failed to erase the existing ESP or one of the dell partitions).

Manually erased the partitions and tried to use "automatic" â only creates /, swap and /home, no ESP (and thankfully refuses to continue with installation)

even used dd if=/dev/zero of=/dev/sda bs=10M count=20 from rescue system to completely clear any existing partitions before booting into the installer again.

Still automatic/use whole disk only created root, swap and home, no ESP.

So use manual, same effect for using the automatic in manual mode, no ESP created. (contrary to what the wiki page claims 

Had to manually create ESP (btw: no default mountpoint /boot/EFI offered in the dropdown).

PS: after boot had to manually add Mageia entry to the UEFI boot configuration in Dell's bios

CC: (none) => lohmaier+mageia

Samuel Verschelde 2015-06-29 17:38:44 CEST

Assignee: bugsquad => thierry.vignaud
Severity: normal => major

Comment 2 papoteur 2015-06-29 19:21:00 CEST
Hello,
Note that in my case, the UEFI was proposed in custom/automatic mode.
Papoteur
Comment 3 Thierry Vignaud 2016-06-17 14:47:04 CEST
If you see that error, please:
- plug an USB key
- go to tty2 (alt+ctrl+F2)
- type "run"
- attach (not paste) the "report.bug" file you'll found on the USB key to this bug report

Keywords: (none) => NEEDINFO

Thierry Vignaud 2016-06-18 15:20:45 CEST

Status: NEW => ASSIGNED

Comment 4 Thierry Vignaud 2016-06-18 16:18:30 CEST
Works for me as of current mga (drakx v17.39)
Comment 5 Mike Rambo 2016-08-29 18:30:29 CEST
Have twice attempted UEFI (bare hardware) installation on random extra hard drives that we have laying around. One hdd was windows of unknown version (but probably 7) and the other had had a pfSense test installation on it. In both cases I selected erase and auto configure. In both cases the installer (using boot-nonfree.iso from a usb key) then told me I needed /boot/EFI. Says drakx is 17.55. Attempting the instructions in comment 3 results in file not found. 'run' doesn't seem to be there. I manually created the /boot/EFI partition and have the installation proceeding because I'm trying to test for another bug but I can repeat this if it will help as we should have a number of hard drives of this description I can substitute.

CC: (none) => mrambo

Comment 6 Mike Rambo 2016-08-29 21:29:43 CEST
Figured out that it is 'bug' rather than 'run'. Attaching 16236-report.bug.
Comment 7 Mike Rambo 2016-08-29 21:31:37 CEST
Created attachment 8378 [details]
report.bug re: comment 3
Comment 8 Marja Van Waes 2018-04-28 22:24:38 CEST
I assume this was fixed before Mageia 6 release, because last comment in this report dates from well over 1½ years ago, so from before Mageia 5.1.

Note that installer bugs should always be set to Version: Cauldron, because we cannot fix an already released iso.

To indicate that Mageia 5 stable was the last version in which an installer bug was reproduced, you could have put (MGA5) on the whiteboard ;-)

Anyway, closing as OLD

If this bug was still valid with Mageia 6, then please reopen it, set Version: to Cauldron and put "(MGA6)" on the whiteboard

Resolution: (none) => OLD
CC: (none) => marja11
Status: ASSIGNED => RESOLVED