Bug 2571 - drakboot crashed (mkinitrd failed:)
Summary: drakboot crashed (mkinitrd failed:)
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-08-31 09:53 CEST by leo lenoir
Modified: 2011-12-03 20:55 CET (History)
3 users (show)

See Also:
Source RPM: drakxtools-13.58-1.mga1
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description leo lenoir 2011-08-31 09:53:20 CEST 
The "drakboot" program crashed. Drakbug-13.58 caught it.

Modification : remplacement de hd2 par hd1

Backtrace was:
mkinitrd failed:
(mkinitrd -f (hd2,0)/boot/initrd.img 2.6.36.2-desktop-2mnb) at /usr/lib/libDrakX/bootloader.pm line 124.
	...propagated at /usr/sbin/drakboot line 65.
standalone::bug_handler() called from /usr/sbin/drakboot:65

Kernel version = 2.6.38.7-desktop-1.mga
Distribution=Mageia release 1 (Official) for x86_64
CPU=Intel(R) Core(TM)2 Duo CPU     E4600  @ 2.40GHz
Manuel Hiebel 2011-08-31 10:30:55 CEST

Component: Release (media, process) => RPM Packages

Comment 1 Dave Hodgins 2011-08-31 10:40:38 CEST 
Are you installing under VirtualBox?  If so, this bug may be a duplicate
of bug 44.

CC: (none) => davidwhodgins

Comment 2 Samuel Verschelde 2011-10-01 17:43:02 CEST 
please answer to the question in comment #1 if you want any chance for us to understand what the problem and find a possible solution :)

CC: (none) => stormi

Samuel Verschelde 2011-10-01 17:45:47 CEST

Keywords: (none) => NEEDINFO

Comment 3 Marja Van Waes 2011-12-03 20:55:34 CET 
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.