spinning HD > SSD clone super slow, /w errors

for many years already, i clone my system drive every few months to another HD and keep it as a backup. if/when the system gets corrupted, i just swap drives and copy the latest data to the clone.

for cloning i use USB-booting paragon Hard Disk Manager, and the HD raw copy option.

so i did just reach out for my clone and booted. all is good.

but when i tried to make a new clone, spinning HD to SSD, the copy takes 10 hours instead the usual 3. and when i tested the new clone, on first boot it first runs chkdsk and finds a ton of errors (none on the source). it boots, but windows is corrupt on it - so obviously the cloning didn't succeed.

what could be the problem? has my SSD gone south? or - should i erase/empty it before cloning onto it?

i'm on a win7 laptop, the spinning drive is Hitachi 1Tb, the SSD a samsung evo 850.

Try to use Macrium Software | Macrium Reflect Free
If your SSD is smaller than 1T, you must resize the C partition to fit.

How old is your hard drive? Maybe it is going bad.

As I know, trim is only for SSD's.
- TRIM
Type this cmd
fsutil behavior query DisableDeleteNotify

It will give you one of two results, either a 0 or a 1. A zero indicates that TRIM is enabled correctly, a one means that it is not. If you have a TRIM-compatible SSD, but find that Windows 7 hasn't enabled the command, you can easily do so by running this command:

fsutil behavior set DisableDeleteNotify 0

It is possible that your hard drive is bad; but it isn't very old, so that's not likely.

My computer is always on, and my drive is holding up just fine. I have always operated that way, and it hasn't appeared to put any additional wear on my hard drives.

Like Megahertz said above, use Macrium Reflect Free to do the backup. And try doing an image backup rather than a clone backup. I recently used Macrium Reflect Free to do an image backup of a 750 GB hard drive, and I then restored the image to a 120 GB SSD. It worked without any problems. I then set up TRIM on the SSD, and I was good to go. The SSD became my C: drive (my primary Windows drive), and it's been working fine for several months now.

Boot from Win 7 installation disk, go to repair and launch a CMD window.
Type
chkdsk c: /f

Pay attention on the results, specially for bad clusters or bad blocks.

Megahertz07 said:

As I know, trim is only for SSD's.
- TRIM
Type this cmd
fsutil behavior query DisableDeleteNotify

It will give you one of two results, either a 0 or a 1. A zero indicates that TRIM is enabled correctly...
fsutil behavior set DisableDeleteNotify 0

yes, of course trim is only SSD. how the system knows what kind of drive, i'm not sure.

Trim is enabled, but it doesn't really apply in my situation, as it does its thing on deleted sectors on system idle time as determined by the OS. during a clone, each and every sector gets written to, and there is no idle time.

delete all contents, then forcetrim would work, if only the utility worked on a big partition.

another thought - what if i delete the partition, not its contents? what does the SSD do then, internally? i assume it still needs the deleted sectors "trimmed."

but yes, on the first clone onto the SSD there was no problem as its sectors are, off the shelf, "trimmed."

zdoe said:

what if i delete the partition, not its contents?

If you delete the partition, the contents are deleted with it. And once you delete it, it's gone forever.

If you want to delete a partition without deleting the contents, the only way to do that is to back it up first, then delete the partition, then recreate the partition, then restore the backup to the new partition.

well, my wording was funky.

but yes i WANT the drive to be in its virgin state. zero data on it.