However, some drives will not immediately remap such sectors when written instead the drive will first attempt to write to the problem sector and if the write operation is successful then the sector will be marked good (in this case, the “Reallocation Event Count” (0xC4) will not be increased). Read errors on a sector will not remap the sector immediately (since the correct value cannot be read and so the value to remap is not known, and also it might become readable later) instead, the drive firmware remembers that the sector needs to be remapped, and will remap it the next time it’s written. If an unstable sector is subsequently read successfully, the sector is remapped and this value is decreased. But what does this mean? I turned to the SMART page at Wikipedia to learn the following (all text copied verbatim):Ĭurrent Pending Sector Count: Count of “unstable” sectors (waiting to be remapped, because of unrecoverable read errors). First was Current Pending Sector Count and and second, Uncorrectable Sector Count (both at 200). In fact, those numbers matched for two items.

I saw the amber flags on two specific SMART values for the drive. Investigating errors in amber shows me this drive may have serious problems! Why a Hard Disk Warning Prompts Win10 Tool Search

Crystaldiskinfo caution