[smartmontools-support] Recurring problem wit bad sectors

Carlos E. R. robin.listas at telefonica.net
Fri Jul 13 13:54:27 CEST 2018


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



On Friday, 2018-06-08 at 12:38 +0200, Carlos E. R. wrote:

> 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

...

> 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:


I never found out, but I learn little bits more :-)

I replaced the disk, but I left the old hard disk connected to see how it 
behaved. I filled it with zeroes (dd...) which succeeded, formatted and 
stored some files. I noticed this in the system log:

<3.6> 2018-07-13 13:18:26 Telcontar smartd 4058 - -  Device: /dev/sda [SAT], SMART Prefailure Attribute: 5 Reallocated_Sector_Ct changed from 98 [Raw 2496] to 98 [Raw 2520]

Now this is interesting.

As you see above, the Reallocated Sector count was zero

    5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always           0

now is bigger, half an hour later than that report:

   5 Reallocated_Sector_Ct   0x0033   098   098   010    Pre-fail  Always       -       2536

   9 Power_On_Hours          0x0032   083   083   000    Old_age   Always       -       15265

Minutes later:

   5 Reallocated_Sector_Ct   0x0033   098   098   010    Pre-fail  Always       -       2544
   9 Power_On_Hours          0x0032   083   083   000    Old_age   Always       -       15265


Interesting! :-)

So... but:

Telcontar:~ # smartctl -H /dev/sda
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.4.138-59-default] (SUSE RPM)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, 
www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

Telcontar:~ #


I should expect it to fail soon, despite that.


- -- 
Cheers,
        Carlos E. R.
        (from openSUSE 42.3 x86_64 "Malachite" at Telcontar)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAltIkvsACgkQtTMYHG2NR9XJKQCeMP9MbCNOkmArsaNWm2dTxCbs
iQoAn0K2MZhNT5FZRq4JkI7/UcK16zL9
=haPj
-----END PGP SIGNATURE-----



More information about the Smartmontools-support mailing list