Bug 729743

Summary: Boot fails due to user error
Product: [Fedora] Fedora Reporter: Bruno Wolff III <bruno>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: aquini, bruno, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-10 18:18:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg output from failed boot none

Description Bruno Wolff III 2011-08-10 17:55:48 UTC 
Created attachment 517667 [details]
dmesg output from failed boot

Description of problem:
This might be related to bug 726905, but the symptoms are different enough that I thought I would file a separate bug report.

I am including a dmesg report of the boot process since I got a shell prompt that allowed me to mount file systems despite the boot not succeeding.

The last part of dmesg output before I got the fallback shell prompt was:
[   15.157398] dracut: luksOpen /dev/md13 luks-4c784093-1d94-4285-8178-206baee45
f90
[   16.426048] dracut: luksOpen /dev/md14 luks-ab1ed7c7-d153-4d85-aff7-b852dfc93
7f6
[   40.139326] dracut Warning: No root device "block:/dev/mapper/4c784093-1d94-4
285-8178-206baee45f90" found

I have used the 2.6.40-4.fc15 and 2.6.40.1-2.fc15 kernels successfully on another f15 machine with a similar raid set up using version 0.90 arrays without a problem.

Version-Release number of selected component (if applicable):
2.6.40.1-2.fc15

How reproducible:
The problem happens every boot on the affected machine.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Bruno Wolff III 2011-08-10 18:08:41 UTC 
I was seeing some script errors reported on kernel updates, that I had forgotten about and the problem may really be related to that. I am currently running kernel-2.6.38.8-34.fc15.x86_64, but I thought there were some kernels after that one, but predating the 2.6.40 kernels that I also have trouble with. So this may be a case where I or a test update have put my system into a bad state.
Comment 2 Bruno Wolff III 2011-08-10 18:18:31 UTC 
I just did a reinstall and am still getting the scripting error that I was seeing before I went on vacation and forgot about. So this is alomost certainly something that broken on my machine and not a general problem. So I'll just close this one, though I may add a note later after I figure out what needed fixing.
Running Transaction
  Installing : kernel-2.6.40.1-2.fc15.x86_64                                1/1 
Non-fatal <unknown> scriptlet failure in rpm package kernel-2.6.40.1-2.fc15.x86_64
warning: (null) scriptlet failed, exit status 1

Installed:
  kernel.x86_64 0:2.6.40.1-2.fc15                                               

Complete!
Comment 3 Bruno Wolff III 2011-08-15 17:13:35 UTC 
I tracked down the problem and it was user error. At some point I manually fixed up my grub.conf and managed to leave out 'luks-' from the root device name and that bad configuration was copied forward as I updated kernels.
Fixing the entry and rerunning the update script to write the initramfs fixed the problem.