Aller au contenu principal

Acronis says there is not enough disk space but there is plenty!

Thread needs solution

Hello, I have a vexing disk cloning issue. I am migrating a 2.5 TB hard drive with 14GB of data on it to a 256GB hard drive. I have been able to perform this cloning operation a number of times without any errors on other computers. Only this time when I try and clone the 2.5TB disk with only 14GB of data on it to the 256GB SSD drive I get an error "You need another 1.147 TB of free disk space available on the target hard drive to complete the operation with the current filter. Please exclude more files or folders, then try again" at stage "What to exclude". Where it is getting the 1.147 GB figure from is a mystery as the destination drive has 256GB free capacity. So hoping you can help me fix this issue?

thanks S

2 Users found this helpful

Stephen, is it 1.147 TB or 1.147 GB? You show it both ways.

Please perform a CHKDSK of the source 2.5TB drive as this type of issue can be caused by file system errors which in turn cause Acronis to switch to using Sector-by-Sector mode for backup or cloning.  Sector-by-Sector mode would want to copy nearly all of the 2.5TB source data thus will need a much larger target drive.

If you are attempting the clone from within Windows (using Active Clone), then check the log for any messages advising of errors being encountered.  Use the MVP Log Viewer tool to get to the log data - link in my signature.

Hello it is 1.147TB. Sorry I should have clarified. I will run a chkdsk now on the source disk and see if this clears up the error.

I ran a full scan disk but unfortunately the same issue occurs. I get through to selecting the destination disk, and then it creates a new stage named "What to exclude" with the message I described earlier. Is there anything else you can suggest?

What does Acronis mean by "The current filter"? Is there a way to adjust the current filter to one that works?

I am attempting to clone using the Acronis bootable media from a USB pen drive.

Stephen, sorry but we will need more information to try to understand what the core issue is here?

Can you make a note of the exact steps you are following here please, or snap images of those steps to share with us.

Also when in the rescue media, click on the Logs option in the left side menu, and capture an image of the log messages or else click on the top entry and take the option to save the log data to your USB pen drive and post that text file for us.

The reference to 'current filter' would suggest that some exclusions are being set perhaps, but that is just a guess!

I created a bootable Linux USB drive using the "Bootable Rescue Media Builder"
I booted up the PC with the SATA SSD drive of 256GB and the regular hard drive of 2.5TB attached, into the Acronis environment.
I went to "Tools & Utlilties", "Clone Disk". I then selected 
"Clone Mode->Manual", "Source disk->2.5TB disk", Destination Disk->256GB SSD drive", then it gives me a menu option "What to exclude" with the message I have screen shotted for you.
I could not find any option to log within the Acronis bootable media. I can see a "logs" tab on the acronis boot manager tool (see attached image), but when in the clone disk tool I cannot access the logs.

Although I've not used the clone method, I am curious about what I see on your screen shot. Why is the exclusion listing two hard drives? I can't see the complete sizes of the C: and D:. Are these two partitions of one drive or are they two separate drives? It's looking like you are trying to clone both C: and D:.

If both C: and D: are on the one drive this could explain the result when "attempting" to clone. Cloning is disk based not partition based, so you need to include the data on both drives when working out if they will fit.

I suspect what need to be done is for a backup to be made of the disk, then restore partition C and any hidden partitions, and taking particular care that restore disk signature is selected. Hopefully this will work.

Before rebooting, disconnect the old drive - havoc is likely if you have Windows installations on separate drives. Once you have Windows up and running, attach the old drive in a USB dock, and either delete all partitions and then restore drive D to fill the disk, or delete all partitions other than D and then expand partition D to use all the available space on the old drive (use the Windows Disk Management Console - search for disk managment to find it - or your preferred portioning app).

Ian

Hello, yes I am trying to clone the entire disk, a C & a D drive. The C drive has 14GB used, and the D is almost empty.  I have been able to clone C & D together with previous drives where it resizes the partitions on the new SSD drive. Its just this particular disk cloning operation which has thrown the "What to exclude" screen.

Stephen, there is an easy test that you can do here.

Shrink your C: drive to say 100GB in size, then do the same for your almost empty D: drive, then retry the clone.

Try using the 'Shrink volume' option of Windows Disk Management and see how low this will let you try to shrink to.  I have found Disk Management to be the most difficult tool to use for shrinking as it won't handle many situations that dedicated partition tools such as MiniTool Partition Wizard handle with ease!

If WDM won't let you shrink to around 100GB, then this suggests it is balking when finding what Windows considers to be unmovable data blocks, in which case use Partition Wizard.

Hello Steve, 

Thanks for your help.

I removed the D drive altogether as it was not needed and shrank the C: drive partition to the maximum allowed by windows which turned out to be 704 GB. So indeed windows is finding unmoveable data blocks.

I am wondering if this is related to it asking "what to exclude"?  I am going to make a backup before trying to shirink the disk further. 

I felt I needed to post some thanks to the guys above who mentioned C: and D: as the root cause of the problem. It was and my existing 1TB drive has now successfully been cloned to a smaller 500GB SSD drive automatically by Acronis 2018.

I was getting the same error message as the first post and I know I've used previous versions of Acronis in the dim and distant to clone bigger drives to a smaller drive automatically. The error message was unhelpful.

In my case my 1TB disk had a C: 900GB and a D: 24GB on the same physical disk. There was also another physical drive in the laptop, a 24GB SSD, which wasn't even used. It showed up in Disk Management as a 24GB disk but the D: drive (also 24GB) was actually on disk 0 together with the C: drive.

No one would have purposely configured the laptop like this. I suspect the laptop was designed with a 24GB SSD with Windows 8 on. Or perhaps it was used as some sort of fast swap space or something. When the free Windows 10 upgrade came along I suspect it wouldn't fit in the 24GB SSD so the upgrader did some jiggery-pokery which ended up leaving me with a redundant fast SSD drive.

To resolve I used Disk Management to delete the D: volume. I then booted up into Acronis on a USB stick and this time I was able to use the clone wizard to automatically clone my existing drive to the new smaller SSD drive. Happy days.

Safari Wolf wrote:

Oops posted twice. Deleted text.

Very easy to do ... the vvveeerrryyy sssslllooowww (very slow) response time of the forum sever often causes me to do that. And for experience I should know better.

Ian