Bug 10968

Summary: No bootloader option if using 2nd HDD
Product: Mageia Reporter: martyn vidler <martynvidler>
Component: InstallerAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: davidwhodgins, eeeemail, martynvidler, thierry.vignaud
Version: CauldronKeywords: NEEDINFO
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard: 4alpha1
Source RPM: drakxtools CVE:
Status comment:

Description martyn vidler 2013-08-10 10:01:29 CEST
Description of problem:

Grub bootloader 


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


How reproducible:

Always


Steps to Reproduce:
1.Install mageia 
2.Select installation to HDD example sdc.
3.There is no option for a bootloader to be installed
(If sda drive is selected the bootloader options is offered)

When booted into new install Use MCC/Boot set up boot system, 
It reports "No bootloader found creating a new configuration", Select ok it takes you back to main screen

If I try grub-install /dev/sda it installs grub legacy but I only get grub prompt


Reproducible: 

Steps to Reproduce:
martyn vidler 2013-08-10 10:13:56 CEST

Whiteboard: (none) => 4alpha1

martyn vidler 2013-08-10 10:14:15 CEST

CC: (none) => martynvidler

Comment 1 Manuel Hiebel 2013-08-10 10:46:21 CEST
"3.There is no option for a bootloader to be installed
(If sda drive is selected the bootloader options is offered)

When booted into new install Use MCC/Boot set up boot system,"

so one was installed as you can boot ?

"It reports "No bootloader found creating a new configuration", Select ok it takes you back to main screen"

was that with grub2 install ?

"If I try grub-install /dev/sda it installs grub legacy but I only get grub prompt"
what for grub prompt ?

also can you _attach_ your /root/drakx/report.bug
martyn vidler 2013-08-10 10:49:11 CEST

CC: (none) => eeeemail

martyn vidler 2013-08-10 10:49:38 CEST

CC: (none) => davidwhodgins

Comment 2 martyn vidler 2013-08-10 11:18:11 CEST
I have my own grub2 installed on sda and a boot partition sda1 which I edit grub.cfg as needed.

To boot my new install I edited grub prompt or add it to my grub.cfg

When I install to sdax drive the bootloader option is present and I can install it (over write  my own grub) and use it 

There is no /root/drakx/report.bug as I used a live dvd version
Comment 3 Manuel Hiebel 2013-08-11 00:40:04 CEST
then the MCC/Boot issue is "normal" and known.

CC: (none) => thierry.vignaud
Source RPM: (none) => drakxtools

Comment 4 martyn vidler 2013-08-11 07:21:05 CEST
Ok so then we have the no bootloader option when installing on to 2nd/3rd hdd
Comment 5 Dave Hodgins 2013-08-11 08:09:59 CEST
Which iso are you using to install?
Comment 6 martyn vidler 2013-08-11 08:17:29 CEST
It would of been Mageia-4-alpha1-LiveCD-GNOME-en-i586-CD.iso and I tried Mageia-4-alpha1-LiveDVD-GNOME-i586-DVD.iso, As I said if I choose to install to sdaX I get the bootloader option.
Comment 7 Dave Hodgins 2013-08-11 09:50:12 CEST
I couldn't get gnome to start in live mode (gnome shell segfault). It's truly
alpha level quality at this point, so I installed using the kde x86-64 livedvd
which shouldn't matter, as the installer parts are common.

I installed with just /, on sdb5. When it got to the bootloader configuration,
I was able to use the dropdown box to select sdb5 to install the grub to,
instead of sda. (I use the gag boot manager on sda). Had no problems.

Are you not seeing the bootloader configuration dialog at all?
Comment 8 martyn vidler 2013-08-11 09:59:22 CEST
No it gets to the user part then finishes. I will run again, Report back I,m sure it exits install screen and I end up at Desktop?
Comment 9 Dick Gevers 2014-12-01 11:27:14 CET
In #c8 more info was promised. Not seen since 15 months.

However pre-5 installers will not be fixed.

Could you state how this holds against 5beta1 or higher and change the whiteboard accordingly? Thanks.
Otherwise we should close as OLD, I regret to tell.

Keywords: (none) => NEEDINFO

Comment 10 Thierry Vignaud 2015-05-15 16:48:24 CEST
This should be fixed as of Mga 5 RC as we've a quite a lot better grub2 integration

Status: NEW => RESOLVED
Resolution: (none) => FIXED