Bug 797322
| Summary: | dracut Warning: Unable to process initqueue | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tom <thomasbelvin> | ||||||||
| Component: | lvm2 | Assignee: | Peter Rajnoha <prajnoha> | ||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | rawhide | CC: | agk, bmarzins, bmr, dracut-maint, dwysocha, emcnabb, gansalmon, harald, heinzm, itamar, jonathan, kernel-maint, lvm-team, madhu.chinakonda, mbroz, msnitzer, noctuorare, prajnoha, prockai, zkabelac | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | lvm2-2.02.94-1.fc18 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | |||||||||||
| : | 799535 (view as bug list) | Environment: | |||||||||
| Last Closed: | 2012-03-08 08:24:26 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Tom
2012-02-24 22:46:08 UTC
Trying 'dracut -f' stops older kernel from booting as well. Attached nonbooting dmesg with rd.debug added and rhgb removed. Created attachment 565725 [details]
nonbooting dmesg
(In reply to comment #1) > Trying 'dracut -f' stops older kernel from booting as well. > Attached nonbooting dmesg with rd.debug added and rhgb removed. What kernel version is this? Did udev, dracut, or device-mapper get updated around or before the kernels that have a problem? If rc4.git0.1 works, it might be using an older version of the userspace tools in the initramfs. Basically, dracut is failing to setup the device mapper devices that are used for your LVs. It says it can't find /dev/dm-*, which is odd. Can you capture the full boot log for the machine? Attached yum history and dmesg from last working boot. I can only chroot into my system now, since I haven't been able to get the dracut instructions to work for me. http://fedoraproject.org/wiki/How_to_debug_Dracut_problems#Accessing_the_root_volume_from_the_dracut_shell Created attachment 565778 [details]
yum history
Created attachment 565779 [details]
Working dmesg
I experience this problem on Gentoo Linux. It seems that /sbin/dmsetup from lvm2-2.02.92 no longer works with argument like "/dev/dm-0", which should work with 2.02.88. s/argument/device name Sorry Harald, is this something dracut needs to adjust to, or something the LVM team needs to fix? Boots for now since I took the 'rd.luks.uuid= ' line out of the kernel grub command, and simplified /etc/fstab without uuid. (In reply to comment #9) > Harald, is this something dracut needs to adjust to, or something the LVM team > needs to fix? I would like to have a comment from the LVM team, why the behaviour changed. What exactly changed? I tried "dmsetup table /dev/dm-X" which fails now (dmsetup table /dev/mapper/<name> still works, IMHO it is bug in dmsetup... (You should not use dm-X devices directly, these are not static, but that is different issue...) 3ffe9aa27d7dfb1bb8f06152e0097b437e4845b9 is the first bad commit
commit 3ffe9aa27d7dfb1bb8f06152e0097b437e4845b9
Author: Peter Rajnoha <prajnoha>
Date: Wed Feb 15 11:27:01 2012 +0000
Mangle device name on dm_task_set_name/newname call if necessary.
Peter, please can you check and fix it?
Regression. Blocker for 2.02.94. (Easy fix. 2.02.94 is due around Wednesday this week.) Fix checked in. |