Bug 15605

Description of problem:
(New bug as Len Lawrence thought this was different from recent somewhat-related issues)

Laptop with 2x SSD 256Gb drives.  (I've split the raid pending Mageia raid fixes).
x86_64 RC5 install still halts after choosing 'use available space' install option:
An error occurred
You must have an ESP Fat32 partition mounted in /boot/EFI

By choosing 'use available space' there has been no opportunity for manually choosing the mount point for the existing EFI partition, so the installer needs to find it and make a mount point for it, rather than complaining this hasn't been done. (with custom install, this isn't an issue - I just make the mount point manually).  I went back a step, then saw it had created sda4 and 7 of 50 and 150Gb, proposing / and /home as mount points for these.  Nothing said this time about EFI, but it still hasn't given the EFI partition a mount point that I can see.  Allowing install to run and see what happens...

Well, the install froze shortly after, almost nothing installed:
urpmi error: unable to install package /tmp/image/media/core/hostname-3.15-5.mga5.x86_64.rpm
urpmi error: unable to install package /tmp/image/media/core/iproute2-3.19.0-1.mga5.x86_64.rpm
urpmi error: Can't open file [/tmp/image/media/core/lib64intl8-0.19.4-1.mga5.x86_64.rpm] [No such file or directory]

I see the 'use available space' install also did odd stuff in partitioning; I had existing sda1 of 407Mb, sda2 EFI of 300Mb, sda3 of 128 Mb (for MS-Win) and there was an sda6 swap partition of 2.6Gb.  I'd deleted sda4 and sda5 M4 and M5 partitions and left empty space.  Installer created sda4 of 50Gb, a second swap in new sda5 of 4Gb, and sda7 of 180Gb which I saw on earlier run was for /home.  The partition numbering order is now wrong; the installer hasn't fixed this, and the 2nd swap was unnecessary.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce: