Bug 6954 - Choosing which installation to upgrade didn't work
Choosing which installation to upgrade didn't work
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
6.1
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Matt Wilson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-11-12 10:34 EST by heikki
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:
Environment:
Last Closed: 2000-02-22 11:12:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description heikki 1999-11-12 10:34:12 EST
We wanted to upgrade an old RedHat 5.0 installation, and at the same time
use a different root partition. So, we copied whole installation from
/dev/hda2 to /dev/hdb2, sticked in a boot diskette, and tried to upgrade
over ftp (that machine did not have a CD).

Answered /dev/hda to the question which one to upgrade.

All went smoothly, until we were informed that we didn't have enough disk
space (on a 1500M partition, filled with about 900M of the old
installation). (I report the disk size calculations as a separate bug)

Tried to delete stuff we were sure wouldbe reinstalled, and nothing helped.
Turned out that the install was trying to put things on hdb2. It had
mounted /dev/hdb2 as /mnt/sysimage(?)/ and hda2 as /mnt/sysimage/a2.

In the end we Fdisk'd /dev/hdb2 into an empty partition, so that the
installer would not find it, and would be forced to upgrade hda2. This
seemed to work, but we hit the disk size problem again, and had to stop for
today. Fdisk-created hd2 to Linux again, fsck'd it, and booted back to
normal.
Comment 1 Jay Turner 1999-11-29 15:09:59 EST
This issue has been forwarded to a developer for further action.
Comment 2 Jay Turner 2000-02-22 11:12:59 EST
This issue is resolved in the latest cut of the installer.

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