On 04/01/2024 03:25, Charles Curley wrote:
I decided
instead to boot to a USB stick and run badblocks. The read-only test
took 12 minutes and reported no errors.
I now have a writing test (-w) running. It has reported no failures on
its first pass.
Is badblock writing test useful for SSD taking into account wear
leveling? Each write should be mapped to another physical address. All
errors should be handled by firmware.
To test low-end USB pen drives and SD cards there is the f3 (Fight Flash
Fraud or Fight Fake Flash) tool, however such test should not be
necessary for a SATA SSD.
Have you checked that no firmware update is available for this drive?
I have experienced just a few failures of HDD. It may be irrelevant for
SSD, but in the case of HDD I would replace the disk reporting
Current_Pending_Sector as soon as possible. It seems, repeating reports
from smartd are intentional.
On the other hand the "VALUE" has not decreased and is still 100, and
the attribute is not marked as "pre-fail". Perhaps there is not reason
to worry to much.
I am unsure concerning accounting if an error happens during reading a
file then the file is deleted without overwriting and the address range
is marked unused (trimmed).
