The "drakboot" program crashed. Drakbug-17.65 caught it.
Running 'Set up boot system' from Mageia Control Centre
grub2-install failed: Installing for i386-pc platform.
grub2-install: warning: dummy mbr.
grub2-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
grub2-install: error: will not proceed with blocklists.
...propagated at /usr/lib/libDrakX/any.pm line 269.
...propagated at /usr/libexec/drakboot line 49.
drakbug::bug_handler() called from /usr/libexec/drakboot:49
Theme name: Qt4
Kernel version = 4.8.15-desktop-1.mga6
Distribution=Mageia release 6 (Cauldron) for x86_64
CPU=Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
drakboot crashed =>
drakboot crashed (grub2-install: error: will not proceed with blocklists.)Source RPM:
*** Bug 20024 has been marked as a duplicate of this bug. ***
*** Bug 21320 has been marked as a duplicate of this bug. ***
Looking at the error messages above it seems to indicate that the drive in question may be GPT with a 'dummy MBR'.
In this case a BIOS boot partition would be required to install in PC_BIOS mode and the installer should have noticed this, unless the intention was to install in UEFI mode and the PC-BIOS installer was used in error?
It does appear that the installer was in PC-BIOS mode as grub2 (not grub2-efi) is installed as witnessed by the "Installing for i386-pc platform" message.
I just realized that these may not be installer related at all - to me it's not clear whether these are happening during an install or from within a working system using drakboot from mcc.
(In reply to Barry Jackson from comment #4)
> to me it's not clear whether these are happening during an install or from
> within a working system using drakboot from mcc.
At least for the initial report of comment 0, it would be the latter:
(In reply to Stuart Morgan from comment #0)
> Running 'Set up boot system' from Mageia Control Centre
It's also more difficult to retrieve such error logs from a failing install than from a working system where drakbug will pop up, so it's likely safe to assume that the duplicates are also from a live system.
Right, looking at the dates the only recent one is 21320 which was using mcc->drakboot in Mga6 after upgrade from Mga5.
If the Mga5 was PC-BIOS using grub legacy then it would update to Mga6 with grub legacy, so this is a different bug to the others as there is no suggestion of GPT. (the others mention 'dummy MBR' which to me implies GPT)
Maybe 21320 should not be marked as a duplicate of this one, it is new, different and the others (this and the other dup) are 6 months old cauldron.
*** Bug 21726 has been marked as a duplicate of this bug. ***