Smart Test question on command 'smartd -q showtests'

[Paul5]

I just noticed that smart tests have not been done in years, I'm assuming an upgrade killed them. 0 to 173 hours to now manual one of 15000 odd hours so in trying to learn I entered this command found in Truenas Tutorial https://www.truenas.com/docs/core/coretutorials/tasks/runningsmarttests/ to see if there any schedules not listed in the GUI:

To verify the schedule is saved, you can open the shell and enter smartd -q showtests.

But instead of verifying any schedules I assume it created some and what is more strange to me is the 90 type S tests for ada0 below, it seems to be picking on ada0 though it's fine:

root@truenas:~ # smartd -q showtests
smartd 7.2 2021-09-14 r5236 [FreeBSD 13.1-RELEASE-p7 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

Opened configuration file /usr/local/etc/smartd.conf
Configuration file /usr/local/etc/smartd.conf parsed.

Omitted information

Next scheduled self tests (at most 5 of each type per device):
Device: /dev/ada0, will do test 1 of type S at Wed Jul 5 00:13:50 2023 AWST
Device: /dev/ada0, will do test 2 of type S at Thu Jul 6 00:13:50 2023 AWST
Device: /dev/ada0, will do test 3 of type S at Fri Jul 7 00:13:50 2023 AWST
Device: /dev/ada0, will do test 4 of type S at Sat Jul 8 00:13:50 2023 AWST
Device: /dev/ada0, will do test 5 of type S at Sun Jul 9 00:13:50 2023 AWST

Totals [Tue Jul 4 21:13:50 2023 AWST - Mon Oct 2 21:13:50 2023 AWST]:
Device: /dev/ada1, will do 0 tests of type L
Device: /dev/ada1, will do 0 tests of type S
Device: /dev/ada1, will do 0 tests of type C
Device: /dev/ada1, will do 0 tests of type O
Device: /dev/ada2, will do 0 tests of type L
Device: /dev/ada2, will do 0 tests of type S
Device: /dev/ada2, will do 0 tests of type C
Device: /dev/ada2, will do 0 tests of type O
Device: /dev/ada0, will do 0 tests of type L
Device: /dev/ada0, will do 90 tests of type S
Device: /dev/ada2, will do 0 tests of type L
Device: /dev/ada2, will do 0 tests of type S
Device: /dev/ada2, will do 0 tests of type C
Device: /dev/ada2, will do 0 tests of type O

*********************************************************************************
Why were these tests created and why 90 tests just on one disk.

 

[sretalla]

OK, so I have a server with a lot of disks in it... my output is similar, except I see the 90 for each of the disks (I assume this means 90 short tests will be run in the next 90 days), which makes sense as I do a short test just after midnight every day.

I also see for each of the disks that 3 long tests will be run in the next 90 days (makes sense since I do long tests every 30 days).

What your output is telling you is that only ada0 is set for any tests. Did you make sure to select each disk in the list (or did you select the option for all disks)?

 

[Paul5]

First this is curiosity, no real concern to me.

Chain of events leading up to me asking about this:

1-looking around 'Storage > Disks' and noticed one disk with 173 hours. All my disks are > 5 years so 173 hours is way to low.
2-Checked Smart tests are on for each disk, 'Storage > Disks > ada? > Enable Smart > True': all good
3-Checked 'Services > Smart service' is on: all good
4-Checked 'Tasks > S.M.A.R.T Tests' and found two, one 'Offline' and one 'Short' but no disks selected. So no tests being done.
5-I then ran on the Shell 'Smartctl -t short /dev/XXX' on all the disks and Smart was updated, example 173 hours up to 15XXX hours or so.

I did a bit of reading and found the command 'smartd -q showtests' Note: no tests are in effect as in '4' above for over 5 years. which is what I found strange as to why it generated tests for ada0, specifically with the number 90 as shown in my original post.

OK, so I have a server with a lot of disks in it... my output is similar, except I see the 90 for each of the disks (I assume this means 90 short tests will be run in the next 90 days), which makes sense as I do a short test just after midnight every day.

I also see for each of the disks that 3 long tests will be run in the next 90 days (makes sense since I do long tests every 30 days).

What your output is telling you is that only ada0 is set for any tests. Did you make sure to select each disk in the list (or did you select the option for all disks)?

sretalla you may want to check your smart tests are actually working, see my results below.

If you look at the output of 'smartctl -a /dev/ada0' below it looks like all 90 tests where done consecutively. Remember prior to 'smartd -q showtests' no tests have been done in over 5 years with an hour reading of 173. I now possibly got 90 tests after invoking 'smartd -q showtests' in a matter of minutes. Those hour readings look strange; 15880 to 15967 in minutes.

Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 15967 -
# 2 Short offline Completed without error 00% 15957 -
# 3 Short offline Completed without error 00% 15952 -
# 4 Short offline Completed without error 00% 15939 -
# 5 Short offline Completed without error 00% 15938 -
# 6 Short offline Completed without error 00% 15937 -
# 7 Short offline Completed without error 00% 15934 -
# 8 Short offline Completed without error 00% 15929 -
# 9 Short offline Completed without error 00% 15923 -
#10 Short offline Completed without error 00% 15919 -
#11 Short offline Completed without error 00% 15914 -
#12 Short offline Completed without error 00% 15901 -
#13 Short offline Completed without error 00% 15895 -
#14 Short offline Completed without error 00% 15885 -
#15 Short offline Completed without error 00% 15882 -
#16 Short offline Completed without error 00% 15880 -


6-I deleted the tests in 4 'Tasks > S.M.A.R.T Tests' that had no disks selected
7-I created two new tests for all disks in 'Tasks > S.M.A.R.T Tests' on Long and one Short encompassing all disks.

8-I ran 'smartd -q showtests' and now it reflects the tests I created with all disks to be tested over the next 30 days.


Next scheduled self tests (at most 5 of each type per device):
Device: /dev/ada1, will do test 1 of type L at Fri Jul 7 21:05:37 2023 AWST
Device: /dev/ada2, will do test 1 of type L at Fri Jul 7 21:05:37 2023 AWST
Device: /dev/ada0, will do test 1 of type L at Fri Jul 7 21:05:37 2023 AWST
Device: /dev/ada3, will do test 1 of type L at Fri Jul 7 21:05:37 2023 AWST
Device: /dev/ada1, will do test 1 of type S at Tue Jul 11 21:05:37 2023 AWST
Device: /dev/ada2, will do test 1 of type S at Tue Jul 11 21:05:37 2023 AWST
Device: /dev/ada0, will do test 1 of type S at Tue Jul 11 21:05:37 2023 AWST
Device: /dev/ada3, will do test 1 of type S at Tue Jul 11 21:05:37 2023 AWST
Device: /dev/ada1, will do test 2 of type L at Fri Jul 14 21:05:37 2023 AWST
Device: /dev/ada2, will do test 2 of type L at Fri Jul 14 21:05:37 2023 AWST
Device: /dev/ada0, will do test 2 of type L at Fri Jul 14 21:05:37 2023 AWST
Device: /dev/ada3, will do test 2 of type L at Fri Jul 14 21:05:37 2023 AWST
Device: /dev/ada1, will do test 2 of type S at Tue Jul 18 21:05:37 2023 AWST
Device: /dev/ada2, will do test 2 of type S at Tue Jul 18 21:05:37 2023 AWST
Device: /dev/ada0, will do test 2 of type S at Tue Jul 18 21:05:37 2023 AWST
Device: /dev/ada3, will do test 2 of type S at Tue Jul 18 21:05:37 2023 AWST
Device: /dev/ada1, will do test 3 of type L at Fri Jul 21 21:05:37 2023 AWST
Device: /dev/ada2, will do test 3 of type L at Fri Jul 21 21:05:37 2023 AWST
Device: /dev/ada0, will do test 3 of type L at Fri Jul 21 21:05:37 2023 AWST
Device: /dev/ada3, will do test 3 of type L at Fri Jul 21 21:05:37 2023 AWST
Device: /dev/ada1, will do test 3 of type S at Tue Jul 25 21:05:37 2023 AWST
Device: /dev/ada2, will do test 3 of type S at Tue Jul 25 21:05:37 2023 AWST
Device: /dev/ada0, will do test 3 of type S at Tue Jul 25 21:05:37 2023 AWST
Device: /dev/ada3, will do test 3 of type S at Tue Jul 25 21:05:37 2023 AWST
Device: /dev/ada1, will do test 4 of type L at Fri Jul 28 21:05:37 2023 AWST
Device: /dev/ada2, will do test 4 of type L at Fri Jul 28 21:05:37 2023 AWST
Device: /dev/ada0, will do test 4 of type L at Fri Jul 28 21:05:37 2023 AWST
Device: /dev/ada3, will do test 4 of type L at Fri Jul 28 21:05:37 2023 AWST
Device: /dev/ada1, will do test 4 of type S at Tue Aug 1 21:05:37 2023 AWST
Device: /dev/ada2, will do test 4 of type S at Tue Aug 1 21:05:37 2023 AWST
Device: /dev/ada0, will do test 4 of type S at Tue Aug 1 21:05:37 2023 AWST
Device: /dev/ada3, will do test 4 of type S at Tue Aug 1 21:05:37 2023 AWST
Device: /dev/ada1, will do test 5 of type L at Fri Aug 4 21:05:37 2023 AWST
Device: /dev/ada2, will do test 5 of type L at Fri Aug 4 21:05:37 2023 AWST
Device: /dev/ada0, will do test 5 of type L at Fri Aug 4 21:05:37 2023 AWST
Device: /dev/ada3, will do test 5 of type L at Fri Aug 4 21:05:37 2023 AWST
Device: /dev/ada1, will do test 5 of type S at Tue Aug 8 21:05:37 2023 AWST
Device: /dev/ada2, will do test 5 of type S at Tue Aug 8 21:05:37 2023 AWST
Device: /dev/ada0, will do test 5 of type S at Tue Aug 8 21:05:37 2023 AWST
Device: /dev/ada3, will do test 5 of type S at Tue Aug 8 21:05:37 2023 AWST

Totals [Wed Jul 5 10:05:37 2023 AWST - Tue Oct 3 10:05:37 2023 AWST]:
Device: /dev/ada1, will do 0 tests of type L
Device: /dev/ada1, will do 12 tests of type S
Device: /dev/ada1, will do 0 tests of type C
Device: /dev/ada1, will do 0 tests of type O
Device: /dev/ada1, will do 13 tests of type L
Device: /dev/ada1, will do 0 tests of type S
Device: /dev/ada1, will do 0 tests of type C
Device: /dev/ada1, will do 0 tests of type O
Device: /dev/ada2, will do 0 tests of type L
Device: /dev/ada2, will do 12 tests of type S
Device: /dev/ada2, will do 0 tests of type C
Device: /dev/ada2, will do 0 tests of type O
Device: /dev/ada2, will do 13 tests of type L
Device: /dev/ada2, will do 0 tests of type S
Device: /dev/ada2, will do 0 tests of type C
Device: /dev/ada2, will do 0 tests of type O
Device: /dev/ada0, will do 0 tests of type L
Device: /dev/ada0, will do 12 tests of type S
Device: /dev/ada0, will do 0 tests of type C
Device: /dev/ada0, will do 0 tests of type O
Device: /dev/ada0, will do 13 tests of type L
Device: /dev/ada0, will do 0 tests of type S
Device: /dev/ada0, will do 0 tests of type C
Device: /dev/ada0, will do 0 tests of type O
Device: /dev/ada3, will do 0 tests of type L
Device: /dev/ada3, will do 12 tests of type S
Device: /dev/ada3, will do 0 t

So whilst this is all curiosity.'smartd -q showtests' originally created a test with 90 consecutive tests for the first disk when it should have just displayed 'No Tests Scheduled for any disk'

Again, sretalla you may want to check yours for as above with my new output their is no 90 and it is also over a 30 day period and not 90 days as you stated.

Interesting?

 

[sretalla]

Thanks for the concern. There's nothing wrong with my SMART tests... they run daily as expected.

I am keeping an eye on it with the Multi_report from @joeschmuck

multi_report.sh version for Core and Scale

Multi-Report Tool to chart and record statistical data on your drives. This will email the results to the end user. This will also send alerts via email as well.

www.truenas.com

 

[Paul5]

Thanks for the concern. There's nothing wrong with my SMART tests... they run daily as expected.

I am keeping an eye on it with the Multi_report from @joeschmuck

multi_report.sh version for Core and Scale

Multi-Report Tool to chart and record statistical data on your drives. This will email the results to the end user. This will also send alerts via email as well.

www.truenas.com

No worries and thanks.