Long SMART tests?

[rungekutta]

Hi guys,
So I just installed FreeNAS on my new SuperMicro X11 build. Been reading this forum for a while and also the online docs, but no prior experience with FreeNAS otherwise.

I notice the default install/wizard sets up regular scrubs and also short SMART tests, but no long ones. Does that mean the community no longer considers it best practise to run them?

Also, IPMI on Mac seems a little iffy - worth trying, or stick to Windows (for the client)?

Appreciate any thoughts.

 

[rungekutta]

PS setup is 6x3TB in RAIDZ2, boot from SATADOM, 16GB ECC RAM and Intel i3 cpu.

 

[danb35]

No, you should regularly schedule long SMART tests as well. I run them weekly; up to four weeks between tests is probably OK.

Also, IPMI on Mac seems a little iffy - worth trying, or stick to Windows (for the client)?

I've never been able to make the web-based IPMI work satisfactorily on my Mac (specifically, the KVM part; the rest of the system works OK), but the IPMIView application mostly works. It's very slow to launch, though. I've had better results under both Windows and Linux.

 

[jgreco]

Hi guys,
So I just installed FreeNAS on my new SuperMicro X11 build. Been reading this forum for a while and also the online docs, but no prior experience with FreeNAS otherwise.

SMART tests are usually the early warning of developing disk problems. We run a short test on disks every four hours and a long twice a week. Some people have argued that this is excessive, but they can never really point at what exactly the downside is, since SMART tests are designed to give way to user traffic. It might be bad if your pool was so busy the tests never had a hope of completing, I guess, but in years of doing this, haven't seen that.

 

[rungekutta]

Ok thanks, I'll set up some new schedules for this.

I ran manual long tests on all disks just now and somewhat disconcertedly the server suddenly rebooted spontaneously while I was playing around with some MineOS jails. Log file ends abruptly with last message about a minute before. So guessing hardware triggered, but not sure how to diagnose this? IPMI?

I notice temperature running a bit hot on the drives too.

Code:

[xxx@alaska ~]$ sudo smartctl -a /dev/ada5
smartctl 6.5 2016-05-07 r4318 [FreeBSD 10.3-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD30EFRX-68EUZN0
Serial Number:    WD-WCC4N3USVV1J
LU WWN Device Id: 5 0014ee 6064f37a9
Firmware Version: 82.00A82
User Capacity:    3,000,592,982,016 bytes [3.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:    Fri Jun 10 00:04:23 2016 CEST
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:      ( 249)    Self-test routine in progress...
                    90% of test remaining.
Total time to complete Offline
data collection:         (37980) 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:      ( 381) 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       -       4
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       3
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       -       4
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       1
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       3
194 Temperature_Celsius     0x0022   114   113   000    Old_age   Always       -       36
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
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Interrupted (host reset)      60%         3         -

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.

This is after I manually restarted the test again.

 

[jgreco]

And you had no problems during burn-in with the server rebooting?

 

[rungekutta]

Burn-in starts now, really. The long SMART tests were first step. Ran them from FreeNAS and as mentioned was playing around to familiarise myself with the GUI when the server abruptly restarted.

Haven't run memtest yet, will do that too of course (in addition to testing disks).