Bug 913198 - Can not boot, dracut fails to find drive
Summary: Can not boot, dracut fails to find drive
Keywords:
Status: CLOSED DUPLICATE of bug 902512
Alias: None
Product: Fedora
Classification: Fedora
Component: util-linux
Version: 18
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Karel Zak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-20 16:07 UTC by Carlisle Childress
Modified: 2013-02-28 15:24 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-02-28 13:23:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
fdisk -l (1.02 KB, text/plain)
2013-02-20 16:11 UTC, Carlisle Childress
no flags Details
/dev/disk/by-uuid (753 bytes, text/plain)
2013-02-20 16:14 UTC, Carlisle Childress
no flags Details
lsinitrd (190.25 KB, text/plain)
2013-02-20 16:16 UTC, Carlisle Childress
no flags Details
/boot/grub2/grub.cfg (4.61 KB, text/plain)
2013-02-20 16:17 UTC, Carlisle Childress
no flags Details
/etc/fstab (955 bytes, text/plain)
2013-02-20 16:18 UTC, Carlisle Childress
no flags Details
blkid (3.20 KB, text/plain)
2013-02-20 16:22 UTC, Carlisle Childress
no flags Details

Description Carlisle Childress 2013-02-20 16:07:12 UTC
Description of problem:
I have a booting problem very similar, if not identical to Bug 841466

Fedora 18 was install without upgrade in a partition which previously had Fedora 16. Initial Fedora 18 installed worked without any problems, but after I upgraded the kernel the new kernels failed to boot and I ended up in the dracut prompt with the following message:

dracut Warning: Unable to process initqueue
dracut Warning: /dev/disk/by-uuid/89fdb906-8904-4941-b701-5da5c21d4bc5 does not exist

I've confirmed the partition refered to by that uuid is accessible by other means and that smartctl is reporting no problems on the disk.  Booting into kernel 3.6.10 the kernel that was initially installed with Fedora 18 always worked, but any new kernel did not.  I did see this error when installing new kernels: "grubby fatal error: unable to find a suitable template"

While attempting to find a work around, I ran "dracut -f" and after that I could no longer boot with kernel 3.6.10

I did find a work around by changing the grub2 entry for 3.7.7 from root=UUID=89fdb906-8904-4941-b701-5da5c21d4bc5 to root=/dev/sda8  

and fstab to:

 ##UUID=89fdb906-8904-4941-b701-5da5c21d4bc5 /       ext4    defaults        1 1
/dev/sda8	/	ext4	defaults	1 1


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

dracut-024-23.git20130118.fc18.x86_64
kernel-3.6.10-4.fc18.x86_64
kernel-3.7.7-201.fc18.x86_64
kernel-3.7.8-202.fc18.x86_64 
Note: 3.7.8 was installed but no entries for it appear in grub2

How reproducible:

Every time until I found a work around.

Steps to Reproduce:
1. select kernel entry in grub2 that references partition by uuid
2. dracut warning messages issued
3. boot stops at dracut prompt
  
Actual results:
The OS fails to boot ( until I found work around )

Expected results:
The OS should boot.

Additional info:

Comment 1 Carlisle Childress 2013-02-20 16:11:57 UTC
Created attachment 700122 [details]
fdisk -l

sda1 is ntfs windows xp
sda2 is ext4 /boot for Fedora 17 and 18
sda3 is ext3 /boot for Centos 6
sda4 is extended partition
sda5 is swap
sda6 is ext4 /home shared between C6, F17, F18
sda7 is ext4 /usr/local shared between C6, F17, F18
sda8 is ext4 / Fedora 18
sda9 is ext4 / Centos 6
sda10 is ext4 empty but previously had Fedora 15 with btrfs
sda11 is ext4 / Fedora 17

Comment 2 Carlisle Childress 2013-02-20 16:14:28 UTC
Created attachment 700123 [details]
/dev/disk/by-uuid

Comment 3 Carlisle Childress 2013-02-20 16:16:22 UTC
Created attachment 700124 [details]
lsinitrd

Comment 4 Carlisle Childress 2013-02-20 16:17:27 UTC
Created attachment 700125 [details]
/boot/grub2/grub.cfg

Comment 5 Carlisle Childress 2013-02-20 16:18:14 UTC
Created attachment 700126 [details]
/etc/fstab

Comment 6 Carlisle Childress 2013-02-20 16:22:00 UTC
Created attachment 700128 [details]
blkid

Notice how /dev/sda8 is odd

Comment 7 Harald Hoyer 2013-02-28 11:28:02 UTC
(In reply to comment #6)
> Created attachment 700128 [details]
> blkid
> 
> Notice how /dev/sda8 is odd

did you try to convert ext4 to btrfs somehow?

reassigning to util-linux

Comment 8 Karel Zak 2013-02-28 13:23:40 UTC
update to util-linux 2.22-2.6

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

Comment 9 Carlisle Childress 2013-02-28 14:31:48 UTC
The sda8 filesystem was not converted from ext4 to btrfs.  It was formatted at install.  The problem however is not fixed.

Comment 10 Harald Hoyer 2013-02-28 15:02:23 UTC
(In reply to comment #9)
> The sda8 filesystem was not converted from ext4 to btrfs.  It was formatted
> at install.  The problem however is not fixed.

Ok, here are the steps:

# yum update util-linux

should be at least 2.22-2.6.

Check the output of:

# blkid /dev/sda8

If it is still outputting 
ID_FS_AMBIVALEN=filesystem:ext4:1.0 filesystem:btrfs

append the output of:

# LIBBLKID_DEBUG=0xffff blkid -o udev -p /dev/sda8


If the output looks ok:

Regenerate the initramfs, so that it includes the new util-linux

# dracut -f

Reboot and try to boot with
root=UUID=89fdb906-8904-4941-b701-5da5c21d4bc5

Comment 11 Carlisle Childress 2013-02-28 15:24:13 UTC
Sorry, I hadn't had my coffee when I wrote that.

The problem IS fixed.  

Thanks for your help. 

-another satisfied Fedora user.


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