Bug 868588 - PartitioningError: partition is too large for BIOS Boot formatting (allowable size is 0 MB to 2 MB)
Summary: PartitioningError: partition is too large for BIOS Boot formatting (allowable...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0b90131ed529e37fa32e51b1fdd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-21 00:59 UTC by Reartes Guillermo
Modified: 2012-11-14 15:38 UTC (History)
4 users (show)

Fixed In Version: anaconda-18.28-1
Clone Of:
Environment:
Last Closed: 2012-11-14 15:38:30 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: anaconda-tb (425.55 KB, text/plain)
2012-10-21 00:59 UTC, Reartes Guillermo 		no flags Details
File: product (6 bytes, text/plain)
2012-10-21 00:59 UTC, Reartes Guillermo 		no flags Details
File: type (9 bytes, text/plain)
2012-10-21 00:59 UTC, Reartes Guillermo 		no flags Details
File: ifcfg.log (641 bytes, text/plain)
2012-10-21 01:00 UTC, Reartes Guillermo 		no flags Details
File: storage.log (251.75 KB, text/plain)
2012-10-21 01:00 UTC, Reartes Guillermo 		no flags Details
File: version (11 bytes, text/plain)
2012-10-21 01:00 UTC, Reartes Guillermo 		no flags Details
File: environ (780 bytes, text/plain)
2012-10-21 01:00 UTC, Reartes Guillermo 		no flags Details
File: anaconda.log (25.17 KB, text/plain)
2012-10-21 01:00 UTC, Reartes Guillermo 		no flags Details
File: syslog (60.78 KB, text/plain)
2012-10-21 01:00 UTC, Reartes Guillermo 		no flags Details
File: hashmarkername (8 bytes, text/plain)
2012-10-21 01:00 UTC, Reartes Guillermo 		no flags Details
File: packaging.log (2.38 KB, text/plain)
2012-10-21 01:00 UTC, Reartes Guillermo 		no flags Details
File: cmdline_file (96 bytes, text/plain)
2012-10-21 01:00 UTC, Reartes Guillermo 		no flags Details
File: release (24 bytes, text/plain)
2012-10-21 01:00 UTC, Reartes Guillermo 		no flags Details
File: program.log (45.82 KB, text/plain)
2012-10-21 01:00 UTC, Reartes Guillermo 		no flags Details
tried to remove a 'shadow' biosboot partition in unknown tree. (shadow = it is the same partition as / when i switched back from a 5g biosboot to an ext4 /) (88.85 KB, image/png)
2012-11-13 20:40 UTC, Reartes Guillermo 		no flags Details
View All

Description Reartes Guillermo 2012-10-21 00:59:40 UTC 
Description of problem:
switched partition to bios boot (previously /)

Version-Release number of selected component:
anaconda-18.19

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.19 exception report
:Traceback (most recent call first):
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/partitioning.py", line 802, in doPartitioning
:    part.format.maxSize))
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 430, in apply
:    doPartitioning(self.storage)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 108, in _runSpoke
:    action.apply()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 323, in _on_spoke_clicked
:    self._runSpoke(spoke)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 338, in _on_spoke_clicked
:    self._on_spoke_clicked(self._spokes[dest].selector, None, self._spokes[dest])
:PartitioningError: partition is too large for BIOS Boot formatting (allowable size is 0 MB to 2 MB)
Comment 1 Reartes Guillermo 2012-10-21 00:59:55 UTC 
Created attachment 630689 [details]
File: anaconda-tb
Comment 2 Reartes Guillermo 2012-10-21 00:59:57 UTC 
Created attachment 630690 [details]
File: product
Comment 3 Reartes Guillermo 2012-10-21 00:59:59 UTC 
Created attachment 630691 [details]
File: type
Comment 4 Reartes Guillermo 2012-10-21 01:00:02 UTC 
Created attachment 630692 [details]
File: ifcfg.log
Comment 5 Reartes Guillermo 2012-10-21 01:00:10 UTC 
Created attachment 630693 [details]
File: storage.log
Comment 6 Reartes Guillermo 2012-10-21 01:00:12 UTC 
Created attachment 630694 [details]
File: version
Comment 7 Reartes Guillermo 2012-10-21 01:00:14 UTC 
Created attachment 630695 [details]
File: environ
Comment 8 Reartes Guillermo 2012-10-21 01:00:18 UTC 
Created attachment 630696 [details]
File: anaconda.log
Comment 9 Reartes Guillermo 2012-10-21 01:00:21 UTC 
Created attachment 630697 [details]
File: syslog
Comment 10 Reartes Guillermo 2012-10-21 01:00:24 UTC 
Created attachment 630698 [details]
File: hashmarkername
Comment 11 Reartes Guillermo 2012-10-21 01:00:26 UTC 
Created attachment 630699 [details]
File: packaging.log
Comment 12 Reartes Guillermo 2012-10-21 01:00:28 UTC 
Created attachment 630700 [details]
File: cmdline_file
Comment 13 Reartes Guillermo 2012-10-21 01:00:31 UTC 
Created attachment 630701 [details]
File: release
Comment 14 Reartes Guillermo 2012-10-21 01:00:34 UTC 
Created attachment 630702 [details]
File: program.log
Comment 15 Reartes Guillermo 2012-11-05 22:51:53 UTC 
i deleted all partitions in the unknown tree
created with the wizard new ones
changed one of them to biosboot


Package: anaconda-18.24
OS Release: Fedora release 18-Beta-TC7
Comment 16 Chris Lumens 2012-11-13 16:21:42 UTC 
I can't reproduce this with anaconda-18.28.  Now I see the red bar at the bottom with the error text.  Is this now better for you too?
Comment 17 Reartes Guillermo 2012-11-13 20:40:42 UTC 
Created attachment 644377 [details]
tried to remove a 'shadow' biosboot partition in unknown tree. (shadow = it is the same partition as / when i switched back from a 5g biosboot to an ext4 /)

I no longer get the error described in comment #0. So at least the 'unknown error' part is solved. :-)

However, i can still cheat anaconda to do some weird stuff, for example what happened in the screen-shot. (maybe a new bug-report is needed?).
Comment 18 Chris Lumens 2012-11-14 15:38:30 UTC 
Yeah, a new bug report would be for the best.  We try to keep bugs to a single issue so we know when something's fixed.
Note You need to log in before you can comment on or make changes to this bug.