Bug 519031
Summary: | RuntimeError: device is already mapped | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Frank Murphy <frankly3d> | ||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | rawhide | CC: | anaconda-maint-list, vanmeeuwen+fedora | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | anaconda_trace_hash:cc73975620e8af49978a8ddf12470c1ce1ffb30b83691d732f4028179ce0de15 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-08-25 19:37:38 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
Frank Murphy
2009-08-24 16:40:08 UTC
Created attachment 358480 [details]
Attached traceback automatically from anaconda.
home was pre-setup in /dev/sda3 install was to use free space before home for default partitions. had just inputted to use Irish keyboard, when exception happened. https://www.redhat.com/archives/fedora-list/2009-August/msg02201.html Portions of this may be relevant? As I also used gparted to setup the free-space. Palimpsest Disk Utility, havng refused to allow permission. Solved (Hopefully) When booting from the liveMedia. As a reflex, I always entered luks p\w when asked. If this is skipped, just press enter util boot continues. Partitioning (gparted\Palimpsest) and then install work fine. Maybe is may be the case for other similar events? That's not a solution, merely a workaround. Feel free to use it to avoid this problem, of course, but the underlying cause for the traceback should still be fixed. *** This bug has been marked as a duplicate of bug 508796 *** |