Why does an SSD go into safe mode "SATAFIRM S11" every half a year?

Question

Iron

For the 3rd time (about once every half a year) the ssd "Apacer AST220" suddenly goes into safe mode "SATAFIRM S11", it is not possible to recover with the data, only by flashing with formatting. This disk is used for a computer system that is used for a browser, kints and other little things, but it's still not pleasant to lose some data. Why can this happen and what other recovery options are there besides repairs11.exe just to get it out of safe mode?

Answer 1

Conventionally, flash memory during production can be divided into 3 categories: the first is the best, with a minimum number of errors (used, for example, in almost all SSDs from Samsung, Intel, Crucial, Plextor and other high-quality brands - that's why they are so expensive. Moreover, that Intel has created a sub-brand ADATA for itself - and under it it releases ssd from its rejection so as not to spoil its brand). Well, the type of memory also directly affects reliability - relatively reliable expensive SLC, MLC or cheap slag TLC-QLC. The second one is average in quality, and the third one is full [email protected]#&%. Apacer is exactly that. Given that such memory has a very high frequency of new bad blocks, and the firmware is stored on memory chips, it is regularly damaged when new bad blocks appear. First, the replacement comes from the spare area, and then from the main volume. That is why the most powerful ssds have a volume of not 128GB, but 120 (240, not 256, 480, not 512, etc.) - there are so many bads right from the factory that the manufacturer has to cut the volume and increase the reserve area so that the ssd does not immediately fall into "SMART status bad" when it is exhausted. Errors in the firmware itself can also lead to falling out in safe - an option to update the firmware, if any. But in general, the option to buy ssd of normal brands, which is also not a guarantee against data loss, but reduces its likelihood. All sorts of noname Chinese brands can use bunandas, it comes down to picking out emmc and ufs chips from broken phones and shoveling SSDs based on them. ) - there are so many bads right from the factory that the manufacturer has to cut the volume and increase the reserve area so that the ssd does not immediately fall into "SMART status bad" when it is exhausted. Errors in the firmware itself can also lead to falling out in safe - an option to update the firmware, if any. But in general, the option to buy ssd of normal brands, which is also not a guarantee against data loss, but reduces its likelihood. All sorts of noname Chinese brands can use bunandas, it comes down to picking out emmc and ufs chips from broken phones and shoveling SSDs based on them. ) - there are so many bads right from the factory that the manufacturer has to cut the volume and increase the reserve area so that the ssd does not immediately fall into "SMART status bad" when it is exhausted. Errors in the firmware itself can also lead to falling out in safe - an option to update the firmware, if any. But in general, the option to buy ssd of normal brands, which is also not a guarantee against data loss, but reduces its likelihood. All sorts of noname Chinese brands can use bunandas, it comes down to picking out emmc and ufs chips from broken phones and shoveling SSDs based on them. - an option to update the firmware, if any. But in general, the option to buy ssd of normal brands, which is also not a guarantee against data loss, but reduces its likelihood. All sorts of noname Chinese brands can use bunandas, it comes down to picking out emmc and ufs chips from broken phones and shoveling SSDs based on them. - an option to update the firmware, if any. But in general, the option to buy ssd of normal brands, which is also not a guarantee against data loss, but reduces its likelihood. All sorts of noname Chinese brands can use bunandas, it comes down to picking out emmc and ufs chips from broken phones and shoveling SSDs based on them.

Answer 2

most likely the problem in the disk
may be in the sata wire ...