Seagate NAS HDD vs WD Red?

Status
Not open for further replies.
ewhac

ewhac

Contributor
Joined
Aug 20, 2013
Messages
177
I'm partial to Hitachi Ultrastars myself...
 
Bhoot

Bhoot

Patron
Joined
Mar 28, 2015
Messages
241
DrKK said:
Issue
Code:
smartctl -x /dev/ada0
for each device ada0..adaN, then pastebin the result and give us the link.
Click to expand...
the result is going in more than one page with shell running in GUI 132x50. Anyway I could get it right from the beginning?
 
Ericloewe

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Bhoot said:
the result is going in more than one page with shell running in GUI 132x50. Anyway I could get it right from the beginning?
Click to expand...
Use putty or your favorite SSH client.
 
joeschmuck

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
danb35 said:
...or redirect to a file: smartctl -x /dev/ada0 > smartoutput.txt
Click to expand...
That is a great option, then you could just attach the output. However might I suggest a minor change and then you could just increment the ada0 to ada1, etc...
"smartctl -x /dev/ada0 >> smartoutput.txt" and this will append each run to the end of the smartoutput.txt file vice having to make up separate files. But it's just another option.
 
C

cudencuden

Dabbler
Joined
Dec 15, 2015
Messages
26
a bit offtopic but i've been hunting for wd red deals for the last couple months....didn't have much luck with the 4TB wd red...the 3TB and 6TB seems to go on sale more often
 
Bhoot

Bhoot

Patron
Joined
Mar 28, 2015
Messages
241
Ericloewe said:
Use putty or your favorite SSH client.
Click to expand...
i tried running ssh on filezilla no success. :( somehow the username password didn't match. Any youtube tutorial?
danb35 said:
...or redirect to a file: smartctl -x /dev/ada0 > smartoutput.txt
Click to expand...
Could you please elaborate?
 
ChiknNutz

ChiknNutz

Patron
Joined
Nov 6, 2015
Messages
217
I just built my FreeNAS using the 3TB Seagates. I got the first four of them for $93.50 each, then the last two for $100 each. I didn't see any compelling reason to go with the WD Reds so picked what was on sale at the time. Of course the system is still really new, so nothing yet to report on the overall longevity.
 
danb35

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Following a command with > filename will send the output of that command to filename, overwriting filename if it already exists. Following the command with >> filename, as @joeschmuck suggested, will send the output to filename, appending it to the end of filename if it already exists. Either one will create a text file with the output of the smartctl commands, which you can then put on an accessible share on your server.
 
Bhoot

Bhoot

Patron
Joined
Mar 28, 2015
Messages
241
solarisguy said:
Did you enable SSH root login in the GUI?
Click to expand...
yes sir
ssh.png
 
Last edited:
S

solarisguy

Guru
Joined
Apr 4, 2014
Messages
1,125
@Bhoot, is this SFTP or SSH ?

Could please try
  1. ssh root@localhost in the GUI using Shell, just to verify that settings are right
  2. use PuTTY for external access
 
joeschmuck

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
Filezilla is for FTP, right? Not SSH. Use Putty, or actually with the instructions above you can do it from the GUI shell.
 
Jailer

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
joeschmuck said:
Filezilla is for FTP, right?
Click to expand...
You can SFTP with Filezilla and get in, just need to make sure that's the protocol selected in the settings before you connect.
 
Bhoot

Bhoot

Patron
Joined
Mar 28, 2015
Messages
241
so here is the info for a disk which suddenly depleted from 0 in week 2 od December to 460 unreadable (pending) sectors in SMART test in the 3rd week of December
I am sorry for the delay, was a little busy around the holidays. Now I am purchasing a hot spare (WD Red 4tb again) and sending this to WD for RMA.

Code:
[root@freenas] ~# smartctl -x /dev/ada3
smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p25 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red (AF)
Device Model:     WDC WD40EFRX-68WT0N0
Serial Number:    WD-WCC4E4JL9D6R
LU WWN Device Id: 5 0014ee 20baf3797
Firmware Version: 82.00A82
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Jan  7 16:14:14 2016 IST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: 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:                (54780) 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:        ( 548) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x703d) SCT Status supported.
                                        SCT Error Recovery Control 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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   193   193   051    -    181539
  3 Spin_Up_Time            POS--K   188   180   021    -    7575
  4 Start_Stop_Count        -O--CK   100   100   000    -    117
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   200   200   000    -    0
  9 Power_On_Hours          -O--CK   092   092   000    -    5979
