Bug 243561
| Summary: | Anaconda stalls on network installation at "Starting Installation" | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Carl-Johan Kjellander <carljohan> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 7 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-08-30 21:48:44 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: | |||
|
Description
Carl-Johan Kjellander
2007-06-09 19:03:30 UTC
I left the install from ftp://ftp.chl.chalmers.se/ running without touching it at the unrefreshed anaconda screen and did something else for a while. After a long time it actually started installing. But why this long wait with anaconda only using 1% CPU? And since it doesn't refresh the screen is just grey with a blue and dark grey bar, with no info about what it's doing. I did leave the installs from ftp://ftp.funet.fi/ running for 10 minutes and that is way to long for an unrefreshed screen. People will think that it's crashed, especially since the screensaver comes on, which should never happen. I also did a network install (via FTP), by booting from USB pen drive (diskboot.img). After I supplied the FTP mirror path, it started downloading the "stage2.img" file and thats where it stayed hung for 20 minutes. During this period, all its doing is downloading a 90MB file from the FTP server but gives no indication of how much has been downloaded. In the absence of any indicator (in bytes and/or percentage or even a progress bar) the user would think that the installer is hung. I thought the installer was hung and thats why I interrupted the install twice before actually going thru with it. I also switched console (ctrl-alt-f1 thru f7) and one of the consoles had info about what file was being downloaded but no progress indicator. After formatting the filesystem, once the package installation starts, I saw a similar anaconda hang (as reported in comment #1), when I switched to a text console and then switched back, the anaconda UI stayed frozen (unrefreshed) for a long time before regaining its normal state (displaying messages about which package is being installed). It must have stayed frozen for about 15 minutes or so. |