04-16-2018 01:03 PM
Sanitize Drive didn't work, because the Linux it's based on suffers from the same problem as my main installation, namely that it tries
to access disk sectors that are beyond its capacity, which takes almost 5 minutes per sector to get a timeout error back.
Thank you both, HWTech and targetbsp, for your time, I'm going to try to RMA the device. Do you happen to know the product number
I need to enter into the RMA site? It's supposed to be a 5 or 6 digit code on the original packaging which I no longer have ( CT2050MX300SSD1 )
Thanks and have a nice day!
04-16-2018 01:21 PM
Thanks for the update on the situation.
Contact Crucial Support directly by their Live Chat. I've started the RMA process this way a few times.
04-16-2018 01:22 PM
Ah, yeah. That is the bit that's on the packaging!
Crucial customer services for your region (link in my signature) should eb able to supply that. Failing that, forum regular Bogdan can usually magic them up from somewhere when he next visits!
04-17-2018 01:38 AM
The material number that should work is 323595
As for the reported capacity/drive data... if you are going to RMA the drive (that is still covered by a warranty) I wouldn't suggest playing with drive configuration. However, out of curiosity, you coudl probably check (and only check) HPA/DCO information.
I have only read about HPA and DCO and never really had to fix any drive this way. It seems there are some tools that are able to modify this kind of parameters but I am not sure does it work the same way on HDDs and SSDs, maybe it does. You would probably act on your own responsibility.
I think you could safely check/detect the HPA/DCO values without modifying anything. Download OSForensics, go to 'Forensic Imaging' option > 'Disk Hidden Areas HPA/DCO' tab > and click 'Detect HPA/DCA' button.
I wonder what values would you see for 'Max User LBA', 'Max Native LBA' and 'Max DiskLBA'...
04-17-2018 02:02 AM
04-17-2018 02:22 AM
Thanks for an update Good luck with RMA process!