Bug 862568

Summary: "Fedora 18 Beta Test Compose 1 (TC1)" does not boot
Product: [Fedora] Fedora Reporter: Joachim Backes <joachim.backes>
Component: anacondaAssignee: Will Woods <wwoods>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: g.kaviyarasu, harald, jonathan, mbanas, Panos.Kavalagios, 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-02-05 12:25:48 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
Bootscreen during the boot
none
partial output #1 of journalctl
none
partial output #2 of journalctl
none
boot log with rd.debug rd.loglevel=77 none

Description Joachim Backes 2012-10-03 08:58:53 UTC
Created attachment 620694 [details]
Bootscreen during the boot

Description of problem:
I downloaded Fedora-18-Beta-TC1-x86_64-DVD.iso and burned it to a DVD.
Check media was OK!

But if booting (in VirtualBox), it stops in a very early phase. See
the attached screen shots.

Then I booted the DVD on a real machine, it stops with exactly the
same (negative) results.

bootscreen.jpg shows the boot screen, and the other show the output of
 the journalctl command (as recommended).

Kind regards



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


How reproducible:


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


Expected results:


Additional info:

Comment 1 Joachim Backes 2012-10-03 09:00:04 UTC
Created attachment 620704 [details]
partial output #1 of journalctl

Comment 2 Joachim Backes 2012-10-03 09:00:51 UTC
Created attachment 620705 [details]
partial output #2 of journalctl

Comment 3 Martin Banas 2012-10-03 10:24:29 UTC
Created attachment 620738 [details]
boot log with rd.debug rd.loglevel=77

Attaching boot log. Please let me know if you need anything else.

Comment 4 Panos Kavalagios 2012-10-22 12:49:35 UTC
The same issue affects alpha Fedora-18-Alpha-i386-DVD.iso. The host virtualbox is the latest VirtualBox-4.2-4.2.2_81494_fedora17-1.x86_64 for F17 64bit.

Comment 5 Fedora End Of Life 2013-12-21 09:01:31 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2014-02-05 12:25:52 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.