Bug 473352

Summary: Anaconda crashes trying to upgrade from Fedora9 to Fedora10
Product: [Fedora] Fedora Reporter: Oleg Drokin <green>
Component: anacondaAssignee: David Lehman <dlehman>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 10CC: anaconda-maint-list, leonshadow77, russo.lutions, vikigoyal, weiler+redhat-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-03 21:39:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
exception log none

Description Oleg Drokin 2008-11-27 22:34:48 UTC
Created attachment 324922 [details]
exception log

Description of problem:
When doing upgrade from Fedora10 DVD, I gt a message that anaconda encountered an exception.

I am attaching the log generated.
Might have something to do with my encrypted device.

Comment 1 Oleg Drokin 2008-11-27 23:42:16 UTC
I just commented out this line in /etc/fstab and the upgrade proceeded past the point of failure:
/dev/mapper/backup /backups ext3 defaults 0 0

Comment 2 Chris Lumens 2008-12-08 14:57:38 UTC
*** Bug 475194 has been marked as a duplicate of this bug. ***

Comment 3 Chris Lumens 2008-12-15 15:02:32 UTC
*** Bug 476507 has been marked as a duplicate of this bug. ***

Comment 4 A.Russo 2008-12-20 04:21:25 UTC
I too experienced this bug. However, paring my fstab down to only the installed hard drives (3 of them, all SATA) did not make any difference. 

I was using preupgrade from F9 to F10 on x86_64.

I'd be willing to beta test any fixes if you can instruct me how to do it within the preupgrade framework.

Comment 5 David Lehman 2008-12-22 19:08:49 UTC
The basic problem is that there is no easy way to know that the device referenced by the fstab is a mapped LUKS device. (If the troublesome device is not a mapped LUKS device, you are seeing a different problem.)

The simplest solution is to change the mapping so that the mapped device starts with 'luks-', eg: 'luks-backups' (using the example from the original reporter). To do this, edit /etc/crypttab to change the mapping name so it begins with 'luks-', then edit /etc/fstab to use the new device (eg: /dev/mapper/luks-backups). After that, which should take no more than a few minutes, your upgrade should work.

Comment 6 Sam W. 2009-01-13 06:50:53 UTC
I think I've run into something similar with an f8 to f10 upgrade using the DVD.  I'm seeing: "Error mapping device mapper/foo as /home/foo; mount: special device /dev/mapper/foo does not exist".

The same error appears whether or not the passphrase is provided.

The solution suggested (prepending "luks-" to all of the labels) worked (so far), and it had to be added to both the regular partition and encrypted swap partition entries.

At the very least, I suggest this be added to the known bugs list.