Healthy SSD locked in Read-Only, not responding to ATA Secure Erase

Understanding a Healthy SSD Locked in Read-Only Mode and Its Unresponsive ATA Secure Erase

In the realm of data storage, Solid State Drives (SSDs) have become a staple due to their speed and reliability. However, even healthy drives can occasionally encounter perplexing states, such as becoming locked in a read-only mode, rendering them inaccessible for writing operations. Recently, a user shared their experience with a PNY CS900 480GB SATA SSD that, despite being in excellent health, was locked in a read-only state and would not respond to ATA Secure Erase commands. This situation highlights some intriguing aspects of SSD behavior and offers insights into potential recovery methods.

The Scenario

The user, who had been utilizing a PNY CS900 SSD as a Windows boot drive since 2018, encountered system instability manifested as a Blue Screen of Death (BSOD). Following troubleshooting, it was observed that the SSD was operating in a locked, read-only mode at the microcontroller level. Notably:

  • Read and access of files remained possible: The drive could still be read from, indicating the fundamental health of the media.
  • Write operations were blocked: No new data could be written, and the drive was effectively in a protected state.
  • Drive health was excellent: S.M.A.R.T. data indicated a health score of 92%, with no bad sectors or visible signs of failure.
  • Attempted remediation: The user tried issuing ATA Secure Erase commands through various means—PNY’s proprietary software, Linux tools, and paid OS utilities—but the drive did not respond.

Key Clarifications

  • Connection method matters: All commands were executed while the SSD was connected directly via SATA to the motherboard. Attempts to use USB-to-SATA adapters were unsuccessful, likely because ATA command signals do not transfer correctly over such converters.
  • Drive not in hardware read-only mode: Both OS-level checks and property inspections confirmed the drive was not set to read-only mode at the OS level. The lock was intrinsic, at the microcontroller level.

The Conundrum

Typically, SSDs may lock themselves in a read-only state at the end of their lifespan or upon encountering severe hardware issues to prevent data corruption. Such lockouts are often associated with:

  • Worn-out cells or sectors
  • Detection of hardware failures
  • Protection mechanisms triggered by power surges or hardware anomalies

However, in this case, the drive remained physically

Share this content:

Leave a Reply

Your email address will not be published. Required fields are marked *