Not sure if hard drive failing, or errors are due to power cut

Status
Not open for further replies.

worldroll

Cadet
Joined
Oct 12, 2014
Messages
1
Hi, had a power cut and 20:08 on nov 11th, I don't have any ups.

The next morning at 7:40 i've got a e-mail that the volume is DEGRADED, I can recover as it is raidz2 but I want to make sure that the hard drive is actually bad and the errors arn't due to the power cut.

Code:
# zpool status
  pool: volume1
state: DEGRADED
status: One or more devices are faulted in response to persistent errors.
        Sufficient replicas exist for the pool to continue functioning in a
        degraded state.
action: Replace the faulted device, or use 'zpool clear' to mark the device
        repaired.
  scan: scrub repaired 0 in 3h45m with 0 errors on Sat Nov  1 10:25:17 2014
config:

        NAME                                            STATE     READ WRITE CKSUM
        volume1                                         DEGRADED     0     0     0
          raidz2-0                                      DEGRADED     0     0     0
            gptid/2298696d-5409-11e4-b442-0cc47a30d30c  ONLINE       0     0     0
            gptid/23886c2b-5409-11e4-b442-0cc47a30d30c  ONLINE       0     0     0
            gptid/2455f9fc-5409-11e4-b442-0cc47a30d30c  ONLINE       0     0     0
            gptid/24a303f3-5409-11e4-b442-0cc47a30d30c  ONLINE       0     0     0
            gptid/25c8c654-5409-11e4-b442-0cc47a30d30c  ONLINE       0     0     0
            gptid/26bc7724-5409-11e4-b442-0cc47a30d30c  ONLINE       0     0     0
            gptid/27e41b72-5409-11e4-b442-0cc47a30d30c  ONLINE       0     0     0
            gptid/2940bf49-5409-11e4-b442-0cc47a30d30c  ONLINE       0     0     0
            gptid/2a7dc831-5409-11e4-b442-0cc47a30d30c  FAULTED      3     72     0  too many errors
            gptid/2b8add0e-5409-11e4-b442-0cc47a30d30c  ONLINE       0     0     0

errors: No known data errors


and the smartctl for the faulted drive is

Code:
 smartctl -a /dev/da2
smartctl 6.2 2013-07-26 r3841 [FreeBSD 9.2-RELEASE-p12 amd64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST3000DM001-9YN166
Serial Number:    W1F0BCLG
LU WWN Device Id: 5 000c50 04a44275f
Firmware Version: CC4B
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Nov 12 17:48:07 2014 GMT

==> WARNING: A firmware update for this drive may be available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/223651en

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:                (  575) 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:        ( 339) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x3085) SCT Status supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   111   099   006    Pre-fail  Always       -       35304968
  3 Spin_Up_Time            0x0003   093   092   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1153
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   060   051   030    Pre-fail  Always       -       176138863361
  9 Power_On_Hours          0x0032   092   092   000    Old_age   Always       -       7655
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   099   099   020    Old_age   Always       -       1147
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   094   094   000    Old_age   Always       -       6
188 Command_Timeout         0x0032   099   096   000    Old_age   Always       -       1 1 6
189 High_Fly_Writes         0x003a   099   099   000    Old_age   Always       -       1
190 Airflow_Temperature_Cel 0x0022   065   050   045    Old_age   Always       -       35 (Min/Max 14/37)
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       -       274
193 Load_Cycle_Count        0x0032   090   090   000    Old_age   Always       -       20739
194 Temperature_Celsius     0x0022   035   050   000    Old_age   Always       -       35 (0 13 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      -       7231h+41m+35.740s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       70755668902942
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       256858224801316

SMART Error Log Version: 1
ATA Error Count: 6 (device log contains only the most recent five errors)
        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 6 occurred at disk power-on lifetime: 24 hours (1 days + 0 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 ff ff ff ef 00      02:19:05.893  READ DMA EXT
  27 00 00 00 00 00 e0 00      02:19:05.892  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      02:19:05.884  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      02:19:05.878  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      02:19:05.852  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 5 occurred at disk power-on lifetime: 24 hours (1 days + 0 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 ff ff ff ef 00      02:19:03.025  READ DMA EXT
  27 00 00 00 00 00 e0 00      02:19:03.024  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      02:19:03.016  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      02:19:02.992  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      02:19:02.896  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 4 occurred at disk power-on lifetime: 24 hours (1 days + 0 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 ff ff ff ef 00      02:19:00.152  READ DMA EXT
  27 00 00 00 00 00 e0 00      02:19:00.151  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      02:19:00.143  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      02:19:00.135  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      02:19:00.116  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 3 occurred at disk power-on lifetime: 24 hours (1 days + 0 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 ff ff ff ef 00      02:18:57.276  READ DMA EXT
  27 00 00 00 00 00 e0 00      02:18:57.275  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      02:18:57.267  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      02:18:57.260  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      02:18:57.235  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 2 occurred at disk power-on lifetime: 24 hours (1 days + 0 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 ff ff ff ef 00      02:18:54.399  READ DMA EXT
  27 00 00 00 00 00 e0 00      02:18:54.398  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      02:18:54.390  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      02:18:54.384  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      02:18:54.347  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

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%      7642         -
# 2  Extended offline    Completed without error       00%      7565         -
# 3  Short offline       Completed without error       00%      7485         -
# 4  Short offline       Completed without error       00%      7245         -
# 5  Extended offline    Completed without error       00%      7155         -
# 6  Short offline       Completed without error       00%      7076         -
# 7  Short offline       Completed without error       00%      7014         -

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.
 

rs225

Guru
Joined
Jun 28, 2014
Messages
878
I would say the drive has a defective control board. The error LBA is 0x0fffffff. I had a drive of the same model, that also repeatedly would go offline on a particular LBA, but it did not seem to have such a neat hex address. Finally RMA'd it.

If it were any other model, I might suggest cables or controller port, but moving mine around changed nothing. The ST3000DM001 is cursed.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Yeah, your drive is failing in a "not conventional" way. But that disk definitely needs to be RMA'd and replaced.
 

erturne

Dabbler
Joined
Sep 5, 2013
Messages
19
While you're thinking about it, get an UPS! I have my NAS on an APC BE750RT.
 

DrKK

FreeNAS Generalissimo
Joined
Oct 15, 2013
Messages
3,630
Agreed. I suspect the controller for the drive.

In either case, this drive should not be in your array. The situation will either get worse, or stay the same; either way it will disrupt a ZFS pool.
 
Status
Not open for further replies.
Top