Bug 190069

Summary: Anaconda hang when the install source is an firewire disk
Product: [Fedora] Fedora Reporter: Frank Büttner <bugzilla>
Component: anacondaAssignee: Peter Jones <pjones>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 5CC: stefan-r-rhbz, triage
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: bzcl34nup
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-04-24 14:11:06 UTC Type: ---
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
Anacon log file none

Description Frank Büttner 2006-04-27 09:56:35 UTC
Description of problem:
When the install source is an on an Firewire disk anaconda hang's.

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


How reproducible:


Steps to Reproduce:
1. Boot the System via the Fedora install PXE kernel and initrd
2. select harddisk as source for the files
3. after loading the graphic installer anaconda hangs.
  
Actual results:
anaconda hangs

Expected results:
working installation/update

Additional info:
When switch to console 3 the last output is:
INFO: moving (1) to step welcomne
INFO: moving (2) to step findrootparts

Comment 1 Frank Büttner 2006-04-27 09:56:35 UTC
Created attachment 128296 [details]
Anacon log file

Comment 2 Jeremy Katz 2006-04-28 01:18:10 UTC
Can you switch ttys when it hangs?  Does it help if you boot with 'linux nodmraid
'?

Comment 3 Frank Büttner 2006-04-28 06:49:12 UTC
Yes I can do this.
Thanks the option nodmraid was the solution. Now the update process will continue.

Comment 4 Stefan Richter 2008-03-04 16:31:32 UTC
Can this bug be closed?

Comment 5 Bug Zapper 2008-04-04 02:46:13 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 6 Joel Andres Granados 2008-04-24 14:11:06 UTC
There is a bug where the dmraid stuff just blocks.  This bug has not been solved
yet and we are still working to fix it.   However there is a work around.  If
you use nodmraid, the installer will ignore/skip the dmraid stuff allowing the
install to finish.  This is a workaround and does not fix the problem.
There is a long list of bugs that are filed against this problem.  This bug is
one of them.  We have decided to close all the related nodmraid bugs and leave
just one open that will represent all of the others.  So this bug will be duped
for this reason.

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