F5F Stay Refreshed Hardware Desktop Cloned drives consuming additional space

Cloned drives consuming additional space

Cloned drives consuming additional space

N
naTe_coRe_1084
Senior Member
254
06-17-2017, 07:44 PM
#1
I just completed cloning my boot drive from a 500gb SSD to a 2tb SSD and observed the space usage varied between the drives after booting from the clone. I followed the instructions in a YouTube tutorial by ThisBytesForYou (https://www.youtube.com/watch?v=e8omB4pFLlA). The source drive showed 442gb used while the target held 561gb. I’m curious about the difference. Pc Specs: Windows 10 64-bit, Ryzen 5 1600, 32GB DDR4 (2x16GB), 3000MHz, Gigabyte a320m-s2h, motherboard 430W EVGA PSU, GTX 1050ti. Source Drive: 500gb Kingston Target Drive: 2tb Crucial
N
naTe_coRe_1084
06-17-2017, 07:44 PM #1

I just completed cloning my boot drive from a 500gb SSD to a 2tb SSD and observed the space usage varied between the drives after booting from the clone. I followed the instructions in a YouTube tutorial by ThisBytesForYou (https://www.youtube.com/watch?v=e8omB4pFLlA). The source drive showed 442gb used while the target held 561gb. I’m curious about the difference. Pc Specs: Windows 10 64-bit, Ryzen 5 1600, 32GB DDR4 (2x16GB), 3000MHz, Gigabyte a320m-s2h, motherboard 430W EVGA PSU, GTX 1050ti. Source Drive: 500gb Kingston Target Drive: 2tb Crucial

D
DxDmaster00
Member
226
06-18-2017, 10:43 AM
#2
Are you aware of the allocation unit dimensions on each device? Setting the larger drive to utilize a bigger allocation unit can boost data size, especially when dealing with numerous small files.
D
DxDmaster00
06-18-2017, 10:43 AM #2

Are you aware of the allocation unit dimensions on each device? Setting the larger drive to utilize a bigger allocation unit can boost data size, especially when dealing with numerous small files.

L
lily9minimowi
Junior Member
31
06-20-2017, 12:58 AM
#3
Uncertain about identifying the allocation unit. The scan indicating more files on Drive C versus Drive F also confirms it's a clone. I checked for malware using Malwarebytes to rule out any infections during the cloning process.
L
lily9minimowi
06-20-2017, 12:58 AM #3

Uncertain about identifying the allocation unit. The scan indicating more files on Drive C versus Drive F also confirms it's a clone. I checked for malware using Malwarebytes to rule out any infections during the cloning process.

R
RepoRizer
Posting Freak
872
06-22-2017, 03:17 PM
#4
Ok, found the allocation units. Everything appears to be the same unless I'm missing something since I don't know what all the numbers in this list mean.
R
RepoRizer
06-22-2017, 03:17 PM #4

Ok, found the allocation units. Everything appears to be the same unless I'm missing something since I don't know what all the numbers in this list mean.

G
gigi_tron
Member
67
06-22-2017, 07:15 PM
#5
The allocation size remains consistent. It could be the software didn’t allocate units effectively, even though I haven’t used it. I generally don’t like cloning drives.
G
gigi_tron
06-22-2017, 07:15 PM #5

The allocation size remains consistent. It could be the software didn’t allocate units effectively, even though I haven’t used it. I generally don’t like cloning drives.

M
mahasa57
Junior Member
1
06-23-2017, 12:41 AM
#6
When preparing for cloning, it's wise to use Disk Cleanup as an administrator to remove unnecessary files such as cached thumbnails, restore points, log files, Windows Update data, and empty the recycle bin. Next, run Defrag as an administrator to clean up the source drive. Proceed with the cloning process. Once done, repeat Defrag and TRIM the destination drive. Finally, compare the two drives to see if the space difference stems from Windows adjusting the MFT and Swap file sizes based on capacity variations. Shadow Volume Copy could also contribute to the larger size.
M
mahasa57
06-23-2017, 12:41 AM #6

When preparing for cloning, it's wise to use Disk Cleanup as an administrator to remove unnecessary files such as cached thumbnails, restore points, log files, Windows Update data, and empty the recycle bin. Next, run Defrag as an administrator to clean up the source drive. Proceed with the cloning process. Once done, repeat Defrag and TRIM the destination drive. Finally, compare the two drives to see if the space difference stems from Windows adjusting the MFT and Swap file sizes based on capacity variations. Shadow Volume Copy could also contribute to the larger size.