Bug 1468 - Hanging during package scan phase of upgrade
Hanging during package scan phase of upgrade
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-03-10 03:05 EST by jimcr
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-03-12 15:09:19 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description jimcr 1999-03-10 03:05:05 EST
Im unable to upgrade a 486-33 from RedHat 4.0 to RedHat
5.2.  Ive
tried both local CD-ROM and NFS install, in both cases the
hangs while "scanning packages".

Doing a local CD-ROM install:

Alt-F3: (last 2 lines before hang)
* making symlink from /tmp/rhimage to image
* psFromHeaderListDesc read 573 headers

Also FWIW, cdrom wouldnt eject without a power-down, with a
reboot, the eject button doesnt work.

Doing NFS install, Alt-F4 says;

<4>NFS server not responding, still trying
<4>NFS server OK
<4>NFS server not responding, still trying
<4>NFS server OK
<4>Couldn't get a free page is running Redhat 5.1, and NFS works between 2
for normal boots.  I dont know what the free-page problem is
but cant find any log-file entry that helps to explain it.
cdrom spun up just after NFS IPs were set during install,
pings from
.254 work to the .100 machine, ie the one doing upgrade.

In both cases Alt-F2 prompt was really sluggish (even for a
486), I
waited 15 minutes for a 'ps' before giving up.

Im using recently downloaed images
06012  1440 boot.img.new
65505  1440 supp.img.new
Comment 1 David Lawrence 1999-03-12 15:09:59 EST
If your machine contains 8 megs of ram or less then that is what is
causing the problem. We are working on a solution to this and will
post an update when it is finished. Until then one possible workaround
is to upgrade the ram to at least 16 megs for the install process. You
can then downgrade back to 8 if needed after.

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