Read errors while attempting to clone healthy SSD

[varwwwhtml]

This is my first post. Hello to all of you. I've been a fan of the YouTube channel for a while and have last night come up against a weird problem. But before I launch in to it, I wanted to say hey, and to apologize ahead of time if my post accidentally breaks some obscure forum rule, or if it doesn't include enough information.

 

I am trying to clone a 120gb SSD to a brand new 240gb of the same make and model (both are Kingston A400). BUT both Macrium Reflect and Clonezilla fail in the process due to errors reading the source drive. The idea was to clone to a larger drive so that I could format and repurpose the 120gb for a different project.

 

The thing is, this 120gb SSD is relatively young, has never exhibited any issues, and also passes chkdsk /r /f fine. And the chkdsk logs make no mention of any irreparable issues with the drive.

 

Macrium insists "Clone Failed - Error 9", and Clonezilla doesn't really give an error code, it just quits out. I have attempted to clone Macrium Reflect's "ignore bad sectors" option ticked, but this just results in the same error code at around the same point in the process. Googling for solutions for Macrium's "error 9" all say to run chkdsk to make sure the drive is healthy, but the drive is apparently as healthy as can be. 

 

Are there any heavier duty tools to scan/repair a drive that I can try to use on an SSD. If not, what are my options here?

[Lordclouds]

3 minutes ago, wONKEyeYEs said:

I have a canned response for all such situations...

Fresh OS install.

You're welcome.

When you install windows it creates a special key for your hardware so if you change anything , you will need to reinstall windows.

[Lordclouds]

8 minutes ago, wONKEyeYEs said:

Wha?

I have changed various hardware before and never have I ever had to reinstall Windows as a result.

Except, obviously, when I change the boot drive.

Is because is the boot drive that keeps that info

[Lordclouds]

10 minutes ago, wONKEyeYEs said:

Thank you Captian Obvious.

I don't wanna write the long answer lol

[varwwwhtml]

57 minutes ago, Lordclouds said:

When you install windows it creates a special key for your hardware so if you change anything , you will need to reinstall windows.

Wait. I would like to get this straight because I've built a lot of computers, but after years of just buying them/using Macs (save your opinions please), I am only recently getting back in to building in the last few months. The last Windows drive I cloned was a Windows XP one. So please forgive my ignorance here, but are you saying that there is no way to clone a Windows 10 drive's contents and structure to another, and then successfully boot to that new drive? And that this is a possible cause of these clone failures? Because wow, that would be an incredibly bad choice on their part, if so. And it's also weird that in all of my frantic Google-ing about this problem, that nothing like this was mentioned by anyone.

[Lordclouds]

3 minutes ago, varwwwhtml said:

Wait. I would like to get this straight because I've built a lot of computers, but after years of just buying them/using Macs (save your opinions please), I am only recently getting back in to building in the last few months. The last Windows drive I cloned was a Windows XP one. So please forgive my ignorance here, but are you saying that there is no way to clone a Windows 10 drive's contents and structure to another, and then successfully boot to that new drive? And that this is a possible cause of these clone failures? Because wow, that would be an incredibly bad choice on their part, if so. And it's also weird that in all of my frantic Google-ing about this problem, that nothing like this was mentioned by anyone.

with the recent updates and the complexity of new drivers changing one SSD info to another is simply complicated and not recommended. A fresh install will always be necessary.

[Lordclouds]

Just now, Lordclouds said:

with the recent updates and the complexity of new drivers changing one SSD info to another is simply complicated and not recommended. A fresh install will always be necessary.

I was writing it down in a simple way to understand sorry if I wasn't clear

[varwwwhtml]

3 minutes ago, Lordclouds said:

I was writing it down in a simple way to understand sorry if I wasn't clear

No no, I just wanted to make sure I was understanding correctly. 

 

Seeing as how nothing I try is working, looks like I am running out of options anyway. So I will consider a plan of attack of just installing Windows 10 on the new drive, and recovering my files and settings from the old one.

 

Thanks, all.

[Lordclouds]

1 hour ago, varwwwhtml said:

No no, I just wanted to make sure I was understanding correctly. 

 

Seeing as how nothing I try is working, looks like I am running out of options anyway. So I will consider a plan of attack of just installing Windows 10 on the new drive, and recovering my files and settings from the old one.

 

Thanks, all.

Np make sure to format just in case.

[Pickles von Brine]

4 hours ago, varwwwhtml said:

No no, I just wanted to make sure I was understanding correctly. 

 

Seeing as how nothing I try is working, looks like I am running out of options anyway. So I will consider a plan of attack of just installing Windows 10 on the new drive, and recovering my files and settings from the old one.

 

Thanks, all.

At this point that may be the best option.