Bug 21726

Summary:	drakboot crashed when switching to GRUB2 (grub2-install: error: will not proceed with blocklists)
Product:	Mageia	Reporter:	Ilya Belov <belof.ilya>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	belof.ilya, marja11, thierry.vignaud, zen25000
Version:	6
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	drakxtools-17.88-1.mga6, grub2	CVE:
Status comment:
Attachments:	lspcidrake -v fstab device.map

Description Ilya Belov 2017-09-17 15:12:59 CEST

The "drakboot" program crashed. Drakbug-17.88 caught it.

Trying to set GRUB2 instead of GRUB
(Some messages were in Russian and I've translated it myself)

grub2-install failed: Installing for platform i386-pc.
grub2-install: warning: File system «fat» does not support embedding
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: oxygen-gtk
Kernel version = 4.9.50-desktop-1.mga6
Distribution=Mageia release 6 (Official) for x86_64
CPU=Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz

Comment 1 Ilya Belov 2017-09-17 15:14:59 CEST

Created attachment 9677 [details]
lspcidrake -v

Comment 2 Ilya Belov 2017-09-17 15:18:08 CEST

Created attachment 9678 [details]
fstab

Comment 3 Ilya Belov 2017-09-17 15:18:41 CEST

Created attachment 9679 [details]
device.map

Ilya Belov 2017-09-17 15:18:54 CEST

CC: (none) => belof.ilya

Comment 4 Marja Van Waes 2017-09-17 23:28:45 CEST

This report reminds me of bug #20023, but I'm not sure the cause is the same (there's mention of a dummy mbr in that report, but not in this one)

Assigning to the Mageia tools maintainers, CC'ing barjac.

Assignee: bugsquad => mageiatools
CC: (none) => marja11, zen25000

Comment 5 Barry Jackson 2017-09-18 13:26:30 CEST

This is yet another PC-BIOS / UEFI mix-up.

fstab would indicate that this is a UEFI installation, yet I suspect that grub2 as opposed to grub2-efi is installed for some reason.

Comment 6 Barry Jackson 2017-09-18 15:05:28 CEST

Marja, I think this is a duplicate of 21320 which is IMHO incorrectly marked as a duplicate of 20023.
Note the mention of fat partition in 21320, ESP? and the fact that again grub2 is in use not grub2-efi. (i386 mentioned by grub2 error)

Comment 7 Thierry Vignaud 2017-09-18 15:08:47 CEST

I doubt that. drakboot would install the right grub2 flavor depending on  whether /sys/firmware/efi exists or not.
I think the issue there is that Ilya tried to force installing grub2 on a vfat partition.

@Ilya: Can you provide more info at what choices you made when configuring grub2 in place of grub-legacy?

Source RPM: drakxtools-17.88-1.mga6 => drakxtools-17.88-1.mga6, grub2
Summary: drakboot crashed when switchig to GRUB2 => drakboot crashed when switching to GRUB2 (grub2-install: error: will not proceed with blocklists)
CC: (none) => thierry.vignaud
Keywords: (none) => NEEDINFO

Comment 8 Thierry Vignaud 2017-09-18 15:16:29 CEST

The issue is that when one switches from grub-legacy to grub2 on a non UEFI system[1], the list of boot devices is filtered for generic bootloader needs by bootloader::allowed_boot_parts() but we don't know yet that the user will later switch to grub2
However grub2 has more restrictions... See:
http://gitweb.mageia.org/software/drakx/tree/perl-install/bootloader.pm#n713

But as the switch to grub2 is done _after_, we got bit...

We could add a later check: if grub2 has been selected, we could popup with an error message.
Aka rerunning bootloader::allowed_boot_parts()  and making sure the choosen boot_device is part the new list.

Keywords: NEEDINFO => (none)

Thierry Vignaud 2017-09-18 15:30:44 CEST

Status: NEW => ASSIGNED
Assignee: mageiatools => thierry.vignaud

Comment 9 Thierry Vignaud 2017-09-18 15:32:47 CEST

Dup

*** This bug has been marked as a duplicate of bug 20023 ***

Resolution: (none) => DUPLICATE
Status: ASSIGNED => RESOLVED

Comment 10 Thierry Vignaud 2017-09-18 15:34:31 CEST


*** This bug has been marked as a duplicate of bug 21320 ***

Comment 11 Barry Jackson 2017-09-18 19:09:18 CEST

(In reply to Thierry Vignaud from comment #8)
> The issue is that when one switches from grub-legacy to grub2 on a non UEFI
> system[1], ...

but this system has a vfat /boot/EFI in fstab (#2) so it is a UEFI system, or am I missing something?