testcase = MGA5 install from classic DVD x64 in EFI/USB : windows 7 installed in EFI mode Disk partitioning before install : sda1 = fat32 100Mio, flags boot, esp which is EFI partition; sda2 = unknown fs type, label microsoft reserved, 128 Mio, label msftres; sda3 = ntfs, 25Gio, ntfsdata ; rest of the disk blank At partitioning windows, selected "use free space" option After rebooting as asked, partition table was as below : sda1 labelled /media/win_ sda3 labelled /media/win_c 4 new partitions : sda4 300Mio ext4 sda5 15 Gio no fstype (greyed out) sda6 3 Gio swap sda7 31 Gio ext4 /home So : - windows boot/EFI was not recognized - sda4 was created seemingly to be /boot/EFI but with ext4 fs - sda5 has no fstype, created to be / I guess. Looking more closely, there is no unallocated space between sda4 and sda5 which probably explains sda5 is unusable. The installer can't go on as it complains there is no root partition. Reproducible: Steps to Reproduce:
This is Mageia5 RC 2nd build on classical iso
CC: (none) => olchal
No, unallocated space is unrelated (partitions are aligned on 1Mb boundary) Please try again up to the point you see the error dialog, then: - attach a USB key - go to tty2 (alt+ctrl+F2) - run the "bug" command. - attach (not paste) the report.bug file you'll find on this USB key here.
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaudSummary: M5RC classic DVD fails to partition disk in EFI mod with windows 7 (use free space option) => M5RC classic DVD fails to partition disk in EFI mod with windows 7 (use free space option) b/c partitionner asked to reboot
Created attachment 6012 [details] bug report after partitioning error As I had moved on other tests, I retraced that one : Windows 7 installed in uefi mode and rest of the hard disk blank. Option "Use free space" in disk partition screen which asked me to reboot. Which I did. I could then see that 3 new partitions had been added this time, all greyed out. As I had no available USB key, I didn't run the bug command, just switched off. After switching back on, I could not even get to partition step as I got a message saying that the partition table was corrupted, proposing to erase bad partitions. + "error is /proc/partitions does not agree with drakx 7 |= 0:" Ran the bug command (see attachment).
From a live disk, running gparted, in fact this is the same partition scheme than in my first try : 4 new partitions as in Description, but this time the 3 last ones are described with unknown file system.
Had same bug using Mag5 Gnome LiveDVD on a blank harddrive (another one) with only a GPT table. I asked to use free space on disk, on reboot, 4 partitions were greyed out and unusable, gparted reporting no filesystem on each partition. This hard drive was previously an MBR harddrive with Windows on it.
Can you check a network install with latest stage2? eg: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/install/stage2/ has yesterday's stage2. Does my fix prevent this useless reboot when partitionning?
Hi Thierry. Did as you asked : Network install pointing to http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64 My installation : 1st sata HD (sda) in GPT with 4 linux distributions and 220 Mo blank 2nd sata HD (sdb) in GPT with windows7 and 120 Mo blank Chose to install on sdb (after windows), option "use free space" Partitioned sda instead of sdb adding 4 partitions in free space 1 fat32 300Mo 2 ext 4 (49 Mo and 170 Mo) 1 swap (4Mo) and reformated sda3 (which is a swap file) Proposed then to choose media sources (core, non free, tainted and so on). So no reboot this time. I aborted then. With Gparted, could see that partitions had file systems set, no grey partition. Unplugged sda Retraced same procedure but only with sdb plugged. At partition step, use free space. The partition tool again set 4 new partitions using same scheme as on sda. This partitions seem usable. No reboot, but due to late time, I aborted. Conclusion : latest stage 2 does not need reboot, seem to write usable partitions but : - do not use the chosen hard disk - still write a new fat32 partition for /boot/EFI though there is already one. Tell me if you want me to go on and make a full installation (in 20 hours time from now).
I have similar problem (as described in comments 1 to 5, I didn't try the latest stage 2 yet) to install MGA5RC Classical DVD64 in dual boot with Windows 10. Some comments and screenshots here: https://wiki.mageia.org/en/User:Lebarhon#GPT_disk_with_Windows_already_installed
CC: (none) => lebarhon
CC: (none) => eeeemail
Still valid with last build (March 15 - 2015) Partitioning option :Using the free space on a Microsoft Windows partition (about 100GB free space) The partition created are: - a 128 MB not formatted - a 300 MB FAT32 - a 4,3 GB and a 8,3 GB ext 4 - a 945 MB swap Existing ESP not detected.
Testing partition tool with latest build in EFI mode along Windows7 - with classical iso (Third Build Dated 16 March 2015 - Mageia-5-RC-x86_64-DVD) ------------------ Whatever option taken (use free space, use free space in a microsoft windows partition, custom + automatic partitioning) : the partitioning tool sets 4 partitions, with proper file system and correctly mounted. It does not ask for a reboot and installation goes to its end. Windows7 boot partition is still ignored and a new boot partition is created each time. - with live iso (Live ISOs second build 16 March 2015- Mageia-5-RC-LiveDVD- ------------- GNOME-x86_64-DVD) Only tried custom + automatic partitioning with /boot/EFI set manually on windows boot partition. Installation wizard asks for a reboot after partitioning. On reboot : /boot/EFI is no more set 3 new partitions created = sda4 38Go ext4 no mountpoint sda5 4Go no fs no mountpoint sda6 76Go nofs no mountpoint Workaround : using custom partition/expert mode, I could set the file systems and mount points. Installation wizard then proceeds to its end.
Olivier, did you try to start Windows after Mageia Installation? At my place, Windows doesn't start, an error message says the kernel isn't found.
(In reply to André DESMOTTES from comment #11) > Olivier, did you try to start Windows after Mageia Installation? > At my place, Windows doesn't start, an error message says the kernel isn't > found. Hi André, No, I could not in any case boot Windows7 from Mageia5 grub menu. ( /usr/sbin/grub2-probe : impossible de trouver un périphérique GRUB pour /Microsoft/Boot/bootmgfw.efi) I have to use boot override from my motherboard to be able to boot windows. I remember having seen you must edit /boot/grub2/grub.cfg to add a windows entry manually but I did not try. I think this would be another bug as this affects grub in EFI mode. It is different from the partitioning tool bug.
Let's not mix different issues in the same bug report. Original bug was about need to reboot when partitionning. This has been fixed. Existing ESP not detected has just been fixed in git (bug #15366)
So let's close this one. Please try latest netinstall once it lands on your favorite mirror. Just check install/stage2/VERSION contains 16.71 eg: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/install/stage2/VERSION for http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/ But you'll have to wait at least one hour before distrib-coffee had synced 16.71
Status: NEW => RESOLVEDResolution: (none) => FIXED
Then open new bug reports for any UEFI issues