Now I've also reduced the used space to merely 80GB. My current 1TB HDD boots up and functions no problem. Ok then, but it's already done so it doesn't matter.Ģ. The Macrium Reflect program recommended by mcnumpty is also a reliable product should you want to give that program a go.ġ. While it's not our usual d-c program we've found it reliable. The EaseUS Todo program you used is a decent program. Or you simply misused the program - not an uncommon event. Perhaps in formatting the intended SSD destination drive you multi-partitioned it in such a way as to cause of the problem you encountered with the d-c program you used although that ordinarily would not cause the problem you encountered.Ĥ. So what went awry with the d-c operation is impossible to determine at this point.
(We're assuming, of course, that your source drive boots & functions problem-free in the current system, right?)ģ. Since your 480 GB destination drive contains sufficient disk-space to receive the 200 GB of data remaining on your "source" drive (apparently a 1 TB drive?) there would seem to be no impediment re available disk-space to carry out a successful d-c operation. There's no harm in doing so but it is unnecessary.Ģ. First of all there is NO need to format your destination drive, i.e., the recipient of the clone, prior to undertaking the disk-cloning operation.
0 kommentar(er)
