Recurring System Alert - false positive or cause for concern?

Status
Not open for further replies.

Suiname

Dabbler
Joined
Dec 5, 2012
Messages
31
I recently had a motherboard failure and had to replace it with a new mobo. My freenas system has now been up and running for a couple weeks, however I keep getting these alerts through the web console:

XGdULBw.png

This happens once or twice a week. When I go into the command line and do a zpool status I get the following output:
Code:
[jt@freenas] /> zpool status
  pool: freenas
 state: ONLINE
status: One or more devices has experienced an unrecoverable error.  An
    attempt was made to correct the error.  Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
    using 'zpool clear' or replace the device with 'zpool replace'.
   see: http://www.sun.com/msg/ZFS-8000-9P
  scan: scrub repaired 36K in 10h5m with 0 errors on Sun Nov  9 10:05:35 2014
config:

    NAME                                            STATE     READ WRITE CKSUM
    freenas                                         ONLINE       0     0     0
     raidz1-0                                      ONLINE       0     0     0
       gptid/e2fcaf82-18ef-11e3-8e05-00012e2f10be  ONLINE       0     0     0
       gptid/e36e3450-18ef-11e3-8e05-00012e2f10be  ONLINE       0     0     0
       gptid/e40ecbde-18ef-11e3-8e05-00012e2f10be  ONLINE       0     0     0
       gptid/e458b6bd-18ef-11e3-8e05-00012e2f10be  ONLINE       0     0     9
       gptid/e4ae15ec-18ef-11e3-8e05-00012e2f10be  ONLINE       0     0     0
       gptid/e509513f-18ef-11e3-8e05-00012e2f10be  ONLINE       0     0     0

errors: No known data errors
[jt@freenas] /> 


If I do a status clear the status goes back to normal and stays that way for several days. Any idea what's going on here?
 

Suiname

Dabbler
Joined
Dec 5, 2012
Messages
31
How can I tell which disk it is? Is it the one with all the checksum errors?
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
It looks like the fourth disk in your RAIDZ vdev is throwing checksum errors, so that seems like a likely candidate to have a problem. Have you enabled the SMART service? Have you enabled (and tested) email reporting? Are you running regular SMART tests?

In the Web GUI, if you go to Storage, then select your pool, then click Volume Status (the button on the bottom row that looks like a blank sheet of paper), it will pull up a page listing your drives by their more common identifiers (most likely adaNpN, where both Ns are numbers). One of them will (or should) be showing checksum errors. Note which disk that is.

Go to the command line and run smartctl -a /dev/adaN, where N is the disk that was reporting checksum errors. Share the results here using code tags, or on pastebin.
 

Suiname

Dabbler
Joined
Dec 5, 2012
Messages
31
So the drives all had smart enabled, but I hadn't setup regular smart tests. I am going to enable that now. Unfortunately when I went in to look just now, none of the drives were showing checksum errors. From the results above, the disk that was having the problem was the 4th, so I assumed it was the same as the drive listed as ada4. I tried matching up the gpids but I couldn't find any place in the gui to do that. Anyways, here's the output of the command run on the 4th disk:
Code:
[root@freenas] ~# smartctl -a /dev/ada4
smartctl 5.43 2012-06-30 r3573 [FreeBSD 8.3-RELEASE-p4 amd64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Deskstar 5K3000
Device Model:     Hitachi HDS5C3020ALA632
Serial Number:    ML0221F3015HMA
LU WWN Device Id: 5 000cca 369c08908
Firmware Version: ML6OA180
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Tue Nov 11 10:43:12 2014 CST
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:  (0x84)    Offline data collection activity
                    was suspended by an interrupting command from host.
                    Auto Offline Data Collection: Enabled.
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:         (23645) seconds.
Offline data collection
capabilities:              (0x5b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    No 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:      ( 394) minutes.
SCT capabilities:            (0x003d)    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     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   135   135   054    Pre-fail  Offline      -       98
  3 Spin_Up_Time            0x0007   151   151   024    Pre-fail  Always       -       364 (Average 361)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       114
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   150   150   020    Pre-fail  Offline      -       27
  9 Power_On_Hours          0x0012   098   098   000    Old_age   Always       -       15745
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       114
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       146
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       146
194 Temperature_Celsius     0x0002   206   206   000    Old_age   Always       -       29 (Min/Max 19/51)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


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.




Anything look suspicious to you?
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Nothing really looks out of line there. The drive has gotten warmer than ideal (it's seen 51 degrees C, preferred max is 40), but nothing looks out of the ordinary otherwise, and I wouldn't expect that to cause the data errors you're seeing.

I'd guess the drive in question would be ada3, since they start counting from 0.
 

Suiname

Dabbler
Joined
Dec 5, 2012
Messages
31
Gotcha. Well here's the output on ada3:

Code:
[root@freenas] ~# smartctl -a /dev/ada3
smartctl 5.43 2012-06-30 r3573 [FreeBSD 8.3-RELEASE-p4 amd64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     Hitachi HDS723020BLE640
Serial Number:    MSN7215P0K6U9T
LU WWN Device Id: 5 000cca 37dc7d3e5
Firmware Version: MX4OAAB0
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Tue Nov 11 10:58:26 2014 CST
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:  (0x84)    Offline data collection activity
                    was suspended by an interrupting command from host.
                    Auto Offline Data Collection: Enabled.
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:         (15300) seconds.
Offline data collection
capabilities:              (0x5b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    No 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:      ( 255) minutes.
SCT capabilities:            (0x003d)    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     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   139   139   054    Pre-fail  Offline      -       70
  3 Spin_Up_Time            0x0007   135   135   024    Pre-fail  Always       -       267 (Average 295)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       72
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   126   126   020    Pre-fail  Offline      -       32
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       9431
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       72
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       118
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       118
194 Temperature_Celsius     0x0002   206   206   000    Old_age   Always       -       29 (Min/Max 19/55)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


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.

 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Nothing looks out of line there either, though again it's gotten too warm in the past. I wouldn't consider ZFS scrub errors to be "nothing to worry about", but I don't see an indication of problems with what you're posting so far, either. You definitely want to enable SMART tests (a common schedule is a short test daily and a long test every week or two), and that may give some further information.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
If your disks get too hot they can and often do start having errors that disappear when the drive is cooler. First thing I'd do is add more cooling to your disks. Second thing I'd do is run long tests on all of your disks and check all of the SMART info. The third thing I'd do is run a scrub and make sure your disks don't get too hot. Then let the scrub finish and see how many errors you get.
 

Suiname

Dabbler
Joined
Dec 5, 2012
Messages
31
Thanks for everyone's help with this. It must have been a temperature related problem, I turned up my fans and the drop in temperature in general probably helps as well, haven't seen this come back. I've enabled daily SMART testing and turned on alerting, so I'll know right away if there's another problem.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Daily SMART testing is unnecessary. Please read my sticky on SMART monitoring and SMART testing. ;)
 

alexg

Contributor
Joined
Nov 29, 2013
Messages
197
It could also be bad SATA cable or memory going bad. Are you using ECC memory?
 
Status
Not open for further replies.
Top