Why did the SSD disk controller lock into read-only mode?

Question

Solid State Drives

I have a Crucial RealSSD C300 CTFDDAA256MAG-1G1 SSD drive with a Marvell 88SS9174-BJP2 controller
One day, the drive went into read-only mode. All searches did not lead to absolutely nothing.
The firmware of this device is 0006, the "new" firmware 0007 is not sewn. The disk is absolutely completely and without errors read by means of acronis for example, but does not allow writing. Accordingly, it is not possible to operate the disk.
It looks like the controller has gone into read-only mode.
The board has something similar to J-TAG.
I understand the issue poorly, and there are no specialists in our city, but it's a pity to throw out the disk.
Maybe someone who understands will tell you how to reset the controller or direct it to specialized sites.
Photo of the board and contact group similar to j-tag.
habrastorage.org/files/eef/074/dc7/eef074dc7f84402...
habrastorage.org/files/ac6/3a9/238/ac63a9238e694a1...

Answer 1

Maybe he has built-in protection, which works after a certain amount of reading / writing. So that the disk does not become completely inoperative.

Answer 2

There are many memory cells and it is unlikely that their cycles are all uniform. And because of 1 sector, it would probably be too much to block the entire disk.
Perhaps an error in the firmware itself (appearing under certain conditions). Perhaps the problem is related to smart, tk. smart disk does not give.
Perhaps the whole point is where the service information is stored, perhaps it was stored on the disk and was suddenly damaged.

Answer 3

If I'm not mistaken, then any SSD has spare memory blocks that are substituted for the burnt blocks. You can look at disk sizes, typical sizes are 60 GB (+ 4 GB reserve), 120 GB (+ 8 GB reserve) and so on.
Memory blocks fail when writing to them.
The probability of block failure is high, and therefore the size of the reserve is large.
But it can still end.
What would the SSD drive designer do in this case?
I would lock the write to keep the information on disk.
It seems to me that this happened, this is the most reasonable way out.
SSD drives are not recommended to be defragmented, and it is not recommended to place a swap file (paging file) on them. In general, the less written on him, the longer he will live.