Bug 162121 - Installer does not recognize existing FC3 on FC4 Install
Installer does not recognize existing FC3 on FC4 Install
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Jones
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2005-06-30 00:15 EDT by Andy Schlei
Modified: 2008-02-17 14:57 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-02-17 14:57:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Anaconda.log from installation choice screen (7.92 KB, text/plain)
2005-07-19 21:42 EDT, Andy Schlei
no flags Details
Syslog from anaconda selection screen (21.33 KB, text/plain)
2005-07-19 21:43 EDT, Andy Schlei
no flags Details

  None (edit)
Description Andy Schlei 2005-06-30 00:15:37 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4

Description of problem:
Installing FC4 from either HTTP or DVD, over existing SMP install of FC3.  Installer looks for, but does not find, existing implementation, so only offers install, not upgrade options.

Upgrade has worked on non-SMP install of FC3

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot from DVD or boot.iso image
2. Start install process, select language, etc.
3. Anaconda offers only install, not upgrad options

Actual Results:  Anaconda goes down install, not upgrade path

Expected Results:  offers to upgrade current FC3 installation

Additional info:

Here is FSTAB:
/dev/VolGroup00/LogVol00 /                       ext3    defaults        1 1
/dev/VolGroup00/lvhome  /home                   ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
/dev/VolGroup00/LogVol01 swap                    swap    defaults        0 0
/dev/hdd                /media/cdrecorder       auto    pamconsole,exec,noauto,managed 0 0
/dev/fd0                /media/floppy           auto    pamconsole,exec,noauto,managed 0 0

Here is output from df -h

Filesystem            Size  Used Avail Use% Mounted on
                       93G   15G   75G  17% /
                      147G   69G   71G  50% /home
/dev/hda1              99M   32M   63M  34% /boot
none                  251M     0  251M   0% /dev/shm
Comment 1 Jeremy Katz 2005-07-08 14:29:27 EDT
What are the contents of /etc/fedora-release?  Also, does it work if you boot
with 'linux upgradeany'?
Comment 2 Andy Schlei 2005-07-17 21:14:31 EDT
Sorry for the delay in responding, I've been on vacation.

/etc/fedora-release is:
[andy@FedoraServer ~]$ cat /etc/fedora-release
Fedora Core release 3 (Heidelberg)

I booted from the boot.iso boot disc, ran with "linux upgradeany" and it still
did not find the existing installation and went immediately to the clean install
Comment 3 Jeremy Katz 2005-07-18 15:19:20 EDT
Can you switch to tty2 at the screen with the desktop, workstation and custom
choices and grab /tmp/anaconda.log and /tmp/syslog to attach here?
Comment 4 Andy Schlei 2005-07-19 21:42:09 EDT
Created attachment 116958 [details]
Anaconda.log from installation choice screen
Comment 5 Andy Schlei 2005-07-19 21:43:19 EDT
Created attachment 116959 [details]
Syslog from anaconda selection screen

As requested, the two files from tty2 during install process
Comment 6 Andy Schlei 2005-07-19 21:46:33 EDT
Files attached as requested.
Comment 7 Jeremy Katz 2005-07-25 23:56:40 EDT
For some reason, running the lvm commands is failing
Comment 8 Christian Iseli 2007-01-19 19:13:45 EST
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Comment 9 Andy Schlei 2007-01-20 13:43:00 EST
This bug is no longer relevant.  I cannot see if it is still a problem since all
my systems are now on FC6.

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