Re: Signs of hard drive failure?

From	Bob Weber <bobrweber@gmail.com>
Newsgroups	linux.debian.user
Subject	Re: Signs of hard drive failure?
Date	2019-10-22 21:20 +0200
Message-ID	<yU7Rf-3FJ-9@gated-at.bofh.it> (permalink)
References	<yTzmx-75Q-7@gated-at.bofh.it> <yTG4F-2V8-3@gated-at.bofh.it> <yTYkV-6ea-5@gated-at.bofh.it> <yU6it-2zY-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On 10/22/19 1:01 PM, Ken Heard wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> At about 04:35 EDT today 2019-10-22 Tuesday I ran 'sudo smartctl -t
> long /dev/sdb'.  At 12:48 I ran the command in the next line.  The
> result is below after the next paragraph.
>
> Based on the results below relating to /dev/sdb and the results
> relating to /dev/sda quoted in my previous email today, I conclude
> that while smartctl considers my two hard drives three years old and
> consequently prone to failure -- what else really is new, all devices
> are prone to failure -- my current backup problems are not related to
> failure of either or both of these drives.  As I stated in my original
> post, they have been in use for only 1.75 years.  I shall consequently
> continue to examine at my scripts for errors in creating tarballs for
> my backups.
>
> Regards, Ken
> - ---------------------------------------------------
>
> ken@SOL:~$ sudo smartctl -a /dev/sdb
> smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-9-amd64] (local build)
> Copyright (C) 2002-16, Bruce Allen, Christian Franke,
> www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Model Family:     Seagate Barracuda 7200.14 (AF)
> Device Model:     ST2000DM001-1ER164
> Serial Number:    Z4Z0TKY8
> LU WWN Device Id: 5 000c50 0796a3479
> Firmware Version: CC25
> User Capacity:    2,000,398,934,016 bytes [2.00 TB]
> Sector Sizes:     512 bytes logical, 4096 bytes physical
> Rotation Rate:    7200 rpm
> Form Factor:      3.5 inches
> Device is:        In smartctl database [for details use: -P show]
> ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
> SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
> Local Time is:    Tue Oct 22 12:45:42 2019 EDT
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
>
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED
>
> General SMART Values:
> Offline data collection status:  (0x82) Offline data collection activity
>                                          was completed without error.
>                                          Auto Offline Data Collection:
> Enabled.
> Self-test execution status:      (   0) The previous self-test routine
> completed
>                                          without error or no self-test
> has ever
>                                          been run.
> Total time to complete Offline
> data collection:                (   80) seconds.
> Offline data collection
> capabilities:                    (0x7b) SMART execute Offline immediate.
>                                          Auto Offline data collection
> on/off support.
>                                          Suspend Offline collection
> upon new
>                                          command.
>                                          Offline surface scan supported.
>                                          Self-test supported.
>                                          Conveyance Self-test supported.
>                                          Selective Self-test supported.
> SMART capabilities:            (0x0003) Saves SMART data before entering
>                                          power-saving mode.
>                                          Supports SMART auto save timer.
> Error logging capability:        (0x01) Error logging supported.
>                                          General Purpose Logging supporte
> d.
> Short self-test routine
> recommended polling time:        (   1) minutes.
> Extended self-test routine
> recommended polling time:        ( 219) minutes.
> Conveyance self-test routine
> recommended polling time:        (   2) minutes.
> SCT capabilities:              (0x1085) SCT Status supported.
>
> 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   115   099   006    Pre-fail
> Always       -       90023624
>    3 Spin_Up_Time            0x0003   096   096   000    Pre-fail
> Always       -       0
>    4 Start_Stop_Count        0x0032   100   100   020    Old_age
> Always       -       557
>    5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail
> Always       -       0
>    7 Seek_Error_Rate         0x000f   073   060   030    Pre-fail
> Always       -       24992023
>    9 Power_On_Hours          0x0032   096   096   000    Old_age
> Always       -       3834
>   10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail
> Always       -       0
>   12 Power_Cycle_Count       0x0032   100   100   020    Old_age
> Always       -       556
> 183 Runtime_Bad_Block       0x0032   100   100   000    Old_age
> Always       -       0
> 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   100   000    Old_age
> Always       -       0 0 0
> 189 High_Fly_Writes         0x003a   096   096   000    Old_age
> Always       -       4
> 190 Airflow_Temperature_Cel 0x0022   070   065   045    Old_age
> Always       -       30 (Min/Max 21/31)
> 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       -       104
> 193 Load_Cycle_Count        0x0032   100   100   000    Old_age
> Always       -       832
> 194 Temperature_Celsius     0x0022   030   040   000    Old_age
> Always       -       30 (0 18 0 0 0)
> 197 Current_Pending_Sector  0x0012   100   100   000    Old_age
> Always       -       0
> 198 Offline_Uncorrectable   0x0010   100   100   000    Old_age
> Offline      -       0
> 199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age
> Always       -       0
> 240 Head_Flying_Hours       0x0000   100   253   000    Old_age
> Offline      -       3733h+04m+36.466s
> 241 Total_LBAs_Written      0x0000   100   253   000    Old_age
> Offline      -       31308850703
> 242 Total_LBAs_Read         0x0000   100   253   000    Old_age
> Offline      -       133591359037
>
> SMART Error Log Version: 1
> No Errors Logged
>
> 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%      3830
>         -
>
> SMART Selective self-test log data structure revision number 1
>   SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
>      1        0        0  Not_testing
>      2        0        0  Not_testing
>      3        0        0  Not_testing
>      4        0        0  Not_testing
>      5        0        0  Not_testing
> Selective self-test flags (0x0):
>    After scanning selected spans, do NOT read-scan remainder of disk.
> If Selective self-test is pending on power-up, resume after 0 minute
> delay.
>
> ken@SOL:~$
>
> -----BEGIN PGP SIGNATURE-----
>
> iF0EARECAB0WIQR9YFyM2lJAhDprmoOU2UnM6QmZNwUCXa816gAKCRCU2UnM6QmZ
> N+GRAJ49DzJwDIA6SlWnmyNBVk1+UUZh8wCdHJhfWS6oChj+SEwtttfuTiiOrwo=
> =e/7+
> -----END PGP SIGNATURE-----
>
 From the long self test everything looks good.  There are only about 3834 hours 
