Scrub and SMART Scheduling question

[eddie200112]

So ive been running myfreeNAS rig for a few months now and I don't know if a scrub or Smart Test have ever run. I thought it would email me the results or to let me know it completed but nothing. I do get the emails for my temp alerts, updates etc though. Is there a way to check to make sure they have completed? A history or something?

Also attached below is my schedule for the Scrub. Have I set it up correctly? I believe I set it up to run at 3:00AM every 2nd and 17th of the months with a threshold of 35 days. I assume threshold means if a scrub hasn't been in 35 days it will do one right?

Thanks!

 

[DrKK]

Scrub schedule looks good.

If you want to see if your scrubs ran, and what the result was:

Code:

[root@dylarama] ~# zpool status
  pool: freenas-boot
state: ONLINE
  scan: scrub repaired 0 in 0h10m with 0 errors on Mon Jul  6 03:55:24 2015
config:

  NAME  STATE  READ WRITE CKSUM
  freenas-boot  ONLINE  0  0  0
  mirror-0  ONLINE  0  0  0
  da0p2  ONLINE  0  0  0
  da1p2  ONLINE  0  0  0

errors: No known data errors

  pool: tank
state: ONLINE
  scan: scrub repaired 0 in 0h35m with 0 errors on Fri Jul  3 00:35:55 2015
config:

  NAME  STATE  READ WRITE CKSUM
  tank  ONLINE  0  0  0
  raidz1-0  ONLINE  0  0  0
  gptid/00b5a6d9-8744-11e4-9958-002590466aa9  ONLINE  0  0  0
  gptid/01c0e17b-8744-11e4-9958-002590466aa9  ONLINE  0  0  0
  gptid/0280881d-8744-11e4-9958-002590466aa9  ONLINE  0  0  0

errors: No known data errors
[root@dylarama] ~#

Note that it says "scan: scrub repaired 0 in {time} with {N errors} on {date}", for each pool. You're looking for N==0, obviously. Note that this gentleman's pool is quite empty, so the scrub of his main tank took only 35 minutes. Typically, you can expect a scrub on fairly good condition WD reds (and this will depend on several factors) to take about 40-80 minutes per TB of stored file. This gentleman has about 400GB stored, hence, 35 minutes is about right.

For the SMART tests:

Code:

[root@dylarama] ~# smartctl -a /dev/ada0
smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p16 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:  Western Digital Red
Device Model:  WDC WD30EFRX-68EUZN0
Serial Number:  {CENSORED}
LU WWN Device Id: 5 0014ee 20a9ece8f
Firmware Version: 80.00A80
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: 3.0 Gb/s)
Local Time is:  Thu Jul  9 03:18:17 2015 EDT
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.
.
.
. {bunch of stuff skipped}
.
.
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%  4819  -
# 2  Short offline  Completed without error  00%  4651  -
# 3  Short offline  Completed without error  00%  4603  -
# 4  Extended offline  Completed without error  00%  4584  -
# 5  Short offline  Completed without error  00%  4436  -
# 6  Short offline  Completed without error  00%  4268  -
# 7  Short offline  Completed without error  00%  4100  -
# 8  Short offline  Completed without error  00%  3932  -
# 9  Short offline  Completed without error  00%  3860  -
#10  Extended offline  Completed without error  00%  3840  -
.
.
.

You will receive an email from these procedures ONLY IF a problem is found. Note line 29-31 tell you the SMART tests were fine, and at the bottom there is shows you which SMART test was run, and when, as measured in the hours of runtime since inception.

 

[eddie200112]

OK Thanks! looks like the last scrub occurred on July 2nd as it should have. I did get an error on the boot scrub it says that "One or more devices are configured to use a non-native block size.
Expect reduced performance."

But it does not say that for my main volume.
Anyone knows if that's a major problem or how to fix it? it says to replace the drives..

 

[Robert Trevellyan]

I assume threshold means if a scrub hasn't been in 35 days it will do one right?

Right, which could be considered rather a long interval. You might consider reducing it to below 15 days to allow it to run on your set schedule. I have my interval set to 1 day and a bi-monthly schedule

on the boot scrub it says that "One or more devices are configured to use a non-native block size.

Can't see why that would be a problem for the boot volume, but if seeing the message troubles you, I would expect the following procedure to resolve it:

1. Save your configuration.
2. Wipe the boot device(s).
3. Clean install FreeNAS.
4. Restore your saved configuration.

My assumption is that FreeNAS will set the proper block size when it formats the device(s) during the clean install.

 

[eddie200112]

Will this delete all my data on my volumes?

 

[danb35]

No, it will not affect your data.

 

[SweetAndLow]

Right, which could be considered rather a long interval. You might consider reducing it to below 15 days to allow it to run on your set schedule. I have my interval set to 1 day and a bi-monthly schedule

Can't see why that would be a problem for the boot volume, but if seeing the message troubles you, I would expect the following procedure to resolve it:

1. Save your configuration.
2. Wipe the boot device(s).
3. Clean install FreeNAS.
4. Restore your saved configuration.

My assumption is that FreeNAS will set the proper block size when it formats the device(s) during the clean install.

Make sure to have a backup of your configuration and encryption keys if you used encryption.