8
My understanding is that Reallocated_Sector_Ct
gives the absolute number of remapped sectors while Reallocated_Event_Count
gives the number of tries to initiate such a remapping. How could it then by that a disk has a Reallocated_Sector_Ct
of 0 but thousands of Reallocated_Event_Count
such as this Seagate ST9500420AS:
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
196 Reallocated_Event_Count 0x000f 087 087 030 Pre-fail Always - 11481 (35561 0)
I seriously doubt that there were 11481 unsuccessful attempts to map sectors on this drive. If I would have to guess then I would say that the interpretation of these values on the interwebs does not reflect what the vendors' or at least Seagate's engineers implemented :) Is there a better explanation?
Interesting! I once had a hard drive whose
Reallocated_Event_Count
suddenly started going up whileReallocated_Sector_Ct
stayed at0
. This was a laptop, I can't be 100% sure but I think it was a Seagate drive too. I agree with you -- it seems unlikely that all attempts to reallocate would fail. I betReallocated_Sector_Ct
is just not implemented in this drive or Seagate are using SMART attributes in some proprietary way. – misha256 – 2017-03-20T01:37:16.073From my observations with several damaged Seagate drives
Reallocated_Event_Count
may also rise while reading damaged sectors. Reallocating at least under linux doesn't occur while reading, it occurs only when writing and thenReallocated_Sector_Ct
rises, if there's still space in spare area. But I may be completely wrong. – Michal Sokolowski – 2017-04-12T18:24:15.247