BarkingGhostar
Diamond Member
My normal boot drive is a Samsung EVO 840 120GB SSD. I will call this one sSSD, for Source SSD. My backup SSD, which is a Samsung EVO 850 120GB. I will call this one tSSD, for Target SSD.
Every 2-4 weeks I use the Samsung Secure Erase s/w to wipe the tSSD and then boot sSSD, Launch Samsung Data Migration and migrate away (a la cloning). This has worked beautifully for me on my PC and my wife's at home work PC (all identical components).
This morning I decided to wipe & clone again, but this time the Samsung Data Migration s/w failed. At the end of the migration process I get:
If the system of the original disk has some problems or bad sectors, it may not be duplicated. {OK}
This is followed by:
Cloning Failed
400180[061b34] {OK}
I repeated my proceed of wiping the tSSD and trying again, but got the same results. I ran Error-Checking in Windows 7 Professional (SP1 & all critical updates, including .netties) which required a reboot but nothing bad, sectors or otherwise, were found.
Tried the cloning process again and got the same results. Mind you after each failed cloning the tSSD is erased by the s/w. So, at this point I went through Disk Management and initialized the disk GPT and added a full NTFS volume. Ran Error-Checking on it and not bad there.
Tried one more time and again got a failure and this time I gave up with the Samsung s/w. I switched to Macrium Reflect and it worked on the first try. I'm booted onto the tSSD right now so I know it isn't hardware.
Ideas, thoughts or suggestions?
Every 2-4 weeks I use the Samsung Secure Erase s/w to wipe the tSSD and then boot sSSD, Launch Samsung Data Migration and migrate away (a la cloning). This has worked beautifully for me on my PC and my wife's at home work PC (all identical components).
This morning I decided to wipe & clone again, but this time the Samsung Data Migration s/w failed. At the end of the migration process I get:
If the system of the original disk has some problems or bad sectors, it may not be duplicated. {OK}
This is followed by:
Cloning Failed
400180[061b34] {OK}
I repeated my proceed of wiping the tSSD and trying again, but got the same results. I ran Error-Checking in Windows 7 Professional (SP1 & all critical updates, including .netties) which required a reboot but nothing bad, sectors or otherwise, were found.
Tried the cloning process again and got the same results. Mind you after each failed cloning the tSSD is erased by the s/w. So, at this point I went through Disk Management and initialized the disk GPT and added a full NTFS volume. Ran Error-Checking on it and not bad there.
Tried one more time and again got a failure and this time I gave up with the Samsung s/w. I switched to Macrium Reflect and it worked on the first try. I'm booted onto the tSSD right now so I know it isn't hardware.
Ideas, thoughts or suggestions?
