Bug 32526 - Installation abandons
Summary: Installation abandons
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.1
Hardware: i386
OS: Linux
high
high
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-21 13:36 UTC by udippel
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-04-02 19:38:30 UTC
Embargoed:


Attachments (Terms of Use)
Anaconda-Dump (10.25 KB, patch)
2001-03-21 13:41 UTC, udippel
no flags Details | Diff

Description udippel 2001-03-21 13:36:53 UTC
A new, customised installation doesn't go through due to an Anaconda-error.
I didn't set anything particular. Can only guess it has to do with the
system:
P-250, 32MB RAM.
Will attach the dump later

Comment 1 udippel 2001-03-21 13:41:49 UTC
Created attachment 13224 [details]
Anaconda-Dump

Comment 2 Michael Fulbright 2001-03-21 19:01:30 UTC
Did you goto the command prompt on VC2 and do any commands?

What are the steps to reproduce this issue?

Comment 3 udippel 2001-03-22 07:05:50 UTC
No, no! - What are the steps on this machine at least, *not* to reproduce??! I
tried several times from scratch. Everything the default; booting with boot.img
from diskette, us, no changes of firewall config, search for bad blocks, 1.5 GB
for /, 300 MB for /home, 200 MB for swap, 40 MB for /boot, tried DHCP and fixed
IP. The machine is okay but old, I use it for classroom demos. Quadruple-boots
fine to DOS, W95, NT and RH6.2. I have Wolverine (2 isos and the boot.img) in
the 'root' of a DOS-formatted, otherwise empty partition of 2GB. Just mail me if
you need details!

Comment 4 Michael Fulbright 2001-04-02 16:06:52 UTC
Brent please look into.

Comment 5 Brent Fox 2001-04-02 19:38:26 UTC
Looks like a duplicate of bug #27933.  Is this a hard drive install?

Comment 6 Brent Fox 2001-04-02 19:40:15 UTC
Actually, buy looking at the traceback, it's clear that this is a hard drive
install.  This bug was present in Wolverine but it was fixed internally in late
February.  Thanks for your report.


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