Bug 55697 - Setup Hangs after the installation type is chosen.
Summary: Setup Hangs after the installation type is chosen.
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-11-05 07:44 UTC by Need Real Name
Modified: 2007-04-18 16:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-11-05 15:07:18 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2001-11-05 07:44:15 UTC
Description of Problem:
    While installing Redhat 7.1, when i got to the second disk, for some 
reason it couldn't mount it. So i had to reboot the computer. In any case, 
from then on setup would hang every time after i would select the 
installation configuration (Workstation, Server...).
To fix it i had to go into rescue mode and run fdisk to clear out all the 
partitions the previous setup created. After this the setup no longer hung.

Version-Release number of selected component (if applicable):
  Red Hat 7.1 Standard (The free one, whichever that is.)

How Reproducible:
  Easy

Steps to Reproduce:
1. Instal as a server and reset the machine when it asks for the second CD.
2. Try to install it again, it hangs (or at least did on my box) after u 
choose what kind of installation u want.
3. 

Actual Results:


Expected Results:


Additional Information:
	I'd guess it has something to do with reading the partition 
information after u choose the installation type. But i'm no expert.

Anyways, just though I'd help you guys out.
Michael

Comment 1 Brent Fox 2001-11-08 16:02:50 UTC
I was unable to reproduce this behavior.  I did an install, and when prompted
for the second cd, I pressed Reset.  I rebooted, ran the install again, and was
able to view the partition table and continued the install with no problems. 
Resolving as 'worksforme'.  I don't know why your machine would have behaved
differently.


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