Description of problem: Have recently got an SSD to speed up the system with the intention of dual booting. Windows7 has been successfully installed onto the SSD. But when I come to try installing the Mageia3 Beta 1 (as a clean install), in "custom disk partition" mode, the SSD reports it is all writeable, there should be at least two NTFS partitions viewable that Windows created. I've not had this problem before, and it possible down to a new motherboard which uses the new UEFI BIOS system. Before anyone suggests, the option over the Win8 "secure boot" has been disabled. Version-Release number of selected component (if applicable): Mageia3 beta 1 How reproducible: Attempt install on machine that uses UEFI and SSD.
Created attachment 3288 [details] Photo of installer Mageia3,Beta1
Could you provide the file /root/drakx/report.bug.gz as an attachment ? If you don't have the file, you can switch to console 2 (by pressing 'Ctrl-Alt-F2') during installation, put a floppy in floppy drive or plug a USB key/stick and type: 'bug' then press Enter. It will put report.bug on the floppy/key.
Keywords: (none) => NEEDINFO
Tried that, but after getting to console all that happened is that it took me to the command prompt to enter the localhost username and password, could not continue.
in the installer, really ? this is really strange you should have a busybox terminal
Arf I guess you use a live ? please try with a netinstall or classical dvd.
Not very sure this is related, but I've also seen something similar when performing a net install. The installer, instead of showing the 'sda' disk, it attempted to create partitions on my USB flash 'sdb' which contained the boot-nonfree.iso image. That puzzled me a few seconds, but I managed to finish the partition stage after switching to the 'sda' tab. From the attached picture, maybe the installer shows the wrong disk ('sdc').
CC: (none) => gruescubogdan
This version I tested first (the original bug filed) Mageia-3-beta1-LiveDVD-KDE4-x86_64-DVD As per your suggestion, I downloaded Mageia-3-beta1-x86_64-DVD version, and it produced the same results when it got to the partition page, that is, the SSD that I want to install Mageia to is claimed to be 100% free, despite there being Windows7 partitions on the drive. As a further point of interest, the install routine for Mageia-3-beta1-LiveDVD-KDE4-x86_64-DVD version is: 1) MUCH slower than the Mageia-3-beta1-x86_64-DVD installation setup. 2) Has a black background (I don't know it that's deliberate), but it does not look the same as the regular setup screens in Mageia-3-beta1-x86_64-DVD.
As a further test, I booted my machine into Mageia2, with the SSD drive connected. When I SU / run gparted, all the Windows partitions are correctly showing up as existing on the SSD, and the unallocated space (where I hope to install Mageia to) is also showing correctly. Looks to me like a problem with the installer not reading the partitions, not some hardware problem associated with the use of UEFI or the fact that the SSD is running off dedicated SATA600 channel on the motherboard.
Upon further tests I tried to partition the SSD using gparted in Mageia2 with Linux formatted partitions in an extended partition. When I tried to install Mageia3Beta1, the installation routing did not even see any of the Linux partitions on the SSD. So there appears to be something wrong with the partitioner software in the installation routine.
Keywords: NEEDINFO => (none)CC: (none) => pterjan, thierry.vignaud
Version: Cauldron => 3
@anyone: please review whether still current in present installer (5beta1): I cannot test ssd myself. If fixed, please close the bug as OLD; if not please update summary and whiteboard and detail the problem. Thanks
Summary: Mageia3,Beta1 installer fails to recognise partitions => Mageia3,Beta1 installer fails to recognise ssd partitionsWhiteboard: (none) => 3beta1
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD