WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2024 Poal.co

1.2K

An SSD I have goes into read-only mode from time to time. After a few weeks of uptime, it will lock up the system and upon restarting everything is fine. The last time this happened it wasn't recognized by the BIOS, so I thought it was toast, but then came back to life and appears to be working as before.

SMART data appear to be fine except a few hardware errors recorded months ago that haven't increased since.

My first thought was to buy another SSD, then read that even hardware manufacturers suggest that this can happen from time to time and shouldn't be a reason for another drive.

What are your thoughts on this? My guess is that it's possibly a firmware issue.

An SSD I have goes into read-only mode from time to time. After a few weeks of uptime, it will lock up the system and upon restarting everything is fine. The last time this happened it wasn't recognized by the BIOS, so I thought it was toast, but then came back to life and appears to be working as before. SMART data appear to be fine except a few hardware errors recorded months ago that haven't increased since. My first thought was to buy another SSD, then read that even hardware manufacturers suggest that this can happen from time to time and shouldn't be a reason for another drive. What are your thoughts on this? My guess is that it's possibly a firmware issue.

(post is archived)

[–] 1 pt

Likely the drive itself (or rather the controller on the drive), but it might be your motherboard or chipset drivers.

Is there newer firmware available for that SSD?

[–] 0 pt (edited )

The SSD is a few years old and and I don't think there has been any newer firmware. But I wonder whether not running TRIM taxes the controller.

[–] 0 pt

Time for a new drive. Solid state memory is not up to the longevity of mechanical drives yet. I have perfectly healthy HDDs that are 10 and 12 years old. A solid state drive is junk after five years of regular use.

[–] 0 pt

Why did you disable TRIM anyway?

[–] 0 pt

It was supposed to be this way by default for FDE.

[–] 1 pt

I had the same issue several months back, the issue was actually not the drive itself but the SATA hardware on the other end failing, it ended up damaging most of the files on the drive before I tracked it down.

[–] 1 pt

Wouldn't this affect the other (non-SSD) drive as well?

[–] 1 pt

It affected all the drives but the one in the first slot, which is why it took a long time to figure out, and I was only running 3 drives at the time one of which (the non SSD) rarely got used

CrystalDiskInfo can tell you how much data has been written to the drive, and then you can check the manufacturer specifications to see if the drive is past it's lifetime.

If the drive is...

  • smaller than 1tb and
  • you write a lot of data to it
  • several years old

you've likely worn the drive out. This obviously heavily depends on how often you write data to the drive.