Bug 19185

Summary:	unable to find free space when raid GPT drives present
Product:	Mageia	Reporter:	jeff deifik <jeff>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, thierry.vignaud
Version:	5	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description jeff deifik 2016-08-12 02:05:51 CEST

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

Comment 1 Thierry Vignaud 2016-08-13 04:47:39 CEST

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) => NEEDINFO
CC: (none) => thierry.vignaud

Comment 2 Marja Van Waes 2016-08-13 21:09:30 CEST

@ 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

Comment 3 Thierry Vignaud 2016-08-13 22:06:59 CEST

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

Comment 4 Marja Van Waes 2016-08-14 11:57:28 CEST

(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)

Comment 5 jeff deifik 2016-08-15 02:30:10 CEST

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.

Comment 6 Thierry Vignaud 2016-08-15 08:32:20 CEST

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) => OLD
Status: NEW => RESOLVED