Description of problem: In Mageia 4 if the bootloader is switched from grub legacy to grub2 using drakboot this works fine and the change is seamless. If the change is made AFTER upgrade to Mageia 5 it just fails silently, and the MBR still has legacy grub. Running grub2-install /dev/sda in the upgraded system writes a new MBR without problem and on the next boot grub2 works. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create Mga4 in VM with legacy grub - fully update it 2. Take snapshot 3. Use drakboot to switch bootloader to grub2 and test it 4. Restore snapshot and upgrade to Mageia 5 5. Reboot and take snapshot 6. use drakboot to switch bootloader to grub2. No errors, but bootloader is not installed, reboot is still using legacy. Reproducible: Steps to Reproduce:
Please look for drakbtoot actions using "journalctl SYSLOG_FACILITY=17" (or /var/log/explanations if you have rsyslog installed)
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaud
Humm found & fixed in git :-(
Status: NEW => RESOLVEDResolution: (none) => FIXED
commit a8702050b4b64fec08fba0a7e9495ad9e42561a3 Author: Thierry Vignaud <thierry.vignaud@...> Date: Tue Apr 7 04:58:21 2015 -0400 fix installing grub2 on MBR (mga#15640) regression introduced in: commit b0039ed72e22303c213539ed68315fd90c3c73f1 --- Commit Link: http://gitweb.mageia.org/software/drakx/commit/?id=a8702050b4b64fec08fba0a7e9495ad9e42561a3
*** Bug 15645 has been marked as a duplicate of this bug. ***
CC: (none) => wilcal.int
Summary: drakboot regression after upgrade from Mga4 => drakboot regression (not updating grub2 bootloader)
commit 7189033dc6e885f0aa29a4befadc824b3e82e8b4 Author: Thierry Vignaud <thierry.vignaud@...> Date: Tue Apr 7 04:58:21 2015 -0400 fix installing grub2 on MBR (mga#15640) regression introduced in: commit b0039ed72e22303c213539ed68315fd90c3c73f1 --- Commit Link: http://gitweb.mageia.org/software/drakx/commit/?id=7189033dc6e885f0aa29a4befadc824b3e82e8b4