External SSD no longer working

[Almost Tech Whiz]

The other day I plugged in my external SSD (Micron M600 1TB) and moved some files over, before pulling it out (not safely ejecting). When I plugged it back in a little while later, Windows told me I had to reformat. Not having anything important on the drive, I attempted it, thinking that would fix it, however it did not format the drive.
So I tried EaseUs Partition manager to try and wipe the drive, and convert it from MBR to GPT, but everything I tried just failed.
I tested the SSD in another external enclosure, and the same thing happened.
The next thing I did was to run a chkdsk, however the drive showed up as RAW file type and thus would not work.
So I moved on to using Diskpart to see if I could delete all partitions, format, clean, etc.. but nothing worked. With everything I tried just throwing a data cyclic redundancy check error.
After this I moved on to using GParted to try and overwrite the partition table, as I thought this may be the issue, but only got an I/O on write error whenever I tried to do anything through GParted.
After this I booted into linux and ran dd on it to a) clear the partition table and b) overwrite the drive. This did not throw any errors, but also seemed to do nothing to fix the drive.

Now today when I plugged the drive in it is showing up as exFat again, but I am still getting all of the same errors.

I have no idea what to do, or if the SSD is simply dead.

Thanks

 

[JaredDM]

It's most likely a hardware failure. If the drive has no LBA access it'll appear as RAW to the system because all it is really seeing is the USB bridge chip. If it's under warranty and the data isn't important, I'd recommend you RMA it. (After you rule out stupid simple stuff like bad USB cable, etc.)

 

[Almost Tech Whiz]

UPDATE: I pulled the SSD out of the external enclosure and plugged it directly into my computer and now I no longer get data cyclic redundancy, however I keep getting a write protected error. I have removed write protection from the drive, yet this issue still persists.
It may be worth noting that this is a self encrypting drive (I'll be honest, I had never hear of such a thing before, and not sure how they work entirely)

 

[Almost Tech Whiz]

I still need help with this if anyone has any suggestions...