Loss of space after cloning
perse -
Hello,
I cloned my 1TB hard drive to a 2TB drive with HDclone, but when I go to disk management, I find myself with a C volume of 930.66GB with 15.95GB free. In storage settings, the information is the same. This makes sense since I cloned a 1GB drive, but where has the additional 1GB gone?
7 answers
Hello,
Disk management shows the disk at its nominal capacity.
It is likely that in the free version, HDClone only copies "1:1" using the "auto-expand" function, which adjusts the sector sizes so that the image exactly matches the source, including its size: use another cloning tool (CloneZilla, Macrium Reflect...)
Hello, thank you for the response,
I tried with Macrium Reflect but an error 9 appeared so I gave up on Macrium.
There is no anomaly. A 1TB disk is recognized by the computer, which counts in binary, as having a capacity of about 931GB, so it is normal that the 2TB disk has a capacity of 1862GB.
Indeed, there seems to be an anomaly. The information provided about Disk 0 at the top does not match that given at the bottom.
At the top, Disk 0 has a capacity of 930GB and some. So it corresponds to a 1TB drive, whereas in the diagram at the bottom, it has a capacity of 1860GB, with no unallocated space, thus corresponding to a 2TB drive.
Hello,
I understand that there is a difference between theoretical capacity and actual capacity, that's not the issue. My problem is that I can't clone my hard drive; it stops at a single partition.
"I cloned my 1TB hard drive to a 2TB drive using HDclone, but when I go to disk management, I find a C volume of 930.66GB with 15.95GB free. In the storage settings, the information is the same. This seems natural since I cloned a 1GB drive, but where has the extra 1GB gone?"
I have a hard time understanding what you're saying. The screenshot you posted corresponds to your 2TB drive with the cloning. On this drive, there is no anomaly. Perhaps you meant that your source drive has 2 partitions and that on the target drive, there is only one partition. But this is not clearly stated in what you wrote. If that's the case, I don’t know HDClone, which might only clone the system partition. Macrium Reflect Free Edition, which has already been suggested, can still perform this operation. In principle, it is in English, so you need to understand the instructions in English.
Hello,
Absolutely, but Laurent must not overlook the discrepancy in size displayed which is symptomatic of the malfunction.
I am not familiar with HD Clone either, I only suggested the hypothesis of limitations in the free version.
As for Macrium Reflect, and aside from a misconfiguration error, error 9 indicates a number of software or hardware issues, more likely related to the source disk, and in this case, we can try to clone whatever we want with whatever we want, which will always lead to the same lack of result unless corrected:
https://10scopes.com/fix-macrium-reflect-error-9/
I suggested in <1> the responsibility of a HD Clone function that would "artificially" extend the size of the target partition so that it is exactly the same as the source partition by manipulating the sector size, but formally, I don't know.
We can possibly look for which Windows command provides the correct/incorrect result (DIR, fsutil, wmi...).
Hello
No functioning anomaly for me either, at least for now.
I cloned a 1GB hard drive, but where did the extra 1GB go?
In all the tutorials, the "extend volume" button in Windows is meant to extend the size of the partition on the unallocated bytes, not the volume which designates a virtual disk that can be smaller or larger than a physical disk.
The image clearly shows the C partition already extended to all the unallocated space and formatted in NTFS. No terabytes lost; the entire new disk is there. The bytes are then recorded within it.
There is a small difference between "partition" and "volume".
Before, volume C occupied the partition C of the same size. Ouch, they have the same name.
The new partition C is larger.
There are several hdclones.
In particular, the free one that exactly reproduces the entirety of the source disk onto the larger disk byte by byte. It removes nothing, adds nothing, and especially does not modify anything. The bytes thus recorded are the same as on the old PC; there is a virtual volume named C that is identical at 930.66 GB, defined and written before cloning with the same values for size, free byte, or file as on the old disk.
It remains to be seen; I don't have the answer because I haven't done it on the PC in question, so I don't know what happens next.
How will Windows figure it out or bug out later?
The choice of this software byte by byte is perfect for copying a data disk, but for this particular case, I don't know. There was (Ouch again) a Windows on the old disk that apparently didn't have enough space on its hard drive, with 2% free, to function properly.
