[smartmontools-support] Recurring problem wit bad sectors

[Carlos E. R.]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Hi,

I see this in the warning log:

<3.2> 2018-05-27 01:17:24 Telcontar smartd 1659 - -  Device: /dev/sdd [SAT], 8 Currently unreadable (pending) sectors
<3.2> 2018-05-27 01:17:24 Telcontar smartd 1659 - -  Device: /dev/sdd [SAT], 8 Offline uncorrectable sectors

So I get worried. Sure enough, output of smartctl confirms:

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
   1 Raw_Read_Error_Rate     0x000f   109   099   006    Pre-fail  Always       -       22817632
   3 Spin_Up_Time            0x0003   094   094   000    Pre-fail  Always       -       0
   4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       2007
   5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
   7 Seek_Error_Rate         0x000f   069   060   030    Pre-fail  Always       -       137698891710
   9 Power_On_Hours          0x0032   084   084   000    Old_age   Always       -       14722
  10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
  12 Power_Cycle_Count       0x0032   099   099   020    Old_age   Always       -       2003
183 Runtime_Bad_Block       0x0032   099   099   000    Old_age   Always       -       1
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       1 1 1
189 High_Fly_Writes         0x003a   040   040   000    Old_age   Always       -       60
190 Airflow_Temperature_Cel 0x0022   063   050   045    Old_age   Always       -       37 (Min/Max 24/38)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       71
193 Load_Cycle_Count        0x0032   095   095   000    Old_age   Always       -       11080
194 Temperature_Celsius     0x0022   037   050   000    Old_age   Always       -       37 (0 13 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       8
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       8
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       14497h+53m+18.823s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       32806270267
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       60885926068



I want to find out the LBA of those sectors, but smartctl long test 
doesn't say:

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%     14735         -
# 2  Short offline       Completed without error       00%     14730         -


If I find out the LBAs, I would backup the affected partition and 
overwrite it with zeros.  But i don't know the LBAs. So what I do is run 
badblocks:

Telcontar:~ # time badblocks -s /dev/sdd
Checking for bad blocks (read-only test): done

real    230m53.226s
user    0m26.117s
sys     31m3.728s
Telcontar:~ #


It completes without problem, and after that the parameters 197 and 198 
are back to zero, and the warning disapears. Maybe badblocks triggers the 
remapping :-? Good, anyway.

But then a day or two later, I get the same warning, and I repeat the 
procedure with the same results.

???

Is it the same 8 blocks failing, or are they new sectors? If they are new 
sectors, I should replace the disk. But...

Can I do something better?

I do have a new hard disk prepared, but I didn't start cloning yet.


- -- 
Cheers,
        Carlos E. R.
        (from openSUSE 42.3 x86_64 "Malachite" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlsaXLIACgkQtTMYHG2NR9V3mACdF6KGGPLwoSpwu+fZ9URXhISR
lOcAniyhz9oW+7eUhLxm6N3lq2APVKK0
=kUym
-----END PGP SIGNATURE-----