![]() Unfortunately it seems the usage of these fields isn't consistent from one manufacturer to the next and so there is no universal method of interpreting them. Did those attributes reach an internal limit of some kind, or is it really just coincidence that they all happen to be 200? It seems odd to me that so many of the fields have "Current" and "Worst" values of 200. "Current Pending Sector Count" and "Uncorrectable Sector Count" are set to "1 01h" in the Settings window but 0 in the main window. Why do my threshold settings in the second screenshot not match what is shown in the main window? For example "Reallocated Sector Count" is set to "1 01h" in the "Health Status Setting - Threshold of Caution (Raw Values)" but is listed as "140" in the main window. 197 0xC5: Current Pending Sector Count: Count of 'unstable' sectors (waiting to be remapped, because of unrecoverable read errors). Both successful and unsuccessful attempts are counted. I would set it to some value slightly higher than the current value. The raw value of this attribute shows the total count of attempts to transfer data from reallocated sectors to a spare area. What is the relationship between "Current", "Worst", and "Raw Values"? How can "Raw Values" be 0 but "Current" and "Worst" both be 200, as is the case with "Read Error Rate"? 'Reallocated Sector Counts' are one of 3 sector counts that the user can set the 'Threshold of Caution' for. Now, I dont think that would cause it be slow, but it could be the case. Related to my questions are the settings in the "Health Status Setting - Threshold of Caution (Raw Values)": reallocated sectors count your disk needs to be replaced backup immediately and get a replacement. I'm having trouble undestanding the various statistics displayed in the main CrystalDiskInfo window (version 8.3.1): ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |