Bug 11813

Summary:	dracut builds non bootable initrd when running with kernel tmb-laptop
Product:	Mageia	Reporter:	Hervé Laurent <laurent.rv>
Component:	RPM Packages	Assignee:	Colin Guthrie <mageia>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	Kicer86, joequant, stormi-mageia, tmb
Version:	4	Keywords:	Triaged
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	dracut-034-10.mga4.src.rpm	CVE:
Status comment:
Attachments:	list of changed rpms dracut's log file

Description Hervé Laurent 2013-11-28 22:23:06 CET

When using kernel tmb-laptop, dracut builds an initrd that fails to boot.

Last lines of rdsosreport.txt :
[   36.617154] dracut: Scanning for all btrfs devices
[   37.132114] dracut: Scanning for all btrfs devices
[   37.141180] dracut Warning: Could not boot.
[   37.305694] dracut Warning: /dev/non-hostonly-lvm does not exist
+ '[' -f /run/initramfs/init.log ']'


Version-Release number of selected component (if applicable):034-10.mga4


How reproducible: Tested with Mageia 4 beta 1, every time


Steps to Reproduce:
1.
2.
3.

Workaround : boot with desktop kernel to build initrds

Reproducible: 

Steps to Reproduce:

Manuel Hiebel 2013-11-29 20:21:42 CET

Keywords: (none) => Triaged
Assignee: bugsquad => mageia

Comment 1 Joseph Wang 2013-12-07 16:18:21 CET

I'm also seeing this on my desk machine

CC: (none) => joequant

Comment 2 MichaÅ Walenciak 2013-12-31 11:56:10 CET

I've this also after yesterday's update (30th Dec) with desktop kernel.

full list of changed rpms in attachment

CC: (none) => Kicer86

Comment 3 MichaÅ Walenciak 2013-12-31 11:56:44 CET

Created attachment 4693 [details]
list of changed rpms

Comment 4 MichaÅ Walenciak 2013-12-31 11:58:44 CET

Created attachment 4694 [details]
dracut's log file

MichaÅ Walenciak 2013-12-31 12:25:19 CET

Severity: minor => major

Comment 5 Samuel Verschelde 2015-04-21 22:30:09 CEST

Thanks for reporting this bug.

kernel-tmb-laptop has been removed in Mageia 5, setting version to Mageia 4. If it appears to have been fixed before Mageia 4, please close. Otherwise, it can either be fixed in an update to Mageia 4 if Colin or tmb can do it, or it will be automatically closed when Mageia 4 reaches EOL.

CC: (none) => stormi, tmb
Version: Cauldron => 4

Comment 6 Samuel Verschelde 2015-09-21 13:20:07 CEST

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Comment 7 Marja Van Waes 2015-10-27 06:57:24 CET

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too).

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

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