10 Spin_Retry_Count        -O--CK   100   100   000    -    0
11 Calibration_Retry_Count -O--CK   100   100   000    -    0
12 Power_Cycle_Count       -O--CK   100   100   000    -    117
192 Power-Off_Retract_Count -O--CK   200   200   000    -    63
193 Load_Cycle_Count        -O--CK   200   200   000    -    391
194 Temperature_Celsius     -O---K   115   104   000    -    37
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    461
198 Offline_Uncorrectable   ----CK   100   253   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   179   179   000    -    8756
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      6  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters
0x21       GPL     R/O      1  Write stream error log
0x22       GPL     R/O      1  Read stream error log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0-0xa7  GPL,SL  VS      16  Device vendor specific log
0xa8-0xb7  GPL,SL  VS       1  Device vendor specific log
0xbd       GPL,SL  VS       1  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xc1       GPL     VS      93  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 16364 (device log contains only the most recent 24 errors)
        CR     = Command Register
        FEATR  = Features Register
        COUNT  = Count (was: Sector Count) Register
        LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
        LH     = LBA High (was: Cylinder High) Register    ]   LBA
        LM     = LBA Mid (was: Cylinder Low) Register      ] Register
        LL     = LBA Low (was: Sector Number) Register     ]
        DV     = Device (was: Device/Head) Register
        DC     = Device Control Register
        ER     = Error register
        ST     = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 16364 [19] occurred at disk power-on lifetime: 5979 hours (249 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 b0 00 01 a9 07 49 9f 40 00  Error: UNC 176 sectors at LBA = 0x1a907499f = 7130794399

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 b0 00 01 a9 07 49 58 40 08     03:19:50.043  READ DMA EXT
  b0 00 d5 00 01 00 00 00 c2 4f e0 40 08     03:19:50.043  SMART READ LOG
  25 00 00 00 b0 00 01 a9 07 49 58 40 08     03:19:43.045  READ DMA EXT
  ec 00 00 00 01 00 00 00 00 00 00 40 08     03:19:43.045  IDENTIFY DEVICE
  25 00 00 00 b0 00 01 a9 07 49 58 40 08     03:19:36.047  READ DMA EXT

Error 16363 [18] occurred at disk power-on lifetime: 5979 hours (249 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 b0 00 01 a9 07 49 9f 40 00  Error: UNC 176 sectors at LBA = 0x1a907499f = 7130794399

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 b0 00 01 a9 07 49 58 40 08     03:19:43.045  READ DMA EXT
  ec 00 00 00 01 00 00 00 00 00 00 40 08     03:19:43.045  IDENTIFY DEVICE
  25 00 00 00 b0 00 01 a9 07 49 58 40 08     03:19:36.047  READ DMA EXT
  25 00 00 00 b0 00 01 a9 07 49 58 40 08     03:19:29.049  READ DMA EXT
  25 00 00 00 b0 00 01 a9 07 49 58 40 08     03:19:22.051  READ DMA EXT

Error 16362 [17] occurred at disk power-on lifetime: 5979 hours (249 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 b0 00 01 a9 07 49 9f 40 00  Error: UNC 176 sectors at LBA = 0x1a907499f = 7130794399

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 b0 00 01 a9 07 49 58 40 08     03:19:36.047  READ DMA EXT
  25 00 00 00 b0 00 01 a9 07 49 58 40 08     03:19:29.049  READ DMA EXT
  25 00 00 00 b0 00 01 a9 07 49 58 40 08     03:19:22.051  READ DMA EXT
  60 00 10 00 10 00 00 00 40 02 90 40 08     03:19:22.027  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     03:19:22.023  READ LOG EXT

Error 16361 [16] occurred at disk power-on lifetime: 5979 hours (249 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 b0 00 01 a9 07 49 8f 40 00  Error: UNC 176 sectors at LBA = 0x1a907498f = 7130794383

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 b0 00 01 a9 07 49 58 40 08     03:19:29.049  READ DMA EXT
  25 00 00 00 b0 00 01 a9 07 49 58 40 08     03:19:22.051  READ DMA EXT
  60 00 10 00 10 00 00 00 40 02 90 40 08     03:19:22.027  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     03:19:22.023  READ LOG EXT
  60 00 58 00 10 00 01 a9 07 21 c8 40 08     03:19:15.029  READ FPDMA QUEUED

Error 16360 [15] occurred at disk power-on lifetime: 5979 hours (249 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 b0 00 01 a9 07 49 9f 40 00  Error: UNC 176 sectors at LBA = 0x1a907499f = 7130794399

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  25 00 00 00 b0 00 01 a9 07 49 58 40 08     03:19:22.051  READ DMA EXT
  60 00 10 00 10 00 00 00 40 02 90 40 08     03:19:22.027  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     03:19:22.023  READ LOG EXT
  60 00 58 00 10 00 01 a9 07 21 c8 40 08     03:19:15.029  READ FPDMA QUEUED
  60 00 10 00 08 00 00 00 40 02 90 40 08     03:19:15.029  READ FPDMA QUEUED

Error 16359 [14] occurred at disk power-on lifetime: 5979 hours (249 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 01 a9 07 21 f8 40 00  Error: UNC at LBA = 0x1a90721f8 = 7130784248

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 58 00 10 00 01 a9 07 21 c8 40 08     03:19:15.029  READ FPDMA QUEUED
  60 00 10 00 08 00 00 00 40 02 90 40 08     03:19:15.029  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     03:19:15.025  READ LOG EXT
  60 00 58 00 08 00 01 a9 07 21 c8 40 08     03:19:08.030  READ FPDMA QUEUED
  60 00 10 00 00 00 00 00 40 02 90 40 08     03:19:08.030  READ FPDMA QUEUED

Error 16358 [13] occurred at disk power-on lifetime: 5979 hours (249 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 01 a9 07 22 0f 40 00  Error: UNC at LBA = 0x1a907220f = 7130784271

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 58 00 08 00 01 a9 07 21 c8 40 08     03:19:08.030  READ FPDMA QUEUED
  60 00 10 00 00 00 00 00 40 02 90 40 08     03:19:08.030  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     03:19:08.026  READ LOG EXT
  60 00 58 00 00 00 01 a9 07 21 c8 40 08     03:19:01.032  READ FPDMA QUEUED
  60 00 10 00 f8 00 00 00 40 02 90 40 08     03:19:01.032  READ FPDMA QUEUED

Error 16357 [12] occurred at disk power-on lifetime: 5979 hours (249 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 01 a9 07 22 0f 40 00  Error: UNC at LBA = 0x1a907220f = 7130784271

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 58 00 00 00 01 a9 07 21 c8 40 08     03:19:01.032  READ FPDMA QUEUED
  60 00 10 00 f8 00 00 00 40 02 90 40 08     03:19:01.032  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     03:19:01.028  READ LOG EXT
  60 00 58 00 f8 00 01 a9 07 21 c8 40 08     03:18:54.009  READ FPDMA QUEUED
  60 00 10 00 f0 00 01 d1 c0 bc 90 40 08     03:18:54.009  READ FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      5812         -
# 2  Extended offline    Completed: read failure       10%      5774         7050726168
# 3  Short offline       Completed without error       00%      5620         -
# 4  Short offline       Completed without error       00%      5401         -
# 5  Extended offline    Completed without error       00%      5318         -
# 6  Short offline       Completed without error       00%      5239         -
# 7  Short offline       Completed without error       00%      5122         -
# 8  Short offline       Completed without error       00%      4951         -
# 9  Extended offline    Completed without error       00%      4868         -
#10  Short offline       Completed without error       00%      4784         -
#11  Short offline       Completed without error       00%      4545         -
#12  Extended offline    Completed without error       00%      4463         -
#13  Short offline       Completed without error       00%      4377         -
#14  Short offline       Completed without error       00%      4209         -
#15  Extended offline    Completed without error       00%      4124         -
#16  Short offline       Completed without error       00%      4042         -
#17  Short offline       Completed without error       00%      3826         -
#18  Extended offline    Completed without error       00%      3743         -

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.

SCT Status Version:                  3
SCT Version (vendor specific):       258 (0x0102)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    37 Celsius
Power Cycle Min/Max Temperature:     37/37 Celsius
Lifetime    Min/Max Temperature:     29/48 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    478 (124)

Index    Estimated Time   Temperature Celsius
125    2016-01-07 08:17    37  ******************
...    ..( 58 skipped).    ..  ******************
184    2016-01-07 09:16    37  ******************
185    2016-01-07 09:17     ?  -
186    2016-01-07 09:18    37  ******************
...    ..(415 skipped).    ..  ******************
124    2016-01-07 16:14    37  ******************

SCT Error Recovery Control:
           Read:     70 (7.0 seconds)
          Write:     70 (7.0 seconds)

Device Statistics (GP Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            3  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            3  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4        11997  Vendor specific
 
Bhoot

Bhoot

Patron
Joined
Mar 28, 2015
Messages
241
This is the output for another disk which generated SMART errors very early in the system.
This goes for RMA after I get the first one back from RMA.
Please feel free to comment on the system/errors.
Also realized my airflow wasn't as good with the original case. So now I switched to Fractal R5 with 2 static fans in the front of the disks along with 2 (included) 140mm gp14. Temperatures of both disks and CPU now lesser than before.
Code:
[root@freenas] ~# smartctl -x /dev/ada2
smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p25 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red (AF)
Device Model:     WDC WD40EFRX-68WT0N0
Serial Number:    WD-WCC4E4JL934K
LU WWN Device Id: 5 0014ee 261047b63
Firmware Version: 82.00A82
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Jan  7 16:22:53 2016 IST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: 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:                (52680) 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:        ( 527) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x703d) SCT Status supported.
                                        SCT Error Recovery Control 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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   200   199   051    -    3483
  3 Spin_Up_Time            POS--K   185   176   021    -    7741
  4 Start_Stop_Count        -O--CK   100   100   000    -    117
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   200   200   000    -    0
  9 Power_On_Hours          -O--CK   092   092   000    -    5979
10 Spin_Retry_Count        -O--CK   100   100   000    -    0
11 Calibration_Retry_Count -O--CK   100   100   000    -    0
12 Power_Cycle_Count       -O--CK   100   100   000    -    117
192 Power-Off_Retract_Count -O--CK   200   200   000    -    63
193 Load_Cycle_Count        -O--CK   200   200   000    -    381
194 Temperature_Celsius     -O---K   114   109   000    -    38
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    44
198 Offline_Uncorrectable   ----CK   100   253   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   200   200   000    -    52
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      6  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters
0x21       GPL     R/O      1  Write stream error log
0x22       GPL     R/O      1  Read stream error log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0-0xa7  GPL,SL  VS      16  Device vendor specific log
0xa8-0xb7  GPL,SL  VS       1  Device vendor specific log
0xbd       GPL,SL  VS       1  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xc1       GPL     VS      93  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 1566 (device log contains only the most recent 24 errors)
        CR     = Command Register
        FEATR  = Features Register
        COUNT  = Count (was: Sector Count) Register
        LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
        LH     = LBA High (was: Cylinder High) Register    ]   LBA
        LM     = LBA Mid (was: Cylinder Low) Register      ] Register
        LL     = LBA Low (was: Sector Number) Register     ]
        DV     = Device (was: Device/Head) Register
        DC     = Device Control Register
        ER     = Error register
        ST     = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 1566 [5] occurred at disk power-on lifetime: 5486 hours (228 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 02 71 91 98 40 00  Error: UNC at LBA = 0x02719198 = 40997272

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 e8 00 60 00 00 02 71 91 c0 40 08     15:57:41.308  READ FPDMA QUEUED
  60 00 e0 00 58 00 00 02 71 90 e0 40 08     15:57:41.308  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     15:57:41.304  READ LOG EXT
  60 00 e8 00 58 00 00 02 71 91 c0 40 08     15:57:37.934  READ FPDMA QUEUED
  60 00 e0 00 50 00 00 02 71 90 e0 40 08     15:57:37.934  READ FPDMA QUEUED

Error 1565 [4] occurred at disk power-on lifetime: 5486 hours (228 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 02 71 91 98 40 00  Error: UNC at LBA = 0x02719198 = 40997272

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 e8 00 58 00 00 02 71 91 c0 40 08     15:57:37.934  READ FPDMA QUEUED
  60 00 e0 00 50 00 00 02 71 90 e0 40 08     15:57:37.934  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     15:57:37.930  READ LOG EXT
  60 00 e8 00 50 00 00 02 71 91 c0 40 08     15:57:34.559  READ FPDMA QUEUED
  60 00 e0 00 48 00 00 02 71 90 e0 40 08     15:57:34.559  READ FPDMA QUEUED

Error 1564 [3] occurred at disk power-on lifetime: 5486 hours (228 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 02 71 91 98 40 00  Error: UNC at LBA = 0x02719198 = 40997272

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 e8 00 50 00 00 02 71 91 c0 40 08     15:57:34.559  READ FPDMA QUEUED
  60 00 e0 00 48 00 00 02 71 90 e0 40 08     15:57:34.559  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     15:57:34.555  READ LOG EXT
  60 00 e8 00 48 00 00 02 71 91 c0 40 08     15:57:31.185  READ FPDMA QUEUED
  60 00 e0 00 40 00 00 02 71 90 e0 40 08     15:57:31.185  READ FPDMA QUEUED

Error 1563 [2] occurred at disk power-on lifetime: 5486 hours (228 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 02 71 91 98 40 00  Error: UNC at LBA = 0x02719198 = 40997272

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 e8 00 48 00 00 02 71 91 c0 40 08     15:57:31.185  READ FPDMA QUEUED
  60 00 e0 00 40 00 00 02 71 90 e0 40 08     15:57:31.185  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     15:57:31.181  READ LOG EXT
  60 00 e8 00 40 00 00 02 71 91 c0 40 08     15:57:27.815  READ FPDMA QUEUED
  60 00 e0 00 38 00 00 02 71 90 e0 40 08     15:57:27.815  READ FPDMA QUEUED

Error 1562 [1] occurred at disk power-on lifetime: 5486 hours (228 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 02 71 91 98 40 00  Error: UNC at LBA = 0x02719198 = 40997272

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 e8 00 40 00 00 02 71 91 c0 40 08     15:57:27.815  READ FPDMA QUEUED
  60 00 e0 00 38 00 00 02 71 90 e0 40 08     15:57:27.815  READ FPDMA QUEUED
  60 00 e0 00 30 00 00 02 71 90 00 40 08     15:57:27.813  READ FPDMA QUEUED
  60 00 e0 00 28 00 00 02 71 8f 20 40 08     15:57:27.811  READ FPDMA QUEUED
  60 00 e0 00 20 00 00 02 71 8e 40 40 08     15:57:27.809  READ FPDMA QUEUED

Error 1561 [0] occurred at disk power-on lifetime: 5486 hours (228 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 02 71 67 b8 40 00  Error: WP at LBA = 0x027167b8 = 40986552

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 18 00 58 00 01 a8 f5 5d f8 40 08     15:57:22.151  WRITE FPDMA QUEUED
  61 00 30 00 50 00 01 a8 f5 4d 60 40 08     15:57:22.151  WRITE FPDMA QUEUED
  61 00 30 00 48 00 01 a8 f5 5d c8 40 08     15:57:22.151  WRITE FPDMA QUEUED
  61 00 28 00 40 00 01 a8 f5 5d a0 40 08     15:57:22.151  WRITE FPDMA QUEUED
  61 00 18 00 38 00 01 a8 49 0b 38 40 08     15:57:22.151  WRITE FPDMA QUEUED

Error 1560 [23] occurred at disk power-on lifetime: 5486 hours (228 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 02 71 67 b8 40 00  Error: UNC at LBA = 0x027167b8 = 40986552

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 28 00 98 00 01 9a 29 e3 88 40 08     15:57:18.764  READ FPDMA QUEUED
  60 00 e0 00 90 00 00 02 71 68 98 40 08     15:57:18.764  READ FPDMA QUEUED
  60 00 e0 00 88 00 00 02 71 67 b8 40 08     15:57:18.763  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     15:57:18.760  READ LOG EXT
  60 00 28 00 88 00 01 9a 29 e3 88 40 08     15:57:15.378  READ FPDMA QUEUED

Error 1559 [22] occurred at disk power-on lifetime: 5486 hours (228 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 02 71 67 b8 40 00  Error: UNC at LBA = 0x027167b8 = 40986552

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 28 00 88 00 01 9a 29 e3 88 40 08     15:57:15.378  READ FPDMA QUEUED
  60 00 e0 00 80 00 00 02 71 68 98 40 08     15:57:15.378  READ FPDMA QUEUED
  60 00 e0 00 78 00 00 02 71 67 b8 40 08     15:57:15.378  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     15:57:15.374  READ LOG EXT
  60 00 e0 00 70 00 00 02 71 68 98 40 08     15:57:12.004  READ FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%      5811         4277199
# 2  Extended offline    Completed: read failure       90%      5763         4277192
# 3  Short offline       Completed without error       00%      5619         -
# 4  Short offline       Completed: read failure       90%      5489         4277192
# 5  Short offline       Completed without error       00%      5401         -
# 6  Extended offline    Completed: read failure       90%      5306         18299056
# 7  Short offline       Completed without error       00%      5239         -
# 8  Short offline       Completed without error       00%      5120         -
# 9  Short offline       Completed without error       00%      4951         -
#10  Extended offline    Completed: read failure       90%      4856         18299056
#11  Short offline       Completed without error       00%      4784         -
#12  Short offline       Completed without error       00%      4545         -
#13  Extended offline    Completed: read failure       90%      4449         18299056
#14  Short offline       Completed without error       00%      4378         -
#15  Short offline       Completed without error       00%      4209         -
#16  Extended offline    Completed: read failure       90%      4114         18299056
#17  Short offline       Completed without error       00%      4042         -
#18  Short offline       Completed without error       00%      3826         -

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.

SCT Status Version:                  3
SCT Version (vendor specific):       258 (0x0102)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    38 Celsius
Power Cycle Min/Max Temperature:     38/38 Celsius
Lifetime    Min/Max Temperature:     27/43 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    478 (475)

Index    Estimated Time   Temperature Celsius
476    2016-01-07 08:25    37  ******************
...    ..( 38 skipped).    ..  ******************
  37    2016-01-07 09:04    37  ******************
  38    2016-01-07 09:05     ?  -
  39    2016-01-07 09:06    38  *******************
...    ..(207 skipped).    ..  *******************
247    2016-01-07 12:34    38  *******************
248    2016-01-07 12:35    37  ******************
...    ..(226 skipped).    ..  ******************
475    2016-01-07 16:22    37  ******************

SCT Error Recovery Control:
           Read:     70 (7.0 seconds)
          Write:     70 (7.0 seconds)

Device Statistics (GP Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            3  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            3  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4        12500  Vendor specific
 
joeschmuck

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
@Bhoot

Your two drives are failing. I would RMA these.

ID's 197 and 200 and the Extended test failures are the indicators here.
 
Bhoot

Bhoot

Patron
Joined
Mar 28, 2015
Messages
241
joeschmuck said:
@Bhoot

Your two drives are failing. I would RMA these.

ID's 197 and 200 and the Extended test failures are the indicators here.
Click to expand...
yes thanks. My Alerts also show the same. But I wouldn't want to buy 2 drives right now. Buy 1 send 1 for RMA. get the 1st RMA'ed and then send second for RMA. Receive that and keep it as a spare. :)
Hope the resilvering doesn't take very long. currently 8x4tb WD reds in raidZ2 giving a total of 20.0 tb ut of which only 7tb free remaining. :/
 
joeschmuck

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
Your resilvering will take a bit of time since your pool is very full. Not sure you can do this where you live but here in the US we can do an Advance Replacement (I think it's called) RMA where WD takes a credit card number from you, places a charge (on hold, not actually applied) on that credit card, and ships you a replacement drive with a return shipping label. So you get the replacement drive, swap it out, put the failed drive into the box and slap on the return label. Once WD get the failed drive back within a certain period of time, they drop the pending charge. Well that is the way it happened for me a few years back. The good thing about it as I received a replacement drive quickly and didn't pay for return shipping costs.

Also, not sure when the last time you ran a Scrub was but you should do it. Also, backup all your important data somewhere. You have 2 drives failing and if a third drive starts having issue, you do risk loosing your data.
 
Bhoot

Bhoot

Patron
Joined
Mar 28, 2015
Messages
241
joeschmuck said:
Your resilvering will take a bit of time since your pool is very full. Not sure you can do this where you live but here in the US we can do an Advance Replacement (I think it's called) RMA where WD takes a credit card number from you, places a charge (on hold, not actually applied) on that credit card, and ships you a replacement drive with a return shipping label. So you get the replacement drive, swap it out, put the failed drive into the box and slap on the return label. Once WD get the failed drive back within a certain period of time, they drop the pending charge. Well that is the way it happened for me a few years back. The good thing about it as I received a replacement drive quickly and didn't pay for return shipping costs.

Also, not sure when the last time you ran a Scrub was but you should do it. Also, backup all your important data somewhere. You have 2 drives failing and if a third drive starts having issue, you do risk loosing your data.
Click to expand...

I'm currently in India. Shifted a lot of personal pics/irreplacable data into WD disks (1tb-6tb external). In India they first arrange for a pick up analyze the disk and then send one back. And well currently a 4tb is costing me about $200/ a piece. My last scrub started 15th december finished on 20th december 2015. The FreeNAS box was off around holidays. With the scrub threshold set to 25 days I think it should start soon on its own.

I just checked the calculator of @Bidule0hm which says around 290h for resilvering at 100 MiB/s.Since I am at about 70% I would still say 10 days for resilver and then I can pull out the second disk and send it for RMA.
 
Last edited:
Status
Not open for further replies.

Similar threads

GWasp
  • Locked
SOLVED Any significant difference between WD Red & Seagate IW?
Replies
5
Views
22K
GWasp
GWasp
deadman36g
  • Locked
Just bought a bundle of stuff for my first FreeNAS build, please tell me if I did well .
Replies
10
Views
1K
HoneyBadger
HoneyBadger
K
  • Locked
First FreeNAS Build - Looking for Approval/Improvements from the Community
Replies
9
Views
2K
Chris Moore
Chris Moore
T
  • Locked
Suggested hardware for iSCSI nas build
Replies
1
Views
765
jgreco
jgreco
tenbriz
  • Locked
Overlook of my (first) build
Replies
3
Views
1K
Inxsible
I
Top