Description of problem: I have a system running mageia 5 with a boot disk and six 4tb drives in a raid 5 array. I replaced the boot disk, but mageia-5 was unable to detect any free space to install os. I removed the six raid drives, and mageia was able to find free space to install os. I suspect the odd gpt partitioning on the 4tb drives confused the installer to the point of being unable to detect the boot drive. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. install mageia on small boot disk 2. Install raid-5 array on 4tb drives 3. replace boot disk, and mageia installer can't find any free space
Mga5 is frozen, it won't be updated. Could you try future Mga6 installer? See http://blog.mageia.org/en/2016/07/01/the-next-step-towards-mageia-6-is-here-sta1-has-been-released/ Also when you see such a bug, you can: - plug a USB key - go to tty2 (alt+ctrl+F2) - run the "bug" command - attach (not paste) the report.bug file found on the USB key to the bug report
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaud
@ Thierry Should the "bug" command already work when there's no / partition mounted? If so, then what we added to the triage guide is wrong https://wiki.mageia.org/en/Triage_guide#Traditional_installer > Please note! > before partitions are mounted for installation, the content is instead in > /tmp/ddebug.log > So if install does not get past partitioning, this is the file to get. User > must manually mount a media and copy that file over. (This bug is about installer finding no free space, so it can't have mounted a partition)
CC: (none) => marja11
That's 2 different things: - where installer kept its logs - an additional "bug" command that concatenate all of them & copy them on a USB key
(In reply to Thierry Vignaud from comment #3) > That's 2 different things: > - where installer kept its logs > - an additional "bug" command that concatenate all of them & copy them on a > USB key Thx, Thierry. I commented that Note out from the triage guide (without removing it, because stormi needed it once when the bug command didn't work)
I tried mageia 6 sta 1. It was able to find the existing mageia 5 and asked if I wanted to upgrade or install. I picked install, and custom disk partitioning, and it was able to see the correct partitioning of /dev/sda . I exited the install at that point. It looks like it should work for mageia 6. I didn't feel like going through the install of beta software on my computer, as I use it for production use.
OK then I'll close this one as OLD as mga5 installer is frozen and won't be updated. I think this bug has been fixed by one of my GPT improvements
Resolution: (none) => OLDStatus: NEW => RESOLVED