Finaly stage of install fails for installing grub2. Failure is no config file. Solution is to use previous untill you can configure boot. Use defaults, bit go through entire setup. Then a config file is available at end of install This is on a new net install of cauldron on x86_64
Thank you for reporting this. Can you add some information about the system: BIOS/MBR or GPT/EFI. I am unsure what you mean by: > Solution is to use previous until you can configure boot. > Use defaults, but go through entire setup Use previous what? What defaults, where? Setup of what?
Summary: Failure to install boot image => net install of Cauldron fails at end installing Grub2 'no config file'CC: (none) => lewyssmith
(In reply to Lewis Smith from comment #1) > Thank you for reporting this. > Can you add some information about the system: BIOS/MBR or GPT/EFI. > > I am unsure what you mean by: > > Solution is to use previous until you can configure boot. Sorry, I was really tired. > > Use defaults, but go through entire setup > Use previous what? > What defaults, where? > Setup of what? Initial system setup/install: The screen for modifying all the sys info, network, grub services, etc. If left at the default values and just click next, when it is time to setup the boot image, it fails with: no grub3 cfg file. Using the previous button to back up to the system setup page and and configuring grub/boot from there, even though nothing is changed, will allow the install to finish. Just opening the dialog and using the defaults displayed is enough. Then at the boot install page, it just works. and allows the install to finish.
(In reply to Lewis Smith from comment #1) > Thank you for reporting this. > Can you add some information about the system: BIOS/MBR or GPT/EFI. Going to guess part of the problem is Mageia boot/grub rpm not automagically installed prior to configuration. I noticed the rpm was install when I also encountered the problem and had to go back to the boot configuration screen Original bug 26676. My install is on a GPT drive with bios set to CSM/Legacy OS for a MBR install which has a bios grub partition. I have a multi-boot install and have never had the problem until this mga8 Cauldron install.
CC: (none) => bittwister2
@James Thank you for the clarification. It looks as if the problem happens when you simply do not, on the final summary screen, 'configure' the bootloader - even if you then accept all the default parameters. The previous comment rather supports this. To avoid going back from the 'next' screen to the summary screen to then configure the bootloader, would it not work if the booloader was configured (with the default values) from the summary screen? I hesitate to ask you to try this - system installations take ages. That would change the bug a bit to 'you need to configure the bootloader at the summary screen'. @Bit Twister Thanks for your comment.
(In reply to Lewis Smith from comment #4) > @James > Thank you for the clarification. It looks as if the problem happens when you > simply do not, on the final summary screen, 'configure' the bootloader - > even if you then accept all the default parameters. The previous comment > rather supports this. > To avoid going back from the 'next' screen to the summary screen to then > configure the bootloader, would it not work if the booloader was configured > (with the default values) from the summary screen? I hesitate to ask you to > try this - system installations take ages. > That would change the bug a bit to 'you need to configure the bootloader at > the summary screen'. > > @Bit Twister > Thanks for your comment. I do believe you are correct. I'm not ready to install again, anytime soon. Since nothing is changed, by using previous button, I would highly expect that a "need to configure boot" message at the summary screen would be a cure. It wasn't that way in mga7 that I recall, so not sure what changed.
I guess it may help developers if you can provide the install log(s).
CC: (none) => fri
Created attachment 11665 [details] install.log
(In reply to Morgan Leijström from comment #6) > I guess it may help developers if you can provide the install log(s). Don't think they exisdt anymore, but tell me where to look and I will.
(In reply to Bit Twister from comment #7) > Created attachment 11665 [details] > install.log Thanks BT! Next time, I'll at least now I know where to look.
(In reply to james Whitby from comment #8) > > Don't think they exisdt anymore, but tell me where to look and I will. /root/drakx I should have looked at the install.log. No debug information there. It would be better to provide the ddebug.log After much scrolling around I find this tidbit * running: grub2-editenv list with root /mnt * program not found: grub2-editenv Tip: Prior to attaching ddebug.log xz --keep --format=xz ddebug.log then you attach ddebug.log.xz
Created attachment 11666 [details] ddebyug.log
So, more an installer than grub2 bug. Probably. The net install fails if the bootloader is not explicitly configured, even with default values. Not sure where to assign it, but tv should be be a good start.
CC: lewyssmith => (none)Assignee: bugsquad => thierry.vignaud
Fixed in git. Package and installer updates to follow.
Assignee: thierry.vignaud => mageiaCC: (none) => mageia
Fixed in new installer stage 2 image now mirroring out.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED