WD Red Drive issue?

[jasonk]

So my first post as a FreeNAS noob and I need some help.

OS : FreeNas 9.3 Stable
Hardware:

• Lenovo TS140
• Core i3 Processor
• 8GB RAM (4 x 2G ECC UDIMM's)

Storage -

• 2X8GB (Kingston, Not yet but to be mirrored for boot)
• 3x1Tb Hitachi Deskstar 7K1000
• 1 x4Tb WD Red

My initial setup was a Raidz2 pool with the 3x1tb and 1x4tb drives, and my plan over the next couple of months is to replace each of the 1tb drives with a 4tb WD Red so ultimately having 4 x 4tb WD Red drives.

So to my problem, I setup the initial data volume via the manual GUI (due to mismatched drive sizes) and created a cifs share which was viewable from other machines on my network. As a test I started to copy a large dataset of photos (1.6tb) to the new volume and after about an hour my FreeNAS box crashed (Think I saw the word panic in the reboot sequence). Upon reboot it hung at initializing the volume for a very long time ~30 - 45 minutes. Eventually when I was able to get back onto the GUI it showed my volume as degraded, and the 4TB WD drive was out of the volume. Looking the disks in the GUI, it showed up but didn't have an serial number associated with it. I then deleted the volume and did a clean reboot, after which the serial number reappeared on the WD drive. However I don't trust the drive now so I started to run the hard drive burn-in test. I initially ran the smartctl -t short test, it stated it would take 5 minutes but after an hour it hadn't completed so I aborted it and re-ran it. Its been several hours now and its still stuck with 10% remaining?

Do I need to have the drive replaced or is there some other test I should be or can be doing?

Code:

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red (AF)
Device Model:     WDC WD40EFRX-68WT0N0
Serial Number:    WD-WCC4E4AP49LE
LU WWN Device Id: 5 0014ee 2612a77f3
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:    Sun Apr  5 15:12:24 2015 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:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 241) Self-test routine in progress...
                                        10% of test remaining.
Total time to complete Offline
data collection:                (51720) 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:        ( 517) 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          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   253   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   100   253   021    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       2
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   001   001   000    Old_age   Always       -       65535
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       45
10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       2
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       1
194 Temperature_Celsius     0x0022   107   106   000    Old_age   Always       -       45
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   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 1
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
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 1 occurred at disk power-on lifetime: 40 hours (1 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 00 53 4f c2 40  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d8 00 01 4f c2 40 08      01:25:57.869  SMART ENABLE OPERATIONS
  ec 00 01 00 00 00 40 08      01:25:57.479  IDENTIFY DEVICE
  ec 00 01 00 00 00 40 08      01:25:48.748  IDENTIFY DEVICE
  ec 00 01 00 00 00 40 08      01:25:37.587  IDENTIFY DEVICE

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Interrupted (host reset)      10%        40         -
# 2  Short offline       Completed without error       00%        30         -
# 3  Short offline       Completed without error       00%        15         -

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

 

[BigDave]

Try a conveyance test.
This will mainly test the mechanical parts of the drive.
If it fails or will not complete that test, it's more than likely bad.

 

[SweetAndLow]

Your seek error rate seems very high and also you need better cooling for your hdd's. Turn those case fans up!

 

[Ericloewe]

Your seek error rate seems very high and also you need better cooling for your hdd's. Turn those case fans up!

It looks like it maxed out a 16-bit integer.

 

[jasonk]

Thanks for the quick responses. If Im reading this correctly, the conveyance test failed?

Code:

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red (AF)
Device Model:     WDC WD40EFRX-68WT0N0
Serial Number:    WD-WCC4E4AP49LE
LU WWN Device Id: 5 0014ee 2612a77f3
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:    Sun Apr  5 18:24:51 2015 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:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 120) The previous self-test completed having
                                        the read element of the test failed.
Total time to complete Offline
data collection:                (51720) 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:        ( 517) 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          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   253   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   100   253   021    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       2
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   001   001   000    Old_age   Always       -       65535
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       49
10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       2
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       1
194 Temperature_Celsius     0x0022   109   106   000    Old_age   Always       -       43
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   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 1
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
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 1 occurred at disk power-on lifetime: 40 hours (1 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 61 00 53 4f c2 40  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d8 00 01 4f c2 40 08      01:25:57.869  SMART ENABLE OPERATIONS
  ec 00 01 00 00 00 40 08      01:25:57.479  IDENTIFY DEVICE
  ec 00 01 00 00 00 40 08      01:25:48.748  IDENTIFY DEVICE
  ec 00 01 00 00 00 40 08      01:25:37.587  IDENTIFY DEVICE

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Conveyance offline  Completed: read failure       80%        48         6831736
# 2  Short offline       Completed without error       00%        46         -
# 3  Short offline       Interrupted (host reset)      10%        40         -
# 4  Short offline       Completed without error       00%        30         -
# 5  Short offline       Completed without error       00%        15         -

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.

 

[BigDave]

If Im reading this correctly, the conveyance test failed?

Yes, your drive is bad. :(

 

[Starpulkka]

Off question:
I have extra stuff what looks on smart data "When the command that caused the error occurred" so this would have alarmed report on my setup.
But if you dont have extra lookup script, and short smart test gives you a completed without error status. Would a Conveyance smart test be a good idea to setup task done 1 per week?

 

[BigDave]

according to posts I've read in our forum, a conveyance test should only be run when the drive
is brand new.
This tests the mechanical parts of the hard disk to ensure that no handling damage occured.

 

[Bidule0hm]

I agree, you should setup an extended test instead ;)

 

[Starpulkka]

Thanks for response. but yes i already know that (as you even sayed it earlier in this topick), but i thought you had some extra insight experience of conveyance test . =) And i think that i put once a week suggestion as a spike. As my hdd's sit pretty much i have to use some agressive predictive failure analysis.

 

[pschatz100]

Going back to the original post...

A Raid Z2 volume with 3x1 plus 1x4 Tb drives would have a nominal capacity of 2Tb, and a formatted capacity less than that. Correct? Would one expect to be able to load 1.6 Tb of data onto such a volume? ZFS volumes develop problems when they get too full.

 

[Robert Trevellyan]

Would one expect to be able to load 1.6 Tb of data onto such a volume?

According to @Bidule0hm 's calculator, yes, just short of 1.6TB to stay within the recommended 80% ZFS utilization.

 

[joeschmuck]

@jasonk
Your drive, ensure you run an extended test on it. I'm not 100% certain it's bad yet just because you have seek errors which can be normal but you have absolutely no errors for IDs 5, 196, 197, 198, and 200. It is odd that you have a maxed out seek error rate in the first place though. If you replace this drive because of this, I'd recommend you reformat the drive to it's full 4TB capacity and then run an extended SMART test on it. But if you do have a failed drive, WD will replace it if it's still under warranty.

 

[jasonk]

Going back to the original post...

A Raid Z2 volume with 3x1 plus 1x4 Tb drives would have a nominal capacity of 2Tb, and a formatted capacity less than that. Correct? Would one expect to be able to load 1.6 Tb of data onto such a volume? ZFS volumes develop problems when they get too full.

My zfs volume went offline after about 300mb full, yes mb, like I stated initially, this was to start testing the throughput and it's capabilities not a production data copy yet.

 

[joeschmuck]

Have you conducted an extended test on your drives yet?

 

[jasonk]

RMA being processed already.

 

[pschatz100]

According to @Bidule0hm 's calculator, yes, just short of 1.6TB to stay within the recommended 80% ZFS utilization.

A Raid Z2 volume with 3x1 plus 1x4 Tb drives would have a nominal capacity of 2Tb, and a formatted capacity around 1.7 or 1.8Tb. Following the general rule of 80% for ZFS utilization, that would equate to 1.4 Tb of data more-or-less. While exceeding the 80% threshold by a bit will not cause the system to crash, the closer you get to 100% utilization the more problems you will have. I don't think that volume will be big enough for 1.6 Tb of data.

jasonk: Good luck with your RMA. There are some good instructions in the stickies for checking out drives before putting them into production. You might consider running the tests on your existing drives while waiting for the RMA's replacement.

 

[Bidule0hm]

Actually you'll have about 1.6 TB usable (after the 80% rule and co) or about 1.4 TiB so, yes, you can put 1.6 TB of data without a problem ;)

 

[jasonk]

As stated in my initial post, within the next 2 months it will be 4x4tb so its a test bed until that point.