disk dieing? or not?

[Scareh]

Code:

[root@freenas] ~# zpool status
  pool: BigDisk
 state: ONLINE
status: The pool is formatted using a legacy on-disk format.  The pool can
        still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'.  Once this is done, the
        pool will no longer be accessible on software that does not support feature
        flags.
  scan: scrub in progress since Fri Sep 13 13:08:04 2013
        18.3G scanned out of 415G at 112M/s, 1h0m to go
        0 repaired, 4.41% done
config:
 
        NAME                                          STATE     READ WRITE CKSUM
        BigDisk                                       ONLINE       0     0     0
          gptid/9d779ca0-f208-11e2-b905-0015179cb91a  ONLINE       0     0     0

output of smartctl -a /dev/da5 (that being this disk) (note that i'm doing a scrub while taking these commands)

Code:

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   114   099   006    Pre-fail  Always       -       59761504
  3 Spin_Up_Time            0x0003   074   074   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       62
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   067   060   030    Pre-fail  Always       -       6288827
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       1293
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       52
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   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   098   000    Old_age   Always       -       4
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   073   054   045    Old_age   Always       -       27 (Min/Max 26/32)
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       -       39
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       75
194 Temperature_Celsius     0x0022   027   046   000    Old_age   Always       -       27 (0 14 0 0 0)
195 Hardware_ECC_Recovered  0x001a   037   006   000    Old_age   Always       -       59761504
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       -       394
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       252831839814931
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       1586137656
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       3149995878

after i copy pasted this in here i ran the command again

Code:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   114   099   006    Pre-fail  Always       -       79403472
  3 Spin_Up_Time            0x0003   074   074   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       62
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   067   060   030    Pre-fail  Always       -       6289143
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       1293
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       52
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   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   098   000    Old_age   Always       -       4
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   073   054   045    Old_age   Always       -       27 (Min/Max 26/32)
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       -       39
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       75
194 Temperature_Celsius     0x0022   027   046   000    Old_age   Always       -       27 (0 14 0 0 0)
195 Hardware_ECC_Recovered  0x001a   036   006   000    Old_age   Always       -       79403472
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       -       394
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       14392435410195
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       1586144127
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       3198656130

so should i be worried that the disk is dieing or not?
zpool status gives me no errors but the read errors seems to increase exponentially...

 

[Scareh]

kinda funny i see the hardware ECC errors recovered value increasing aswell. and not to mention the amount of hours the head's been flying...
atm : 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 246342144230675
i'm thinking the read outs are a bit erm wrong here xD

 

[cyberjock]

Seagate has their own formula for interpreting the errors and stuff. It's not like WD and every other company where "zero" means none. But your parameters 197 and 198 are both zero, so your disk looks fine to me.

 

[Scareh]

allrighty fair enough, just got worried after i saw the word error and the values behind it go up.
Not that i mind too much on whats on that disk since its not in the raid but still :p
thanks cyberjock

 

[cyberjock]

Yeah, I was a little curious about that myself. Why you'd make a single disk ZFS disk is beyond me. You have no protection from corruption since you have no redundancy. I'd probably go with UFS at that point.

 

[Dusan]

Why you'd make a single disk ZFS disk is beyond me.

Even without redundancy you still have the benefit of snapshoting, integrity checking (checksums) and encryption just to name few reasons.
For example in my system I have a removable drive (actually two of them that I rotate) for off-site backup. Is it a single drive ZFS pool, so that I can just ZFS replicate snapshots to the backup drive. Encryption is also a nice feature to have on an off-site backup drive.

 

[Yatti420]

Integrity checking (checksums) alone saved my hind end once already..

 

[cyberjock]

But that only tells you the file is corrupt. I guess it allows for recovery from backup. But that really doesn't help much if a disk starts failing or something.