SMART Results help

flyinfitz1

Explorer
Joined
Mar 29, 2013
Messages
91
replaced my old WD Red 4x3TB RaidZ2 array with Seagate Ironwold 4x6TB RaidZ2. Overall Ive been happy with the drives other than they run a little hotter. Can someone take a look at the SMART results? Im concerned about the seek error rate. Seems like all the drives have this high count. Im on FreeNAS-11.3-U3.2 with hardware specs in my signature. Thanks in advance for the help!

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   066   064   044    Pre-fail  Always       -       4373960
  3 Spin_Up_Time            0x0003   092   089   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       20
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   086   060   045    Pre-fail  Always       -       426268715
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       1670
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       20
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       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   062   056   040    Old_age   Always       -       38 (Min/Max 35/43)
191 G-Sense_Error_Rate      0x0032   098   098   000    Old_age   Always       -       4401
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       60
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       441
194 Temperature_Celsius     0x0022   038   044   000    Old_age   Always       -       38 (0 24 0 0 0)
195 Hardware_ECC_Recovered  0x001a   037   001   000    Old_age   Always       -       4373960
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      -       1643 (109 47 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       11427558799
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       27607682594
[\code]
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399

flyinfitz1

Explorer
Joined
Mar 29, 2013
Messages
91

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
You can also use a smartctl switch to convert the values: smartctl -a -v 1,raw48:54 /dev/daX

See this site for the explanation of how that -v works to change the attribute 1 as shown... you could also do it for other attributes like 7 and 195, I suppose.

 

flyinfitz1

Explorer
Joined
Mar 29, 2013
Messages
91
You can also use a smartctl switch to convert the values: smartctl -a -v 1,raw48:54 /dev/daX

See this site for the explanation of how that -v works to change the attribute 1 as shown... you could also do it for other attributes like 7 and 195, I suppose.


Super helpful thanks!
 

flyinfitz1

Explorer
Joined
Mar 29, 2013
Messages
91
You can also use a smartctl switch to convert the values: smartctl -a -v 1,raw48:54 /dev/daX

See this site for the explanation of how that -v works to change the attribute 1 as shown... you could also do it for other attributes like 7 and 195, I suppose.


is this a permanent fix?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
is this a permanent fix?
It's not a "fix" as such, it just allows you to see the human-readable version of that value (which will always be stored in that difficult to read way by the on-disk SMART controller when it performs the tests) when you query the value... means you need to use the -v switch every time if you want to read the output properly.
 
Top