Description of problem: Tried to set the size of the 'biosboot' partition to '1', but it seems to have interpretted it as '-1'. Version-Release number of selected component: anaconda-18.14 Additional info: libreport version: 2.0.14 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.1-1.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.14 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/size.py", line 79, in _parseSpec : raise ValueError("invalid size specification", spec) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/size.py", line 137, in __new__ : self = Decimal.__new__(cls, value=_parseSpec(spec)) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 701, in _do_refresh : selector = page.addDevice(self._mountpointName(mountpoint) or device.format.name, Size(spec="%f MB" % device.size), mountpoint, self.on_selector_clicked) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1484, in on_add_clicked : self._do_refresh() :ValueError: ('invalid size specification', '-1.000000 MB')
Created attachment 624565 [details] File: anaconda-tb
Created attachment 624566 [details] File: product
Created attachment 624567 [details] File: type
Created attachment 624568 [details] File: storage.log
Created attachment 624569 [details] File: version
Created attachment 624570 [details] File: environ
Created attachment 624571 [details] File: anaconda.log
Created attachment 624572 [details] File: syslog
Created attachment 624573 [details] File: hashmarkername
Created attachment 624574 [details] File: packaging.log
Created attachment 624575 [details] File: cmdline_file
Created attachment 624576 [details] File: release
Created attachment 624577 [details] File: program.log
tried to create a biosboot partition, to avoid a /boot by using GPT (hoping that anaconda would use GPT when one request a biosboot partition, since the disk is unpartitioned yet -new guest-) Package: anaconda-18.16 OS Release: Fedora release 18-Beta-TC4
(In reply to comment #14) > tried to create a biosboot partition, to avoid a /boot by using GPT (hoping > that anaconda would use GPT when one request a biosboot partition, since the > disk is unpartitioned yet -new guest-) GPT is not required to avoid creating a separate /boot filesystem. As long as your root filesystem lies within the first 2TB of a disk you can just skip creating /boot. If you're on x86 or EFI you can skip making /boot even if your root filesystem is on lvm. Anaconda will not change disklabel type based on requested partitions. If you want anaconda to create GPT disklabels by default, pass 'gpt' on the command line. I don't see why you would want to do this, though.
*** Bug 867377 has been marked as a duplicate of this bug. ***
*** Bug 868278 has been marked as a duplicate of this bug. ***
*** Bug 869381 has been marked as a duplicate of this bug. ***
David believes all these '-1.000000 MB' bugs are the same fundamental problem - despite people hitting them in different ways - and furthermore, that they all should be fixed by TC7. Can anyone who has a reliable reproducer for this please re-test with TC7 and confirm that this is fixed? Thanks!
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.