Skip to main content

Disk clone utility demands 699GB extra space on target drive

Thread needs solution

Hey everyone,

I'm trying to use the Clone Disk tool to clone an HDD to a new SSD.

HDD: 1TB of which ~180GB is in use
SDD: 250GB. Single partition, 0GB used/232GB available

Now when I try to clone the HDD to the SSD, Acronis tells me I require 699GB more space on the target drive to be able to continue. This is roughly the amount of stuff I deleted from the HDD in order to make it cloneable to the SSD. To be sure, it is not in the recycle bin - I made sure to empty that.

Does anybody know what could be the issue?

 

[Edit] In the "exclude" window I just clicked the "Users" folder. That's the folder where I deleted that roughly 699GB from. Instead of the 699GB Acronis told me to free up before, it now tells me I require another 131070 TB.

https://i.postimg.cc/QsJxbs42/Acronis-131-TB.png

0 Users found this helpful

Some new information:
I deleted the partition on the SSD so it now only has unallocated disk space. When I now try to clone, Acronis tells me:

"Cannot complete the cloning. The selected partition(s) on the source dive cannot be resized to fit a smaller drive because the source drive uses an unsupported or broken file system."

It is a simple NTFS, mind you. Does anyone know what causes this?

Jack, please run CHKDSK /F for each partition on your source drive to eliminate any file system errors.

Hi Steve,

Thanks for the reply! I ran chkdsk and it indeed found a problem. I proceeded to run chkdsk /f, had the error fixed and upon running chkdsk now, it tells me there are no problems with the drive. Acronis however still insists that "source drive uses an unsupported or broken file system". Nothing has changed. Do you have any further suggestions?

Jack, glad to hear that CHKDSK looks to have fixed part of this problem at least.  Have you done a full restart since running the tool?  If not, that would be the first suggestion (restart not shutdown & start up again).

Beyond that, try creating a new backup task for the same source with a different task name and see if that still gives the same issue?