Bug 1468

Summary: Hanging during package scan phase of upgrade
Product: [Retired] Red Hat Linux Reporter: jimcr
Component: installerAssignee: David Lawrence <dkl>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-03-12 20:09:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description jimcr 1999-03-10 08:05:05 UTC
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
process
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
simple
reboot, the eject button doesnt work.


Doing NFS install, Alt-F4 says;

<4>NFS server 192.168.1.254 not responding, still trying
<4>NFS server 192.168.1.254 OK
<4>NFS server 192.168.1.254 not responding, still trying
<4>NFS server 192.168.1.254 OK
<4>Couldn't get a free page

192.168.1.254 is running Redhat 5.1, and NFS works between 2
machines
for normal boots.  I dont know what the free-page problem is
about,
but cant find any log-file entry that helps to explain it.
Last,
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 20:09:59 UTC
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.