on the drives ... about 6 months worth.  I have drives that have over 5 years 
now.  I run the long self test every other day on my drives to keep up with the 
possibility  of errors.  If you feel that you have had these drives long enough 
you could add another 2TB drive to your raid (the safest thing to do to save 
your data) making it a 3 drive array.

So now you just need to do fsck on the raid drive.  As I explained before the 
sure way to do this is to boot to a linux system cd.  You mentioned knoppix.  I 
use sysrescuecd from http://www.system-rescue-cd.org.
<http://www.system-rescue-cd.org/>

Whatever disk you choose it should be fairly recent so that you know the raid 
will be found and setup correctly.  After booting the cd first do "ls /dev/md*" 
to find the raid drives that have been found.  Then run "fsck -f /dev/mdx" where 
x will be a number up to 3 digits long (I've never seen a longer number ... 
usually something like 127 is the biggest that I have seen).  If that passes 
then your drives should be ok.

There are other tests you could run to see if the 2 drives are alike as far as 
the raid part goes.  The only thing is to correct a difference found ... which 
drive is correct.  The mdadm commands to do this apparently pick one drive as 
correct (who knows which one) and overwrite the other drive for that part that 
part that is different.  Pretty scary to me!

-- 


*...Bob*

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Signs of hard drive failure? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-10-21 15:40 +0200
  Re: Signs of hard drive failure? Renato Gallo <renato@aster-lab.com> - 2019-10-22 11:10 +0200
  Re: Signs of hard drive failure? elvis <elvis@dogonfire.com> - 2019-10-22 11:30 +0200
    Re: Signs of hard drive failure? David Wright <deblis@lionunicorn.co.uk> - 2019-10-22 17:00 +0200
      Re: Signs of hard drive failure? elvis <elvis@dogonfire.com> - 2019-10-22 23:20 +0200
        Re: Signs of hard drive failure? Christopher David Howie <me@chrishowie.com> - 2019-10-23 01:00 +0200
  Re: Signs of hard drive failure? Christopher David Howie <me@chrishowie.com> - 2019-10-22 19:40 +0200
  Re: Signs of hard drive failure? Bob Weber <bobrweber@gmail.com> - 2019-10-22 21:20 +0200

csiph-web