SSD unrecognized after failed clone, can't Initialize it

[carciofoapropulsione]

I got a new WD Blue 3D NAND SATA SSD 1TB M.2. I've put it in an enclosure to connect it through USB.
At this point the drive was recognized in my Windows 10 Disk Manager and I initialized it without creating a partition.
At this point I tried cloning the contents of my current SSD onto it through the program Macrium Reflect but it gave me "Error 21- Clone Failed, Unable to Match Partition".

At this point the SSD was no longer initialized and it shows to be of size 0 GB in DiskPart and impossible to initialize through Disk Manager "due to a fatal hardware error", this is the same thing I get if I try to perform any action on it through diskpart...

I've also tried to use WD's LifeGuard tool, which passed the quick and extended tests but failed the Erase test with "Delete Partition Error"

Is there any way to understand what happened to this drive? I tried plugging it in other ports but I get the same errors...

 

[Ralston18]

My thought is that you simply may have gotten things out of order or missed a step.

Easy to do when setting up a new drive and maybe more so if multiple drives are being used.

Start figuring out what happened via the following link:

https://support.wdc.com/product.aspx?ID=1803

Write down, as best you can remember, what you did.

Then compare that to the link provided above.

Very likely you will spot the error, mistake, misconfiguration etc. and then know how to resolve it to get the SSD recognized and useable.

Plus some WD person monitoring Tom's Hardware may offer additional advice and suggestions.

Key is identifying where the process went astray and where to begin the "do-over".

 

[carciofoapropulsione]

I went and found the Macrium Reflect log if it may be of help:

Clone ID - EF9BCAE80446632C

--------------------------------------------------------------------------------
Dismounting drives


--------------------------------------------------------------------------------
Starting Clone - 11 April 2018 14:28


--------------------------------------------------------------------------------
Creating volume snapshots
Volume Snapshots Created
C:\ \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2
D:\ \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3


--------------------------------------------------------------------------------
Source Disk: GPT Disk 1 [D6FA4B8C-8DB4-455D-A0DF-5F1F318E11CC] - SanDisk SD7SN6S-256G-1006 X3511006 <238.47 GB>
Geometry: 31130\63\512
Destination Disk: GPT Disk 3 [07D5F337-1ACA-4509-BD9B-72A6868D2C52] - JMicron Generic 0508 <931.51 GB>

Clone Type: Intelligent sector copy
Verify: Y
Delta: N
SSD Trim: Y


--------------------------------------------------------------------------------
Operation 1 of 5
Copy Partition: 1 - SYSTEM
FAT32 (LBA) 67.0 MB / 260.0 MB
Destination:
Start Sector: 2,048
End Sector: 534,527
Partition Type: Primary


--------------------------------------------------------------------------------
Checking file system
Gathering Windows Events


--------------------------------------------------------------------------------
Clone failed - Unable to match partition - Drive 2, Start Sector 477024256 Cluster Run Error. Cluster run short - Error code = 21. Please run 'chkdsk : /r'

 

[Ralston18]

The source drive you wish to clone is a San Disk SSD (256 GB).

The destination drive is your new WD Blue 3D NAND SATA SSD 1TB M.2.

Why the USB enclosure versus just directly installing the M.2?

Not sure about that "FAT32" partition....

Read the following link from within this Forum:

http://www.tomshardware.com/forum/id-3674844/finally-cloned-sata-ssd-ssd.html

Overall, the following link, again within this forum, is most likely to create a successful clone.

http://www.tomshardware.com/answers/id-3526539/cloning-external-hard-drive.html

 

[carciofoapropulsione]

The source drive you wish to clone is a San Disk SSD (256 GB).

The destination drive is your new WD Blue 3D NAND SATA SSD 1TB M.2.

Why the USB enclosure versus just directly installing the M.2?

Not sure about that "FAT32" partition....

Read the following link from within this Forum:

http://www.tomshardware.com/forum/id-3674844/finally-cloned-sata-ssd-ssd.html

Overall, the following link, again within this forum, is most likely to create a successful clone.

http://www.tomshardware.com/answers/id-3526539/cloning-external-hard-drive.html

The problem sadly is not the cloning, it's that I can't initialize, format or do anything to the new SSD now, and I can't tell why... Honestly if I thought this could happen I would've just done a clean installation

Update: Tried the "clean all" (or creating partitions) in DiskPart, gave a "failed due to a fatal hardware device error"...

 

[Ralston18]

Try running WD's diagnostic software on the M.2

Try a direct connection somewhere versus the enclosure.

What must be discovered is if the problem is the computer, the enclosure, or the new SSD/M.2 itself.

The M.2 could well be defective itself.

 

[carciofoapropulsione]

Try running WD's diagnostic software on the M.2

Try a direct connection somewhere versus the enclosure.

What must be discovered is if the problem is the computer, the enclosure, or the new SSD/M.2 itself.

The M.2 could well be defective itself.

Thank you for all the help but in the end I decided to RMA it back to amazon, will be more careful and use WD's official software next time I try something like this... I'm not sure how exactly the thread should end as there was no "solution"...

Have a nice day