Bug 5875 - Install program (python/anaconda) from HD crashes when scanning packages
Summary: Install program (python/anaconda) from HD crashes when scanning packages
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jay Turner
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-10-12 09:05 UTC by diego.santacruz
Modified: 2015-01-07 23:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-10-21 17:38:03 UTC

Attachments (Terms of Use)

Description diego.santacruz 1999-10-12 09:05:31 UTC
I downloaded the ISO image and burned a CD-ROM, after giving
up with CD-ROM install (see bug #5873) I copied the files to
a HD (VFAT, FAT16 partition) and installed from there.
Everything went fine until it starts scanning the packages
on the HD. The python/anaconda install program crashes with
the following message:

File "/usr/bin/anaconda.real",
  line 225, in ?
  intf.run(todo, test = test)
  xt.py", line 1000, in run
  rc = apply (step[1](), step[2])
  ", line 10, in __call__
  do.py", line 90, in getHeaderList
  self.hdList =
  rddrive.py", line 46, in readHeaders
  return HeaderList(hl)
  mps.py", line 50, in __init__
  name = h[rpm.RPMTAG_NAME]
  TypeError: unscriptable object

The I have the option to debug or "OK", Hitting "OK" halts
(i.e. shutdown procedure)  the machine.

Probably the same as bug #5551.

Comment 1 jun.yang 1999-10-14 00:02:59 UTC
I have encountered exactly the same problem.  In the Python debugger,
I printed out h=NONE; rpm.RPMTAG_NAME=1000; h[0][1000]=netscape-comm;
h[1][1000]=netscape-communicator; etc.  It failed on a FAT FS on a
SCSI drive and a ext2fs on an EIDE driver.  Hope this helps.

Comment 2 Anonymous 1999-10-14 04:59:59 UTC
Ive Been getting the exact same error on a new install.  Ive got the
entire 6.1 dist on a ext2 hard disk.  Ive tried many different
install options and hd locations.  Currently, the drive is /dev/hdc1
I think this is the same as bug number 5749

Comment 3 Craig Kelley 1999-10-16 01:49:59 UTC
I have noticed the same behavior:

Boot with bootnet, and when you get to the partitioning type, select
fdisk and then continue (without editing any drives).  The error
messages will be there.

------- Additional Comments From   10/20/99 19:59 -------
I have the exact same problem when installing from a CD-ROM.  The ISO
was downloaded from ftp.redhat.com and it was burned.

When upgrading from 6.0 to 6.1 the installer crashes and creates the
same messsage as seen above.

Celerom 366, 64mb ram, 1G HD, Abit BM6 MB,
I doubt it's a system problem as i was running 6.0 with a uptime of
over 30 days before attempting this upgrade.

I do not have any wierd partitions on my drive either.  NO Fat16,
Fat32, NTFS or anything else like that.  Just a Swap partition and my
linux partition.

All 3 install options do not work, whether text, graphical or expert,

Comment 4 Jay Turner 1999-10-21 17:38:59 UTC
Please refer to bug #5555, and #5768, as there are problems which we
know are out there.  If neither of these bugs covers the problem which
you are seeing, then please reopen this bug with more details about
the specific failure that you are seeing as well as fstab and fdisk

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