Bug 1198870 - F22 Alpha TC8 XFCE Live - Install fails custom partitioning, LUKS encrypted LVM + XFS
Summary: F22 Alpha TC8 XFCE Live - Install fails custom partitioning, LUKS encrypted L...
Keywords:
Status: CLOSED DUPLICATE of bug 1204546
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-05 01:14 UTC by Adam Miller
Modified: 2016-01-11 18:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-11 18:20:32 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
/tmp/anaconda.log (43.09 KB, text/plain)
2015-03-06 23:21 UTC, Adam Miller 		no flags Details
/tmp/ifcfg.log (1.92 KB, text/plain)
2015-03-06 23:22 UTC, Adam Miller 		no flags Details
/tmp/program.log (93.67 KB, text/plain)
2015-03-06 23:23 UTC, Adam Miller 		no flags Details
/tmp/sensitive-info.log (108 bytes, text/plain)
2015-03-06 23:24 UTC, Adam Miller 		no flags Details
/tmp/storage.log (385.65 KB, text/plain)
2015-03-06 23:24 UTC, Adam Miller 		no flags Details
/tmp/anaconda-tb-nMevLL (704.88 KB, text/plain)
2015-03-10 21:25 UTC, Adam Miller 		no flags Details
View All

Description Adam Miller 2015-03-05 01:14:41 UTC 
Description of problem:
My previous installation is LUKS encrypted volume with LVM and XFS on the LVs, I am attempting to mount my previous /home partition but reformat /boot (non-encrypted, non-LV), reformat / (on encrypted block device, LV), and reformat swap (on encrypted block device, LV). The installer accepts the configuration just fine but when I attempt to actually install, it fails and offers to report the failure and when I attempt to report the bug, the installer crashes and no longer responds.
Comment 1 David Shea 2015-03-05 14:20:15 UTC 
Please attach the logs from /tmp as individual, text/plain attachments.
Comment 2 Adam Miller 2015-03-06 23:20:07 UTC 
I ended up backing that data up, installing fresh, and restoring the data but I was able to reproduce using spare hardware. I used ext4 this time but the error appears to be the same. I have uploaded the log files. Please let me know if you need any more information.
Comment 3 Adam Miller 2015-03-06 23:21:29 UTC 
Created attachment 999020 [details]
/tmp/anaconda.log
Comment 4 Adam Miller 2015-03-06 23:22:08 UTC 
Created attachment 999021 [details]
/tmp/ifcfg.log
Comment 5 Adam Miller 2015-03-06 23:23:27 UTC 
Created attachment 999022 [details]
/tmp/program.log
Comment 6 Adam Miller 2015-03-06 23:24:08 UTC 
Created attachment 999023 [details]
/tmp/sensitive-info.log
Comment 7 Adam Miller 2015-03-06 23:24:45 UTC 
Created attachment 999024 [details]
/tmp/storage.log
Comment 8 David Shea 2015-03-07 13:56:17 UTC 
There should be a file in /tmp named anaconda-tb-*, containing the full traceback information. Can you attach this?
Comment 9 Adam Miller 2015-03-10 21:25:07 UTC 
Created attachment 1000169 [details]
/tmp/anaconda-tb-nMevLL
Comment 10 Ivan Pacheco 2015-03-23 00:51:10 UTC 
*** Bug 1204546 has been marked as a duplicate of this bug. ***
Comment 11 Adam Miller 2016-01-11 18:20:32 UTC 

*** This bug has been marked as a duplicate of bug 1204546 ***
Note You need to log in before you can comment on or make changes to this bug.