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. Count of "unstable" sectors (waiting to be remapped, because of unrecoverable read errors). ID Cur Wor Thr RawValues(6) Attribute NameīB _98 _00000002 Reported Uncorrectable Errorsį0 100 253 _0 3E05000027C0 Head Flying HoursĬurrent Pending Sector Count. Contrôleur des espaces de stockage Microsoft I recently had a alert in Crystal disk with one of my HDDĬan someone can check if i need to back up my files please?ĬrystalDiskInfo 6.7.3 (C) 2008-2016 hiyohiyo
0 kommentar(er)
