Bug 20023 - drakboot crashed (grub2-install: error: will not proceed with blocklists.)
Summary: drakboot crashed (grub2-install: error: will not proceed with blocklists.)
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: High normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
: 20024 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-12-25 17:43 CET by Stuart Morgan
Modified: 2017-09-18 15:32 CEST (History)
4 users (show)

See Also:
Source RPM: drakxtools-17.65-1.mga6, grub2
CVE:
Status comment:


Attachments

Description Stuart Morgan 2016-12-25 17:43:02 CET
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.
Perl's trace:
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
Marja van Waes 2016-12-26 10:42:31 CET

CC: (none) => marja11, zen25000
Assignee: bugsquad => mageiatools
Summary: drakboot crashed => drakboot crashed (grub2-install: error: will not proceed with blocklists.)
Source RPM: drakxtools-17.65-1.mga6 => drakxtools-17.65-1.mga6, grub2

Comment 1 Marja van Waes 2016-12-26 10:43:01 CET
*** Bug 20024 has been marked as a duplicate of this bug. ***
Comment 2 Marja van Waes 2017-07-23 14:45:23 CEST
*** Bug 21320 has been marked as a duplicate of this bug. ***

CC: (none) => f.agrech

Rémi Verschelde 2017-07-24 14:35:32 CEST

Priority: Normal => High

Comment 3 Barry Jackson 2017-07-24 14:57:24 CEST
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.
Comment 4 Barry Jackson 2017-07-24 15:05:14 CEST
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.
Comment 5 Rémi Verschelde 2017-07-24 15:17:14 CEST
(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.
Comment 6 Barry Jackson 2017-07-24 17:39:45 CEST
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.
Comment 7 Thierry Vignaud 2017-09-18 15:32:47 CEST
*** Bug 21726 has been marked as a duplicate of this bug. ***

CC: (none) => belof.ilya


Note You need to log in before you can comment on or make changes to this bug.