Bug 887494 - Upgrade from f16 -> 17 doesn't find f16 storage
Summary: Upgrade from f16 -> 17 doesn't find f16 storage
Keywords:
Status: CLOSED DUPLICATE of bug 835704
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 17
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-15 16:42 UTC by Sandro
Modified: 2012-12-22 20:50 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-22 20:50:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda logfile after upgrade stops (3.32 KB, text/x-log)
2012-12-15 16:42 UTC, Sandro
no flags Details
storage logfile after upgrade stops (94.78 KB, text/x-log)
2012-12-15 16:43 UTC, Sandro
no flags Details

Description Sandro 2012-12-15 16:42:49 UTC
Created attachment 664039 [details]
anaconda logfile after upgrade stops

Description of problem:
Trying to upgrade from fedora 16 to 17 via preupgrade or DVD. The installer does not find the "old" f16 installation stating that the installation is "too old". On console 3 (Alt-F3) it states that /dev/loop1 cannot be accessed or /mnt/sysimage is busy.

Version-Release number of selected component (if applicable):
F17 DVD or preupgrade

How reproducible:
always

Steps to Reproduce:
1. Boot via f17 DVD or preupgrade
2. choose Install or upgrade
3. Wait until "Examining Storage" finishes
  
Actual results:
Cannot upgrade

Expected results:
Upgrade to F17

Additional info:
see anaconda and storage logs attached

Comment 1 Sandro 2012-12-15 16:43:23 UTC
Created attachment 664040 [details]
storage logfile after upgrade stops

Comment 2 Sandro 2012-12-22 20:50:25 UTC
Hi,

Found the solution in https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=835704.

Thanks,
Sandro

*** This bug has been marked as a duplicate of bug 835704 ***


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