CentOS - Jan 2016 - HDD badblocks

On Sun, Jan 17, 2016 at 10:05 AM, Matt Garman <matthew.garman at
gmail.com> wrote:
> I'm not sure what's going on with your drive. But if it were mine,
I'd want
> to replace it. If there are issues, that long smart check ought to turn up
> something,  and in my experience, that's enough for a manufacturer to
do a
> warranty replacement.
I agree with Matt. Go ahead and run a few of the S.M.A.R.T. tests. I
can almost guarantee based off of your description of your problem
that they will fail.

badblocks(8) is a very antiquated tool. Almost every hard drive has a
few bad sectors from the factory. Very old hard drives used to have a
list of the bad sectors printed on the front of the label. When you
first created a filesystem you had to enter all of the bad sectors
from the label so that the filesystem wouldn't store data there. Years
later, more bad sectors would form and you could enter them into the
filesystem by discovering them using a tool like badblocks(8).

Today, drives do all of this work automatically. The manufacturer of a
hard drive will scan the entire surface and write the bad sectors into
a section of the hard drive's electronics known as the P-list. The
controller on the drive will automatically remap these sectors to a
small area of unused sectors set aside for this very purpose. Later if
more bad sectors form, hard drives when they see a bad sector will
enter it into a list known as the G-list and then remap this sector to
other sectors in the unused area of the drive I mentioned earlier.

Basically under normal conditions, the end user should NEVER see bad
sectors from their perspective. If badblocks(8) is reporting bad
sectors, it is very likely that enough bad sectors have formed to the
point where the unused reserved sectors is depleted of replacement
sectors. While in theory you could run badblocks(8) and pass it to the
filesystem, I can ensure you that the growth of bad sectors at this
point has reached a point in which it will continue.

I'd stop using that hard drive, pull any important data, and then
proceed to run S.M.A.R.T. tests so if the drive is under warranty you
can have it replaced.

Brandon Vincent

Il 17/01/2016 18:46, Brandon Vincent ha scritto:
> On Sun, Jan 17, 2016 at 10:05 AM, Matt Garman <matthew.garman at
gmail.com> wrote:
>> I'm not sure what's going on with your drive. But if it were
mine, I'd want
>> to replace it. If there are issues, that long smart check ought to turn
up
>> something,  and in my experience, that's enough for a manufacturer
to do a
>> warranty replacement.
>
> I agree with Matt. Go ahead and run a few of the S.M.A.R.T. tests. I
> can almost guarantee based off of your description of your problem
> that they will fail.
>
> badblocks(8) is a very antiquated tool. Almost every hard drive has a
> few bad sectors from the factory. Very old hard drives used to have a
> list of the bad sectors printed on the front of the label. When you
> first created a filesystem you had to enter all of the bad sectors
> from the label so that the filesystem wouldn't store data there. Years
> later, more bad sectors would form and you could enter them into the
> filesystem by discovering them using a tool like badblocks(8).
>
> Today, drives do all of this work automatically. The manufacturer of a
> hard drive will scan the entire surface and write the bad sectors into
> a section of the hard drive's electronics known as the P-list. The
> controller on the drive will automatically remap these sectors to a
> small area of unused sectors set aside for this very purpose. Later if
> more bad sectors form, hard drives when they see a bad sector will
> enter it into a list known as the G-list and then remap this sector to
> other sectors in the unused area of the drive I mentioned earlier.
>
> Basically under normal conditions, the end user should NEVER see bad
> sectors from their perspective. If badblocks(8) is reporting bad
> sectors, it is very likely that enough bad sectors have formed to the
> point where the unused reserved sectors is depleted of replacement
> sectors. While in theory you could run badblocks(8) and pass it to the
> filesystem, I can ensure you that the growth of bad sectors at this
> point has reached a point in which it will continue.
>
> I'd stop using that hard drive, pull any important data, and then
> proceed to run S.M.A.R.T. tests so if the drive is under warranty you
> can have it replaced.
>
> Brandon Vincent
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
I'm running long smart test. I'll report data when finished

