- Code: Select all
8/22/2019 1:21:07 AM,#197 Current Pending Sector Count 1 -> 0
8/22/2019 1:16:03 AM,#197 Current Pending Sector Count 0 -> 1
After that, the drive had 2 more events of Pending Sector going to 1 and then back to 0:
- Code: Select all
8/27/2019 7:59:30 PM,#197 Current Pending Sector Count 1 -> 0
8/27/2019 7:54:25 PM,#197 Current Pending Sector Count 0 -> 1
8/24/2019 10:53:10 PM,#197 Current Pending Sector Count 1 -> 0
8/24/2019 10:48:06 PM,#197 Current Pending Sector Count 0 -> 1
After some googling, I learned that this is a weird quirk that plagues basically every MX500 SSD from Crucial: https://utcc.utoronto.ca/~cks/space/blog/tech/SMARTAlarmingFlakyErrors
Some people say that this is a firmware bug that unfortunately hasn't been fixed to this day.
If I had known this before I would probably have thought twice before purchasing this drive. But I got it for a really good price and this behavior doesn't seem to affect performance or data integrity or system stability in any way. Plus the drive comes with 5 years of warranty. So I decided not to return it, do regular backups and hope that someday Crucial will finally release a firmware that fixes this.
I was wondering if it's possible to configure Hard Disk Sentinel in a way so that it would ignore #197 Pending Sector Count attribute and wouldn't change the reported health percentage because of it and only keep saving the changes to the log and showing in the corresponding tab? Because the current situation doesn't seem to reflect the real condition:
Especially after I was experimenting with the program settings and the reported drive health has dropped to 50% when I tried to select "Analyse vendor-specific values" as health calculation method in Advanced Options:
Afterward, I switched back to the recommended method of health calculation but the health graph hasn't changed.
So, my question is: Is there a way to clear only the Health graph without losing other stats? And prevent the Health graph from changing in the future due to the Pending Sector going to 1 and then back to 0?
For now, I just set an offset of -1 for it, but I'm not sure how it will affect the Health graph and whether the changes still will be logged because I still would like to be able to read the log and see when exactly false pendings occurred.