Description of problem: text installer, diskdrake, VM with 8GB disk, i entered a 7000MB disk first, and after creation, i choose "choose different partition" and i get back to disk overview, and it lists unpartitioned space as 1.9TB instead of +-1GB. this is clearly wrong. Reproducible: Steps to Reproduce:
Created attachment 200 [details] weird disk overview this is the disk overview after making 1 / partition of 7000MB and 1 swap partition of 800MB on a VM disk of 8GB. seeing this, i have no confidence whatsoever if this is going to turn out ok.
after trying to go ahead, it gave errors, (that should be obvious), i had to search to find the default option of using available space... which seemed to work well.
Created attachment 202 [details] Normal disk overview Can you detail how you created partitions? I just tried and could not reproduce
well, hmmm ok. first, this is a vbox install with 8GB disk. not kvm or qemu, don't know if it matters. i did a bit of a mess though: 1. i created a partition and deleted it again 2. created it then but too high, 9000MB 3. looked at the disk info, it was totally bonkers 1.9TB 4. deleted it, and typed in 19000MB 5. looked at disk info 6. deleted it again. 7. created with 7000 / 8. selected the 'wrong' unpartition size 9. created with 800 swap 10. noticed that sda5 was now above sda1 and had 2 weird unallocated spaces in between... in your screenshot, where is your unallocated space?
CC: (none) => thierry.vignaudSummary: in text installer: unparitioned space is wrongly reported => in text installer: unpartitioned space is wrongly reported
Blocks: (none) => 1994
@ AL13N Can you reproduce this bug with Mga2a2? If so, can you only reproduce it by first trying to make a partition that is larger than your disk? Setting the severity to low, because hardly anyone does a text install
Keywords: (none) => NEEDINFOPriority: Normal => LowCC: (none) => marja11Source RPM: (none) => drakxtools
Please reply to the question above within two weeks from now, to avoid this bug being closed as OLD. (If you need more time, please say so)
(In reply to comment #6) > Please reply to the question above within two weeks from now, to avoid this bug > being closed as OLD. (If you need more time, please say so) giving you 2 weeks extra time, you mentioned on IRC how busy you are :)
2 weeks extra have passed ;) Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD
i'm sorry, the text installer was broken, so i couldn't test :-) now i have an update to this bug. it seems that the bug likely stems from the starting sector being accomodated, if you enter a number that's too high (even if it means colliding with other partitions, or even going negative in start sector). i'll post some screenshots
Status: RESOLVED => REOPENEDResolution: OLD => (none)
Created attachment 1711 [details] after typing a partition size and it's once too high, the start sector is being decreased thing is, if there's partition before, or whatever, the start sector shouldn't be decreased. i mean, if you want to enter a number in it, you are in front of the numbers, typing any number in it, will make the number 10 times as high, which is likely to go too high, immediately the starting sector is modified... i'd rather like to see a marking or color red, if too high, and being checked when pressing next, rather than the starting sector being modified. it was especially irritating when making a second partition, because, i can't remember what the starting sector was before... somewhere a number in the millions... one can confirm this by using the boot.iso and networkbooting the text installer
Keywords: NEEDINFO => (none)
@ pterjan assigning to you, because I understood you're the diskdrake guy :) Please assign back if I'm wrong (or assign on to the right person)
Assignee: bugsquad => pterjan
still there, see bug 648 as well
i meant bug 646
Blocks: 1994 => (none)
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
fixed together with that other bug
Status: REOPENED => RESOLVEDResolution: (none) => FIXED