Skip to main content

origin HDD recognized as full

Thread needs solution

I have a big issue making a clone HDD from an HDD with 52 GB used on 500 gb of capability, into a 240 GB crucial SSD. I made a lot of Crucial cloning using Acronis without problems, but now, I can't resolve this one...

I've tried a first clone, but Acronis failed, suggesting me to make a full chkdsk to repair an error. I made it. From this point to now, every time I try to make a clone of this HDD, Acronis says me, in the "from-form" the right used space of the origin disk, but then, when I select the SSD (bx500) in the "into-form", it studies the situation and alerts me that it need a second destination SSD to full clone the HDD. 

I'm sorry for my English, but what can I do to find a way to clone?

0 Users found this helpful

Simone, welcome to these public User Forums.

I would strongly recommend making a full disk backup of your working source HDD to an external storage drive - this is your safety net in the event of something going badly wrong!

Creating that backup would also show whether there are any issues with the source HDD, i.e. are any errors generated during the backup process, plus the log file for the backup task can help show what such errors are?

Download a copy of the MVP Assistant log viewer tool and use this to look at the logs to see if they show any issues during the operation process?

The latest version of the new log viewer tool is at the link below.
MVP Assistant - New 2.0 with Rescue Media Builder (New Version 2.5.2)

If you have Disks & Partitions backups created on ATI 2020 or later using .tibx files, then look in the Backup Worker logs.

If you have Files & Folders backups using .tib files (or Disk backups from earlier versions using .tib files) or using Cloning then look in the Demon logs.

Other logs are shown by the MVP Assistant under the 'Active Logs' heading of the Log Viewer page of the Assistant.

The Schedule2 log contains information related to scheduled task but is one of the more difficult logs to read / work through.

The log files should be zipped to preserve their original file names if sharing in the forums and would need to be less than 3MB in size, otherwise you would need to share the zip file via a Cloud share service such as OneDrive, Dropbox etc.