Cloned 340GB -> 128GB SSD. How did Acronis know to only reduce the C:\ partition ??

[GoodEnough]

Source disk had 3 partitions
A: 40MB
B: 14 GB
C: 285GB

Needed to copy entire drive to my new SSD drive. The destination drive only has 128GB so I wanted to simply compress partition C, since A & B had OS recovery data that could not be reduced. ie: Using the "proportional" resize would not be suitable.

I chose "exact copy" (not manual, not proportional) and somehow it knew to keep A & B their original size, and it reduced only C to make everything fit onto the 128GB SSD.

Clever trick! Without scanning the partitions, how did Acronis know that C was the partition that had all the unused space??

 

[phasseshifter]

makes sense prolly measured the amount of data on each partition and part c being the largest with the available free space was the safest way to do it..if it did at all because this is only a theory as i have never used the aforesaid program..

 

[ninaholic37]

I wonder if "exact copy" would have put all 3 on... if C was the first partition.

Without scanning the partitions, how did Acronis know that C was the partition that had all the unused space??

Probably by scanning the partitions :sneaky: Or maybe the partition still has the same record table as before and will blow up once C tries to write past 114GB :ninja: Or maybe it recreates the table for each new drive / when moving to SSD anyway :hmm: Or maybe it said "gee, can't make the last SSD partition larger than what's left" 😛