Description of problem: 1) Selected the install device, hit "Continue" 2) Selected the exisiting partition on which I want to install, clicked "-", confirmed that all data on that partition will be deleted 3) Clicked "+" Version-Release number of selected component: anaconda-18.29.2-1.fc18.x86_64 Additional info: libreport version: 2.0.17 cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8 kernel: 3.6.6-3.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.29.2 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/parted/disk.py", line 246, in addPartition : constraint.getPedConstraint()) : File "/usr/lib64/python2.7/site-packages/parted/decorators.py", line 32, in new : ret = fn(*args, **kwds) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/partitioning.py", line 1885, in growPartitions : constraint=constraint) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/partitioning.py", line 765, in doPartitioning : growPartitions(disks, partitions, free, size_sets=storage.size_sets) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1969, in allocatePartitions : doPartitioning(self) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1957, in setContainerMembers : self.allocatePartitions() : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2103, in newDevice : members=members, device=device) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1609, in on_add_clicked : disks=disks) :PartitionException: Unable to satisfy all constraints on the partition.
Created attachment 654380 [details] File: anaconda-tb
Created attachment 654381 [details] File: environ
Created attachment 654382 [details] File: type
Created attachment 654383 [details] File: ifcfg.log
Created attachment 654384 [details] File: storage.log
Created attachment 654385 [details] File: version
Created attachment 654386 [details] File: program.log
Created attachment 654387 [details] File: executable
Created attachment 654388 [details] File: product
Created attachment 654389 [details] File: anaconda.log
Created attachment 654390 [details] File: hashmarkername
Created attachment 654391 [details] File: cmdline_file
Created attachment 654392 [details] File: release
Created attachment 654393 [details] File: messages
Created attachment 654394 [details] File: other involved packages
I left out a couple of steps: 1) Selected the install device, hit "Continue" 2) Selected "I don't need help, let me customize disk partitioning" and "Standard Partition" Partition scheme configuration. Then clicked "Reclaim space". 3) Selected the exisiting partition on which I want to install, clicked "-", confirmed that all data on that partition will be deleted 4) Clicked "+" 5) Entered "/" in popup window
According to your steps in comment 16, it doesn't look like you gave a size to the newly created filesystem in the add dialog. Is that correct?
Correct, I did not give a size. I just retried and entered a size, the size of the existing partition. Same result: "An unknown error has occurred". I entered the size as "76.80GB". Is that the correct format? Is there a way for me to not enter the size and just use the existing partition?
Here's the fix: I entered "76.79 GB" and, success! It would be really nice if it there was a way to not have to enter a size, to just use the existing partition.
(In reply to comment #18) > Is there a way for me to not enter the size and just use the existing > partition? You don't use the + button to make use of an existing partition -- that is for creating _new_ devices. I realize the terminology used isn't as clear as it could be. To edit an existing partition, select it on the left side and then edit details on the right side. See here for some general instructions: NOTE: These are a draft, and unofficial, but they should help. https://fedoraproject.org/wiki/Anaconda/CustomSpokePrimer
The Anaconda/CustomSpokePrimer page is incredibly helpful, thanks! Re. this bug, the statement under Tips and Hints of that page that "You can enter sizes for new filesystems that are greater than the total available free space" might not be true, if I understand things correctly. I deleted the filesystem (sda7), but it wouldn't let me try to create a new one for which I entered a size that was .01 GB too large.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.