[Discuss] 1 offline uncorrectable sectors detected

[gaf at blu.org (Jerry Feldman)]

I'm double checking this. I actually ran badblocks the other day but did 
not save the output. According to some documentation, and others on the 
web that this repeated warning is always the same sector, and according 
to the articles I saw is that it had been remapped. However, I just ran 
a smartctl assessment, and 198 is showing 0. In the past it showed 1.

[gaf at gaf ~]$ sudo smartctl -A /dev/sdc
smartctl 6.1 2013-03-16 r3800 [x86_64-linux-3.10.7-200.fc19.x86_64] 
(local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE UPDATED  
WHEN_FAILED RAW_VALUE
   1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail 
Always       -       6
   3 Spin_Up_Time            0x0027   178   133   021    Pre-fail 
Always       -       8066
   4 Start_Stop_Count        0x0032   090   090   000    Old_age 
Always       -       10680
   5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail 
Always       -       0
   7 Seek_Error_Rate         0x002e   100   253   000    Old_age 
Always       -       0
   9 Power_On_Hours          0x0032   063   063   000    Old_age 
Always       -       27506
  10 Spin_Retry_Count        0x0032   100   100   000    Old_age 
Always       -       0
  11 Calibration_Retry_Count 0x0032   100   100   000    Old_age 
Always       -       0
  12 Power_Cycle_Count       0x0032   100   100   000    Old_age 
Always       -       120
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age 
Always       -       17
193 Load_Cycle_Count        0x0032   197   197   000    Old_age 
Always       -       10663
194 Temperature_Celsius     0x0022   119   081   000    Old_age 
Always       -       33
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age 
Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age 
Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age 
Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age 
Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age 
Offline      -       0


On 08/20/2013 03:00 PM, Tom Metro wrote:
> Jerry Feldman wrote:
>>>> Offline uncorrectable sectors detected:
>>>>        /dev/sdc [SAT] - 48 Time(s)
>>>>        1 offline uncorrectable sectors detected
>> Certainly. but a minor error like this is not a serious flaw since the
>> sector has already been remapped.
> I believe the error means some operation (self-test or normal usage)
> attempted to read from a sector, it failed, and error correction and the
> usual number of retries was unable to recover.
>
> I don't think the sector has yet been remapped, and that's the whole
> point of this repeated warning. It's telling you that something is still
> pending. Had the sector been remapped, it would increment the
> reallocated sector count and you'd see a warning only once.
>
> The next time this sector gets written to, it'll get remapped, but you
> can force the issue by using "e2fsck -c", which in turn runs
> 'badblocks', or run 'badblocks' directly in a non-destructive mode if
> you aren't running an ext2/ext3/ext4 family of file system. (See the
> list archives for my posting on using 'badblocks' to burn-in a new drive.)
>
>   -Tom
>


-- 
Jerry Feldman <gaf at blu.org>
Boston Linux and Unix
PGP key id:3BC1EB90
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66  C0AF 7CEA 30FC 3BC1 EB90