Bug 8869 - drakboot crashed
Summary: drakboot crashed
Status: RESOLVED DUPLICATE of bug 8462
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2013-01-28 18:11 CET by pat leny
Modified: 2013-02-01 00:59 CET (History)
0 users

See Also:
Source RPM: drakxtools-15.19-2.mga3
CVE:
Status comment:


Attachments

Description pat leny 2013-01-28 18:11:17 CET
The "drakboot" program crashed. Drakbug-15.19 caught it.

choisir grub2 comme gestionnaire de demarrage en mettant kernel 3.8.rc4 par defaut

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: oxygen-gtk
Kernel version = 3.8.0-desktop-0.rc4.1.mga3
Distribution=Mageia release 3 (Cauldron) for x86_64
CPU=AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
Comment 1 Manuel Hiebel 2013-01-28 18:18:20 CET
where have you installed grub2, at /, in the mbr, or other ?

Keywords: (none) => NEEDINFO

Comment 2 pat leny 2013-01-30 21:08:00 CET
where have you installed grub2, at /, in the mbr, or other ?

reponse : i have installed grub2 in mbr
when i choice kernel 3.8.rc4 its good
bye
Comment 3 Manuel Hiebel 2013-02-01 00:59:39 CET

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

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


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