Bug 952950

Summary: unable to start the system after reboot
Product: [Fedora] Fedora Reporter: lnie <lnie>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: anaconda-maint-list, dshea, g.kaviyarasu, jonathan, lnie, mkolman, sbueno, twu, vanmeeuwen+fedora
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: 2014-03-03 14:28:05 UTC Type: Bug
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 Flags
screen shot
none
anaconda.log
none
program.log none

Description lnie 2013-04-17 04:16:52 UTC
Created attachment 736663 [details]
screen shot

Description of problem:

Make a install with "Encrypt my data" on the "INSTALLATION OPTIONS "page choosed.
After reboot ,the system failed to start ,as the attachment shows


Version-Release number of selected component (if applicable):
f19-Alpha-RC3-x86_64 

How reproducible:
100%
Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Tao Wu 2013-04-18 09:30:47 UTC
I also find it happened on F19 rc4 i386.

Comment 2 Chris Lumens 2013-04-22 15:56:16 UTC
If you can reproduce this, please attach /tmp/anaconda.log and /tmp/program.log from the end of installation to this bug report.  There's simply not enough information to go on here.

Comment 3 lnie 2013-04-23 05:24:48 UTC
Created attachment 738824 [details]
anaconda.log

Comment 4 lnie 2013-04-23 05:25:25 UTC
Created attachment 738825 [details]
program.log

Comment 5 David Shea 2014-02-28 15:04:23 UTC
Can you attach the rdsosreport.txt file mentioned in the error message? It would also be helpful if you boot with rd.debug=1 on the command line, and attached the rdsosreport.txt generated from that.

Comment 6 lnie 2014-03-03 08:41:12 UTC
The bug is fixed