Bug 797455 - dracut: Partial mode. Incomplete logical volumes Unable to process initqueue
Summary: dracut: Partial mode. Incomplete logical volumes Unable to process initqueue
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: dracut-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-26 01:50 UTC by Wendell Baker
Modified: 2013-08-20 13:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-20 13:14:12 UTC
Type: ---


Attachments (Terms of Use)
dmesg output on the console... (1.09 MB, image/jpeg)
2012-02-26 01:52 UTC, Wendell Baker
no flags Details

Description Wendell Baker 2012-02-26 01:50:51 UTC
Description of problem:

anaconda install of rawhide is unbootable

Version-Release number of selected component (if applicable):

uname says
Linux (none) 3.3.0-0.rc4.git3.1.fc18.i686.PAE

How reproducible:

yes

Steps to Reproduce:
1. anaconda install of rawhide
2. LUKS for the container partition
3. / /home /local swap in reasonable proportions; swap = 2x RAM
  
Actual results:

unbootable; see picture

Expected results:

bootable.

Additional info:

the installed filesystem is good enough at /dev/mapper/vg_pendant-lv_root
I was able to mount that filesystem and poke around.
I was able to do bind-mounts to overwrite /bin /sbin /lib /usr and get more executables available.
The network is not up though, otherwise I'd submit dmesg.

Tried booting with rd.retry=3000 on the kernel boot line.  That took a long time to stabilize out, but the same result.  Picture nearby.

Comment 1 Wendell Baker 2012-02-26 01:52:51 UTC
Created attachment 565833 [details]
dmesg output on the console...

rawhide installs, but fails to boot.
The network is not yet up.

The hardware supports F16, and previous incarnations of rawhide circa three or four weeks ago.

Comment 3 ell1e 2012-05-11 15:05:49 UTC
This happens to me with TC4 and liveusb-creator -> usb stick and then attempting to launch the live system on a Thinkpad X121e. Is there a chance this will get fixed before F17 gets out?? It's a pretty horrible turnaway issue when people can't even start the installer.

Comment 5 John William 2012-06-03 17:21:32 UTC
Sadly, it looks like this made it into the F17 release. I cannot boot the USB install, network install image or the DVD install images. I also can not do a direct kernel boot either. So - absolutely no way to even boot into the installer that I can see on my machine.

I agree this is a complete turn-off for testers/users. I have a pretty vanilla Athlon machine, so booting to the installer should be no problem. Unless this bug is identified/fixed pretty quickly, I may just sit this one out and wait for F18.

Comment 6 Harald Hoyer 2012-06-04 09:52:16 UTC
can you all please provide more details please?

http://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_troubleshooting

Comment 7 John William 2012-06-09 15:23:56 UTC
I created boot DVD media using the Plextor tool to burn the DVD iso; both the full install DVD and the net install DVD. Neither boots - both fail with the "dracut Warning: /dev/disk/by-label/... does not exist"

I created the USB boot media with dd in F16. Booting it fails with "dracut Warning: unable to mount /dev/sr0"

Comment 8 Harald Hoyer 2012-06-12 13:02:50 UTC
(In reply to comment #7)
> I created boot DVD media using the Plextor tool to burn the DVD iso; both
> the full install DVD and the net install DVD. Neither boots - both fail with
> the "dracut Warning: /dev/disk/by-label/... does not exist"
> 
> I created the USB boot media with dd in F16. Booting it fails with "dracut
> Warning: unable to mount /dev/sr0"

you should use "livecd-iso-to-disk" rather than "dd" for that.

Comment 9 Fedora End Of Life 2013-04-03 14:40:15 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19


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