Cloned HDD to SDD. Used space is not the same

NicoFish

Commendable
Sep 17, 2016
3
0
1,510
I cloned the C: partition of my HDD(disk1) (using MiniTool Partition Wizard Free 9.1.) to a new 240 GB SDD (disk2). I would like to use the SSD to boot and the HDD for storage.

It seems to have worked fine I removed the HDD booted from the SDD no problem. I put the HDD back in and I noticed that the "used space" is no the same.

I have attached an image
http://

note: I did not copy the D: drive

Can anyone explain why this would happen? Was the copy done correctly? If the copy was done correctly should I just wipe all the partitions on Disk1

Thank you for your help. I am very new to the world of PC modification. I used the forum (old posts) extensively during the upgrade but could not find a relevant post.



 
Solution
Assuming your cloned SSD drive has booted without incident and functions without any problems, there is no reason to believe the disk-cloning operation was unsuccessful.

Understand that the d-c program will ordinarily proportionally clone the contents of the source disk to the destination disk. This obviously depends upon the amount of data being cloned and the disk-space available on the destination disk. From what I can see on the screenshot your provided the Mini-Tool program did its work just fine.

A difference in expected space utilization and also file and folder counts between the source and destination drives can be caused by a number of things, including the exclusion of the Windows swap file (pagefile.sys), hibernation file...
Assuming your cloned SSD drive has booted without incident and functions without any problems, there is no reason to believe the disk-cloning operation was unsuccessful.

Understand that the d-c program will ordinarily proportionally clone the contents of the source disk to the destination disk. This obviously depends upon the amount of data being cloned and the disk-space available on the destination disk. From what I can see on the screenshot your provided the Mini-Tool program did its work just fine.

A difference in expected space utilization and also file and folder counts between the source and destination drives can be caused by a number of things, including the exclusion of the Windows swap file (pagefile.sys), hibernation file (hiberfil.sys), and other temporary and instance specific files. This is simply an optimization feature the d-c program generally utilizes that speeds up the cloning process. So there is no need to be concerned about the difference in the total amount of data between the source and cloned destination disks. All that's important is what I indicated in my opening sentence.

Depending upon the d-c program other manipulations of data can be present, e.g., involving the user and/or Windows temp folders, various information and prefetch folders, as well as a host of files that are unnecessary for the cloned disk. If & when the clone is booted to the OS ALL the necessary files will be resurrected.

So you need not be concerned that your cloned SSD is not a viable, functional drive. Ensure that you work with it over a reasonable period of time to determine that is so. Do NOT make any changes to your source disk - the 1 TB HDD - until you're assured of this. Capiche?

When you are thus assured then you can make any changes you desire to your former boot drive.
 
Solution