Bug 896729 - can't properly handle partition sizes
Summary: can't properly handle partition sizes
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
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: 2013-01-17 21:06 UTC by BuggyFe
Modified: 2013-08-21 18:33 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-21 18:33:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda log (96.19 KB, application/octet-stream)
2013-01-19 01:19 UTC, BuggyFe
no flags Details
storage log (837.67 KB, application/octet-stream)
2013-01-19 01:21 UTC, BuggyFe
no flags Details

Description BuggyFe 2013-01-17 21:06:59 UTC
Description of problem:

when try to make custom disc partitioning, the partition size can be change only on so to say 1st try, then it gets frozen. Then the partition size appears to be not one, which has been set up. Has some extra troubles with NTFS (it is not in the list for a new partition)
   
Version-Release number of selected component (if applicable):
18

How reproducible:
100%

Steps to Reproduce:
1. try to make custom partitioning for dual boot
2.
3.
  
Actual results:

complete mess

Expected results:

partitioning as it was in previous versions

Additional info:

minor point, in the current installation/partitioning it is guessed that 1GB=1000MB, in most of systems 1GB = 1024MB

Comment 1 Steve Tyler 2013-01-18 04:54:16 UTC
(In reply to comment #0)
...
> minor point, in the current installation/partitioning it is guessed that
> 1GB=1000MB, in most of systems 1GB = 1024MB

Thanks for your report. Problems with display and conversion of storage units have been reported in this bug:
Bug 890711 - Anaconda Manual Partitioning Incorrectly Converts Unit Sizes

Comment 2 Chris Lumens 2013-01-18 15:27:46 UTC
Can you please attach /tmp/anaconda.log and /tmp/storage.log for your initial problem to this bug report?  Thanks.

Comment 3 BuggyFe 2013-01-19 01:19:58 UTC
Created attachment 682850 [details]
anaconda log

this is not the original trouble, it's a simpler case, I just try to repartition only one of the pre-set partitions and keep all other as they are and it still doesn't get through

Comment 4 BuggyFe 2013-01-19 01:21:29 UTC
Created attachment 682851 [details]
storage log

the same as for anaconda.log attached

Comment 5 BuggyFe 2013-01-19 01:32:55 UTC
I tried a simpler case: repartition only one of the pre-set partitions (pre-set, I mean ones which has been created by Fujitsu bootable disc provided with the notebook to restore the system (Windows 8)). It had an option to resize 2 partitions on the discs (C and D). So, I've made C partition set to allowed minimum 80GB and D - the rest of the disc (main part). Than using Fedora 18 installation procedure (running your anaconda), I try only to reformat what was partition D in the factory case (just looking on the size one can't make a mistake). I deleted D partition and tried to create what I need for my linux installation. Generalli it went smoothly in the set up up to the point where the partitions have to be created (before I was unable to get even there). As a result I got "error checking storage configuration" and the installer can't proceed further.

Comment 6 BuggyFe 2013-01-19 05:18:35 UTC
appeared, crucial step to finish partitioning and start installation was to create 200mb partition /boot/efi of EFI system type. It may be a good idea to make a message to a user when partitioning can't be completed for this reason.

Comment 7 Chris Lumens 2013-03-04 15:16:08 UTC
Partitioning errors are displayed as a bright red bar at the bottom of custom partitioning that you can click on to display the details, or as an orange bar at the bottom of the hub and initial storage spoke that you can also click on to display the details.  It's unclear to me whether you are seeing these or not.

We've been working a lot on storage UI post-F18, though, so please test this again with F19 alpha (which won't be out for a couple months, though) or with a rawhide image and let me know if this is working better for you.  Thanks.


Note You need to log in before you can comment on or make changes to this bug.