Bug 142610 - Unable to upgrade FC2 -> FC3
Summary: Unable to upgrade FC2 -> FC3
Status: CLOSED DUPLICATE of bug 137846
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 3
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-12-10 21:23 UTC by Vincent Koldenhof
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-02-21 19:07:39 UTC

Attachments (Terms of Use)
Dump from anaconda (149.35 KB, text/plain)
2004-12-10 21:24 UTC, Vincent Koldenhof 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Vincent Koldenhof 2004-12-10 21:23:26 UTC 
Description of problem: I have a working FC2 installation installed on
SATA harddisk, which is partitioned on a RAID1 boot partition (/boot),
a RAID1 root partition (/) and a number of LVM volume groups. 

When I insert the FC3 DVD and boot from it, it recognized the fact
that i have a FC installation and gives me the choice to do an
upgrade. When I choose that I get an error ( Stack trace )
Comment 1 Vincent Koldenhof 2004-12-10 21:24:45 UTC 
Created attachment 108358 [details]
Dump from anaconda
Comment 2 Jeremy Katz 2004-12-10 22:00:29 UTC 

*** This bug has been marked as a duplicate of 137846 ***
Comment 3 Vincent Koldenhof 2004-12-13 23:27:46 UTC 
Ok.. I am a newbie with regards to linux and am don't know what to do
now.. I have tried to add labels to my partitions but that did not
help. As you say this bug is a duplicate, I have looked at the bug
#137846 but I cannot find a solution for this problem. ( unless solved
in cvs is a solution, in that case could you explain to me how I can
use that solution ) 

Please help me out here, I want to upgrade my linux system to fedora 3
but I am completly stuck at the moment.
Comment 4 Red Hat Bugzilla 2006-02-21 19:07:39 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.