Bug 8684

Summary: drakboot crashed
Product: Mageia Reporter: Constantin FABRIKEZIS <mageia.phikappa>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Normal CC: zen25000
Version: CauldronKeywords: NEEDINFO
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: drakxtools-15.14-3.mga3 CVE:
Status comment:

Description Constantin FABRIKEZIS 2013-01-14 11:08:17 CET
The "drakboot" program crashed. Drakbug-15.14 caught it.

installer le chargeur de démarage en passant de grub à grub2

grub2-install failed: /usr/sbin/grub2-bios-setupà: attentionà: Le système de fichiers ëàext2àû ne prend pas en charge l'embarquage.
/usr/sbin/grub2-bios-setupà: attentionà: L'embarquage est impossible. GRUB ne peut être installé sur cette configuration qu'en utilisant les listes de blocs. Cependant, les listes de blocs ne sont PAS fiables et leur utilisation est déconseillée..
/usr/sbin/grub2-bios-setupà: erreurà: refus de continuer avec les listes de blocs.
	...propagated at /usr/lib/libDrakX/any.pm line 267.
	...propagated at /usr/sbin/drakboot line 65.
Perl's trace:
standalone::bug_handler() called from /usr/sbin/drakboot:65

Theme name: Equinox Wide
Kernel version = 3.7.1-desktop-1.mga3
Distribution=Mageia release 3 (Cauldron) for x86_64
CPU=Intel(R) Core(TM) i5-2310 CPU @ 2.90GHz
Comment 1 Manuel Hiebel 2013-01-18 22:47:01 CET
Where did you install grub2, on / ?

Keywords: (none) => NEEDINFO

Comment 2 Barry Jackson 2013-01-18 23:11:26 CET
See https://bugs.mageia.org/show_bug.cgi?id=8742

If grub2 is installed then you can boot into it from grub or grub2 on another system using multiboot from grub2 like this:

menuentry 'Mageia-3 Beta 2 net' {
search --no-floppy --label --set=root mga3b2net
multiboot /boot/grub2/i386-pc/core.img

You can also use --uuid instead of label if you wish.

Or from a grub legacy system use:

title Mageia-3
root (hdx,y)
kernel /boot/grub/core.img

CC: (none) => zen25000

Comment 3 Manuel Hiebel 2013-02-01 00:59:19 CET

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

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