Description of problem: I am installing FC3 from the DVD iso on a hard disk. When anaconda starts and tries to detect existing FC systems it finds none. I have two FC2 partitions, one is a clone of the other (FWIW, with different labels). Using the DVD in rescue mode detects both partitions. I have fscked and rebuilt the RPM database. What signature is anaconda looking for? Version-Release number of selected component (if applicable): FC3 anaconda How reproducible: every time Steps to Reproduce: 1. 2. 3. Actual results: No upgrade available Expected results: Additional info:
Same here, my old distro is FC2 upgraded from FC1. Anaconda does not find previous installation, I also tried with boot option "linux upgradeany" which I found from devel lists. There is no complaints in logs appearing on virtual console. Just plain "moving (1) to step installtype", no errors. FC2 is up-to-date version, updated latest today with apt-get. Here is some info about the system: # cat /etc/fstab | grep -v '^#\|^ .*\|^$' LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 LABEL=/home /home ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 none /sys sysfs defaults 0 0 LABEL=/var /var ext3 defaults 1 2 /dev/hda6 swap swap defaults 0 0 /dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0 /dev/cdrom1 /mnt/cdrom1 udf,iso9660 noauto,owner,kudzu,ro 0 0 # fdisk -l /dev/hda Disk /dev/hda: 203.9 GB, 203928109056 bytes 255 heads, 63 sectors/track, 24792 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 1 7 56196 83 Linux /dev/hda2 * 8 646 5132767+ b W95 FAT32 /dev/hda3 647 9729 72959197+ f W95 Ext'd (LBA) /dev/hda5 647 3257 20972826 b W95 FAT32 /dev/hda6 3258 3382 1004031 82 Linux swap /dev/hda7 3383 4130 6008278+ 83 Linux /dev/hda8 4131 4255 1004031 83 Linux /dev/hda9 4256 24792 164963421 83 Linux # e2label /dev/hda1;e2label /dev/hda7;e2label /dev/hda8;e2label /dev/hda9 /boot / /var /home
ok, now that I briefly took a glimpse at anaconda sources (getRedHatReleaseString), I assume you also want to know my system has the following stuff: $ rpm -q fedora-release fedora-release-2-4 $ ls -l /etc/*-release -rw-r--r-- 1 root root 33 May 11 2004 /etc/fedora-release lrwxrwxrwx 1 root root 14 Jul 5 12:16 /etc/redhat-release -> fedora-release $ cat /etc/redhat-release Fedora Core release 2 (Tettnang)
Can you switch to tty2 and grab /tmp/anaconda.log and attach it?
Created attachment 106743 [details] fc3 anaconda.log when it does not recognize fc2 this is the log
Created attachment 106750 [details] anaconda log after FC installation search
Does booting with 'linux upgradeany' help at all?
Yes that fixed the problem. However, both partitions were listed as 'Unknown Linux systems'. What is install looking for that is missing?
That means there's something that's not liked about the formatting of the /etc/redhat-release file. rpm -V fedora-release might show that it's modified.
For me it did not make any difference. Still not finding the partitions. I also tried rpm -e fedora-release, apt-get install fedora-release, and tried the install. no difference. I get this error: $ rpm -V fedora-release /etc/security/selinux/file_contexts: No such file or directory but it is some other error, probably in packaging of fedora-release rpm. I think I changed the hard drive to bigger one at some point. So it is not the original install, but I have copied either the partitions (dd) or the contents of partitions (cp) from old disk to new disk. Could there be some problem with that? I also tried adding boot flags to linux partitions, but no help, so I removed those again. BTW, I can mount those fc2 hdd partitions manually from tty2 from install cd linux no problem.
[root@opal tmp]# rpm -V fedora-release S.5....T /etc/fedora-release ....L... /etc/redhat-release This seems to indicate problems. I re-installed the original rpm but with no change.
Sounds like things are working as expected (fedora-release is a config file, so rpm won't replace it by default)
I did an rpm --force of the FC2 fedora-release on both partitions and both are now recognised. :-))
Never worked for me, so I just used apt-get dist-upgrade. It worked ok.