(0xBB), Reported Uncorrect (a.k.a. UNC) (used only by some vendors): the count of read errors that could not be recovered automatically. SMART ID (0xC6) Uncorrectable Pending Sector Count is an important S.M.A.R.T parameter, which indicates many uncorrectable errors when reading/writing a. The Errors. The five key SMART errors Backblaze tracks are the following: SMART 5: Reallocated sectors count SMART Reported uncorrectable.
Your place: Smart 187 reported uncorrectable error
|Streamer.inc209 error 017 undefined symbol funcidx|
|49 4c18 error laserjet p3005|
|Smart 187 reported uncorrectable error|
watch the videoUnhandled Exception Has Occurred in Your Application. If You Click Continue The Application
I believe HD Tune does similar - that way you don't have to do anything to see it.
Raw read error count generally relates to hdd but can be seen on ssd. As this doesn't apply to ssd
RAW Read Error Rate, a SMART disk error, indicates problems with the disk surface (platter that stores the data), the actuator arm, and the read/write head.
Click to expand
RAW Read Error Rate on an SSD is an indication that there are some bad connections between disk and the drive controller or the problem is within the SSD. Hence, the SSD may fail after a period of time.
Click to smart 187 reported uncorrectable error what i can tell the threshold for that score on HDTune is 6
if that score is Raw read error rate, this is what it says in the Kingston ssd manual I linked above
Raw error rate relative to the number of sectors read this power cycle. For the SF, this attribute includes both
Uncorrectable ECC (UECC) errors, smart 187 reported uncorrectable error, and Uncorrectable RAISE (URAISE)errors.
Normalized Equation: 10log10[BitsRead/(ReadErrors + 1)]
SectorsRead= Number of json error unexpected token & read
Normalized Value Range:
Worst = 38
 : Number of sectors read this power cycle
: Read errors (UECC+URAISE)
So its auditd error setting audit stat score between &
its not very clear
I have another drive of the exact same model, age and usage and this other drive has "0" in the "Number of Reported Uncorrectable Errors" value.
At this point I just replaced this drive and will try an RMA, since I cannot trust it anymore.
And it is really strange. I just detected this problem because of the BTRFS checksum feature. Otherwise I would just be getting corrupted files without any notification from the drive. I would just consider bit rot and I would never suspect the drive if the "Number of Reported Uncorrectable Errors" statistics would not keep increasing