New
#11
Well, the first time was imaging a 250 GB hard drive and putting that image into a 1 TB one. For my 1 TB to 500 GB deal, I thought if the data was small enough (the 1 TB only has around 245 GB used), I would be able to restore the image on the 500 GB hard drive. Is that not the case?
As for the 12 GB, yeah, it always was, and it has around 11 GB used for something. I never needed it though.
Indeed it's not unpartitioned at all (I read it wrong!) . It's a partition to return to "factory install".
You can't install a large disk to a small disk easy with clonezilla. I'll send you a link in 10 minutes how to do it.
After restoring the small image to 1GB disk, you got a lot of unloacted space(?) Did you extend it?
You made an disk image of a large disk. Now you want to restore on small disk..... that's impossible!
After the image to the 1 TB disk, there was unallocated space, and I had to extend it. I don't think I'm copying the entire disk though, just the data that's on it, which is roughly 240 GB of data. According to this link, it's possible with Clonezilla:
How to: Clone a large disk onto a smaller SSD - Overclockers Forums
Edit: Seems that tutorial is saying that I should shrink the drive. Guess I'll do that after the current backup is finished.
In that link: 5) Shrink your existing drive to fit on the SSD
So you had to shrink the partitions BEFORE imaging. So lots of unallocated space at end of physical disk.
clonezilla clones data (not free space) and NOT the unallocate space.
See it as a 1 to 1 copy (except unallocated space).