/dev/da5 [SAT], Failed SMART usage Attribute: 5 Reallocated_Sector_Ct

[VioletDragon]

Hi,

I had a email yesterday from my Storage Server complaining about /dev/da5 [SAT], Failed SMART usage Attribute: 5 Reallocated_Sector_Ct. I did a smart test and it shows passed i decided to offline it and run it Seagate tools on this disk and all tests passed ive also did a full wipe on the disk and still have this /dev/da5 [SAT], Failed SMART usage Attribute: 5 Reallocated_Sector_Ct error, SMART results seems to be okay. Any ideas?

Code:

smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate IronWolf
Device Model:     ST3000VN007-2AH16M
Serial Number:    ZD
LU WWN Device Id: 5 000c50 0c3117743
Firmware Version: SC60
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5980 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed May 13 06:45:21 2020 BST
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:         (  581) seconds.
Offline data collection
capabilities:              (0x73) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    No 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:      (   1) minutes.
Extended self-test routine
recommended polling time:      ( 481) minutes.
Conveyance self-test routine
recommended polling time:      (   2) minutes.
SCT capabilities:            (0x50bd)    SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table 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   082   064   044    Pre-fail  Always       -       173945088
  3 Spin_Up_Time            0x0003   094   094   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       14
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   079   061   045    Pre-fail  Always       -       71657407
  9 Power_On_Hours          0x0032   097   097   000    Old_age   Always       -       3106 (96 230 0)
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       14
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       -       1
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   076   066   040    Old_age   Always       -       24 (Min/Max 24/26)
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       -       14
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       91
194 Temperature_Celsius     0x0022   024   040   000    Old_age   Always       -       24 (0 12 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      -       3098 (93 108 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       24484545283
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       38362697144

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  Short offline       Completed without error       00%      3104         -
# 2  Short offline       Completed without error       00%      3079         -
# 3  Extended offline    Completed without error       00%      2991         -
# 4  Short offline       Completed without error       00%      2912         -
# 5  Short offline       Completed without error       00%      2715         -
# 6  Extended offline    Completed without error       00%      2626         -
# 7  Short offline       Completed without error       00%      2547         -
# 8  Short offline       Completed without error       00%      2379         -
# 9  Extended offline    Completed without error       00%      2289         -
#10  Short offline       Completed without error       00%      2211         -
#11  Short offline       Completed without error       00%      1972         -
#12  Extended offline    Completed without error       00%      1886         -
#13  Short offline       Completed without error       00%      1808         -
#14  Short offline       Completed without error       00%      1640         -
#15  Extended offline    Completed without error       00%      1551         -
#16  Short offline       Completed without error       00%      1473         -
#17  Short offline       Completed without error       00%      1281         -
#18  Extended offline    Interrupted (host reset)      20%      1190         -
#19  Short offline       Completed without error       00%      1113         -
#20  Short offline       Completed without error       00%       945         -
#21  Extended offline    Completed without error       00%       855         -

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.

Thanks.

 

[Samuel Tai]

This happens on all disks from time to time. A sector will go bad, and the controller will copy the contents of that sector somewhere else, and then mark that sector as unavailable. So long as your SMART count for that attribute is below the threshold, you'll be OK. It's probably worth planning to replace that drive when the count gets closer to the threshold.

 

[VioletDragon]

This happens on all disks from time to time. A sector will go bad, and the controller will copy the contents of that sector somewhere else, and then mark that sector as unavailable. So long as your SMART count for that attribute is below the threshold, you'll be OK. It's probably worth planning to replace that drive when the count gets closer to the threshold.

.
Hi thanks for your reply. This drive is only 4 months old i will keep an eye on it, im going to run a long smart test.

 

[Pitfrr]

If the drive is new, did burn it in?
If not, I would advise to run badblocks on it and monitor the #5 Reallocated_Sector_Ct but also #197 and #198.

In the SMART data you posted, it is indeed surprising that you get an email because attribute #5 is at 0...
I know the pending sector (#197) can be increased and decreased if not confirmed but I'm not sure #5 works like that... I would have thought this is an only increasing counter.

 

[VioletDragon]

If the drive is new, did burn it in?
If not, I would advise to run badblocks on it and monitor the #5 Reallocated_Sector_Ct but also #197 and #198.

In the SMART data you posted, it is indeed surprising that you get an email because attribute #5 is at 0...
I know the pending sector (#197) can be increased and decreased if not confirmed but I'm not sure #5 works like that... I would have thought this is an only increasing counter.

Hi,
What do you mean by burn it in?

 

[Samuel Tai]

A burn-in period is a length of time where you tested the drive before putting it into production. It's not something that's typically done in consumer environments, but as you're now running a server, you'll need to start adopting some best practices from data center operations.

 

[VioletDragon]

A burn-in period is a length of time where you tested the drive before putting it into production. It's not something that's typically done in consumer environments, but as you're now running a server, you'll need to start adopting some best practices from data center operations.

I do a full Format will Zeros then i run a short and long SMART test and i also transfer huge files to the disk before putting the drive in production, This drive is only 4 Months old i have 2 disks in a iSCSI pool that has a date of 2013 and still working great, as it seems these 3TB seem to fail quicker.

 

[Pitfrr]

I do a full Format will Zeros then i run a short and long SMART test and i also transfer huge files to the disk before putting the drive in production

That's already something but unfortunately, not thorough enough...

• A full format doesn't check if the data written is good
• The long SMART test only does read test
• Transferring huge files only tests partially (not the complete disk) although it is a bit of a stress test

During the burn-in process you want to test the complete disk. One way to do it is to use badblocks (but there are other tools possible).
It does 4 passes: first writes 0 over the whole disk, verifies the whole disk, and then does it with 3 other different patterns (0x55, 0xAA and 0xFF).
It's a very long process because one cycles consists of 4 writes and read passes (of the whole disk).
It is advised to do this with any disk put in production, for new disks do reduce "infant mortality" (better this happens during the tests than in production!), for second hand disks to make sure they are ok.

But back to your original issue:
I would run badblocks on that disk and make sure attribute #5 is not going up.
But what puzzles me it that you get a notification about the reallocated sector count but this counter is at 0....
And also, if attributes #5, #197 or #198 go up and your disk is still under warranty, I would RMA it (but in your case you said that the Seagate tool didn't report anything wrong... and looking at the SMART data attributes #5, #197 and #197 are fine indeed...).

 

[VioletDragon]

That's already something but unfortunately, not thorough enough...

• A full format doesn't check if the data written is good
• The long SMART test only does read test
• Transferring huge files only tests partially (not the complete disk) although it is a bit of a stress test

During the burn-in process you want to test the complete disk. One way to do it is to use badblocks (but there are other tools possible).
It does 4 passes: first writes 0 over the whole disk, verifies the whole disk, and then does it with 3 other different patterns (0x55, 0xAA and 0xFF).
It's a very long process because one cycles consists of 4 writes and read passes (of the whole disk).
It is advised to do this with any disk put in production, for new disks do reduce "infant mortality" (better this happens during the tests than in production!), for second hand disks to make sure they are ok.

But back to your original issue:
I would run badblocks on that disk and make sure attribute #5 is not going up.
But what puzzles me it that you get a notification about the reallocated sector count but this counter is at 0....
And also, if attributes #5, #197 or #198 go up and your disk is still under warranty, I would RMA it (but in your case you said that the Seagate tool didn't report anything wrong... and looking at the SMART data attributes #5, #197 and #197 are fine indeed...).

Thanks for your message. Yes this is a strange one. Im currently running a long smart test. Reallocated Sectors are remaing at 0. I tested on another machine and still remains at 0. This happened since rebooting the Server.

 

[Samuel Tai]

Actually, that's a bad sign attribute 5 isn't incrementing. That indicates a controller NVRAM fault, and it's possible the disk controller isn't long for this world.

 

[Pitfrr]

Actually, that's a bad sign attribute 5 isn't incrementing. That indicates a controller NVRAM fault

What I don't get is why would you get a notification but then the attribute is still at 0? How could that be linked to the controller?
(I never had this situation so I'm curious... )


And in any case, just to be on the safe side, make sure you have good backups. :p

 

[Samuel Tai]

Not the system storage controller. The little controller PCB on the drive itself.

 

[Pitfrr]

Right! "Controller NVRAM" Didn't read till the end!
Now I get it...

 

[VioletDragon]

That's already something but unfortunately, not thorough enough...

• A full format doesn't check if the data written is good
• The long SMART test only does read test
• Transferring huge files only tests partially (not the complete disk) although it is a bit of a stress test

During the burn-in process you want to test the complete disk. One way to do it is to use badblocks (but there are other tools possible).
It does 4 passes: first writes 0 over the whole disk, verifies the whole disk, and then does it with 3 other different patterns (0x55, 0xAA and 0xFF).
It's a very long process because one cycles consists of 4 writes and read passes (of the whole disk).
It is advised to do this with any disk put in production, for new disks do reduce "infant mortality" (better this happens during the tests than in production!), for second hand disks to make sure they are ok.

But back to your original issue:
I would run badblocks on that disk and make sure attribute #5 is not going up.
But what puzzles me it that you get a notification about the reallocated sector count but this counter is at 0....
And also, if attributes #5, #197 or #198 go up and your disk is still under warranty, I would RMA it (but in your case you said that the Seagate tool didn't report anything wrong... and looking at the SMART data attributes #5, #197 and #197 are fine indeed...).

Code:

Here is the information from the Long Smart Test.


Please wait 481 minutes for test to complete.

Test will complete after Thu May 14 00:01:25 2020


Use smartctl -X to abort test.

% sudo smartctl -a /dev/da5

Password:

smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build)

Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org


=== START OF INFORMATION SECTION ===

Model Family:     Seagate IronWolf

Device Model:     ST3000VN007-2AH16M

Serial Number:    ZD

LU WWN Device Id: 5 000c50 0c3117743

Firmware Version: SC60

User Capacity:    3,000,592,982,016 bytes [3.00 TB]

Sector Sizes:     512 bytes logical, 4096 bytes physical

Rotation Rate:    5980 rpm

Form Factor:      3.5 inches

Device is:        In smartctl database [for details use: -P show]

ATA Version is:   ACS-3 T13/2161-D revision 5

SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)

Local Time is:    Thu May 14 00:06:18 2020 BST

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:         (  581) seconds.

Offline data collection

capabilities:              (0x73) SMART execute Offline immediate.

                    Auto Offline data collection on/off support.

                    Suspend Offline collection upon new

                    command.

                    No 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:      (   1) minutes.

Extended self-test routine

recommended polling time:      ( 481) minutes.

Conveyance self-test routine

recommended polling time:      (   2) minutes.

SCT capabilities:            (0x50bd)    SCT Status supported.

                    SCT Error Recovery Control supported.

                    SCT Feature Control supported.

                    SCT Data Table 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   080   064   044    Pre-fail  Always       -       94821573

  3 Spin_Up_Time            0x0003   094   094   000    Pre-fail  Always       -       0

  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       14

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

  7 Seek_Error_Rate         0x000f   079   061   045    Pre-fail  Always       -       75069442

  9 Power_On_Hours          0x0032   097   097   000    Old_age   Always       -       3123 (159 129 0)

10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0

12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       14

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

189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0

190 Airflow_Temperature_Cel 0x0022   079   066   040    Old_age   Always       -       21 (Min/Max 21/27)

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

193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       107

194 Temperature_Celsius     0x0022   021   040   000    Old_age   Always       -       21 (0 12 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      -       3114 (97 117 0)

241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       29190545587

242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       38362697165


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%      3120         -

# 2  Short offline       Completed without error       00%      3104         -

# 3  Short offline       Completed without error       00%      3079         -

# 4  Extended offline    Completed without error       00%      2991         -

# 5  Short offline       Completed without error       00%      2912         -

# 6  Short offline       Completed without error       00%      2715         -

# 7  Extended offline    Completed without error       00%      2626         -

# 8  Short offline       Completed without error       00%      2547         -

# 9  Short offline       Completed without error       00%      2379         -

#10  Extended offline    Completed without error       00%      2289         -

#11  Short offline       Completed without error       00%      2211         -

#12  Short offline       Completed without error       00%      1972         -

#13  Extended offline    Completed without error       00%      1886         -

#14  Short offline       Completed without error       00%      1808         -

#15  Short offline       Completed without error       00%      1640         -

#16  Extended offline    Completed without error       00%      1551         -

#17  Short offline       Completed without error       00%      1473         -

#18  Short offline       Completed without error       00%      1281         -

#19  Extended offline    Interrupted (host reset)      20%      1190         -

#20  Short offline       Completed without error       00%      1113         -

#21  Short offline       Completed without error       00%       945         -


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.

 

[VioletDragon]

Plugged it into my workstation thats running Ubuntu Desktop and its not reporting any errors on this disk neither. Im wondering if Freenas is being funny

 

[Samuel Tai]

FreeNAS is MUCH more demanding on storage than Ubuntu.

 

[VioletDragon]

Update,

I shutdown the Server and checked the cabling put the drive back in and booted up the Server now this error has gone. Im going to add it back to my RAIDZ2 pool and see what happens.

 

[Philip Robar]

FreeNAS is MUCH more demanding on storage than Ubuntu.

How is one OS inherently "much more demanding" on a disk than any other OS (or file system, which is what I suspect that you really meant)?

 

[Samuel Tai]

Ext4 on Ubuntu only checksums metadata and the journal. ZFS checksums every block. Also, there's much more going on with vdevs participating in stripes/mirrors/raidzx, so there's a lot more reading/writing/parity IO, which is all checksummed.

 

[VioletDragon]

Ext4 on Ubuntu only checksums metadata and the journal. ZFS checksums every block. Also, there's much more going on with vdevs participating in stripes/mirrors/raidzx, so there's a lot more reading/writing/parity IO, which is all checksummed.

This is getting of-topic now but i use ZFS on the boot drive on my workstation.