Cannot Manualy Type in new disk size in Acronis DD 11
I have found a bug in Acronis Disk Director 11. See the attached PDF to this post.
The issue here is that you cannot manually enter a disk size on a partition resize, and when you do enter a size manually, Acronis changes your manual size to the current used size of the volume.
If you were to commit this change you would end up with a OS that would not boot due to no free space on the partition.
This was not the behavior in version 10. You could manually enter a partition size.
Any ideas on a fix here?
Jon
I just tested this again, any entry into the volume size field reverts back to the used size of the disk, not to what I just typed. It does this with or without a decimal.
How does one get acronis to test this to confirm? I have this on VMware mini that I can upload somewhere if someone else wants to test this.
Did you include GB when you entered the number? For example: 20 GB
I think the default should be GB. I doubt most people are making MB or Byte sized partitions.
Ok, tested this again, and yes if you type GB in after the number it does work as desired. Still seems to be a bit flakey, as this was not the behavior in version 10.
I still see this as a bug needing to be fixed. Should you fail to type in GB after your size, it still defaults to the used size of the partition only leaving like 12K of free space. This would cause a machine to not reboot (due to zero free space) should someone commit the changes and not see that they did not get what they typed in the size box.
...Should you fail to type in GB after your size, it still defaults to the used size of the partition only leaving like 12K of free space. This would cause a machine to not reboot (due to zero free space) should someone commit the changes and not see that they did not get what they typed in the size box.
Jon:
The amount of unallocated space on a disk (space not allocated to any partition) has nothing to do with bootability. I have zero unallocated space on all of my disks and my PCs have no issue with booting.
Mark,
The "free space" here is inside the partiton. What Jon is saying is that if you don't watch out and DD does this on a Windows partition, the resized partition will have very little free space inside it. Windows will mostly have some problem because of this (no room to write any new data).
DD 11 is defaulting to BYTES. If you start with a 40GB partition and want to resize it to 60GB and just enter 60 into the box, DD 11 will try to resize it to 60 BYTES. This won't work so it then resizes up to the absolute minimum value based on the used space inside the partition (say 55.2GB). If you don't notice this, you'll end up resizing the partition to 55.2GB with only a few K of free space.
Exactly, and if you have a critical service or something that is required to boot and that service needs to write on the disk your screwed. Native windows without any other software may boot, but who runs a naked OS? Not many.
Bottom line here is, this is a bug, it's re-creatable, and it needs fixed.
The next question who or how does one get Acronis to fix this?
I know based on past experience that opening a support call is a waste of time. Been there, done that. This is not something that can be diagnosed from someone reading a flow chart.
Got it. Sorry for the confusion.
There are probably several ways to make this clearer - a drop-down list next to the size field to select Bytes, MB, or GB; explicitly display the units after the user has entered a number; etc.
This a MAJOR problem that really needs fixing.
Anybody from Acronis listening????????????????????????
Hello,
MudCrab, Mark and Jerry, thanks for your help.
Jon, on behalf of the whole Acronis team please accept our apologies for the inconvenience. As Jerry suggested, I've forwarded the request to the responsible person and we'll surely change GUI layout to make it more clearer in future builds of Acronis Disk Director 11 home.
Please reply to this thread if you have any further questions.
Thank you.