Il 17/01/2016 19:36, Alessandro Baggi ha scritto:
> Il 17/01/2016 18:46, Brandon Vincent ha scritto:
>> On Sun, Jan 17, 2016 at 10:05 AM, Matt Garman
>> <matthew.garman at gmail.com> wrote:
>>> I'm not sure what's going on with your drive. But if it
were mine,
>>> I'd want
>>> to replace it. If there are issues, that long smart check ought to
>>> turn up
>>> something,  and in my experience, that's enough for a
manufacturer to
>>> do a
>>> warranty replacement.
>>
>> I agree with Matt. Go ahead and run a few of the S.M.A.R.T. tests. I
>> can almost guarantee based off of your description of your problem
>> that they will fail.
>>
>> badblocks(8) is a very antiquated tool. Almost every hard drive has a
>> few bad sectors from the factory. Very old hard drives used to have a
>> list of the bad sectors printed on the front of the label. When you
>> first created a filesystem you had to enter all of the bad sectors
>> from the label so that the filesystem wouldn't store data there.
Years
>> later, more bad sectors would form and you could enter them into the
>> filesystem by discovering them using a tool like badblocks(8).
>>
>> Today, drives do all of this work automatically. The manufacturer of a
>> hard drive will scan the entire surface and write the bad sectors into
>> a section of the hard drive's electronics known as the P-list. The
>> controller on the drive will automatically remap these sectors to a
>> small area of unused sectors set aside for this very purpose. Later if
>> more bad sectors form, hard drives when they see a bad sector will
>> enter it into a list known as the G-list and then remap this sector to
>> other sectors in the unused area of the drive I mentioned earlier.
>>
>> Basically under normal conditions, the end user should NEVER see bad
>> sectors from their perspective. If badblocks(8) is reporting bad
>> sectors, it is very likely that enough bad sectors have formed to the
>> point where the unused reserved sectors is depleted of replacement
>> sectors. While in theory you could run badblocks(8) and pass it to the
>> filesystem, I can ensure you that the growth of bad sectors at this
>> point has reached a point in which it will continue.
>>
>> I'd stop using that hard drive, pull any important data, and then
>> proceed to run S.M.A.R.T. tests so if the drive is under warranty you
>> can have it replaced.
>>
>> Brandon Vincent
>> _______________________________________________
>> CentOS mailing list
>> CentOS at centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
> I'm running long smart test. I'll report data when finished
I've performed smartctl test on sda. This is the result from smartctl -a 
/dev/sda:


smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.10.0-327.4.4.el7.x86_64] 
(local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ==Device Model:     WDC WD6400BEVT80A0RT0
Serial Number:    WD-WXF0AB9Y6939
LU WWN Device Id: 5 0014ee 0ac91c337
Firmware Version: 01.01A01
User Capacity:    640,135,028,736 bytes [640 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    5400 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Mon Jan 18 09:42:01 2016 CET
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:  (0x00) Offline data collection activity
                                         was never started.
                                         Auto Offline Data Collection: 
Disabled.
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:                (15960) 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 supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 185) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x7037) SCT Status supported.
                                         SCT Feature Control supported.
                                         SCT Data Table supported.

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       -       0
   3 Spin_Up_Time            0x0027   185   170   021    Pre-fail 
Always       -       1716
   4 Start_Stop_Count        0x0032   067   067   000    Old_age 
Always       -       33362
   5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail 
Always       -       0
   7 Seek_Error_Rate         0x002e   200   200   000    Old_age 
Always       -       0
   9 Power_On_Hours          0x0032   098   098   000    Old_age 
Always       -       2129
  10 Spin_Retry_Count        0x0032   100   100   051    Old_age 
Always       -       0
  11 Calibration_Retry_Count 0x0032   100   100   000    Old_age 
Always       -       0
  12 Power_Cycle_Count       0x0032   099   099   000    Old_age 
Always       -       1572
191 G-Sense_Error_Rate      0x0032   001   001   000    Old_age   Always 
       -       529
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always 
       -       257
193 Load_Cycle_Count        0x0032   098   098   000    Old_age   Always 
       -       308088
194 Temperature_Celsius     0x0022   121   089   000    Old_age   Always 
       -       26
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   100   253   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   051    Old_age 
Offline      -       0


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%      2126 
      -
# 2  Short offline       Completed without error       00%      1626 
      -
# 3  Extended captive    Interrupted (host reset)      90%       379 
      -
# 4  Short offline       Completed without error       00%       327 
      -

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.







Seem that there are not errors. This disk is failing?