SMART tests do not start

22.12 PR: https://github.com/truenas/middleware/pull/9280

22.02.2 PR: https://github.com/truenas/middleware/pull/9192

I was not aware smartmontools behaved like this.

I'll try that and report back.

Edit: Sorry, I said that I did not know how smartmontools behaved, but, actually I know ; of course, you cannot run two tests on the same drive at the same time. The only layer in the stack I do not really know how it behaves is your middleware.

Moreover, since the web GUI allow you, and does not warn you about potential overlapping in tests, I did not know if your middleware was “queuing” SMART tests or not. BTW, the settings you saw, were the defaults set by the installer, I did not think changes were needed, especially, since again, I do not how your middleware works.

Either way, there is no feedback, neither from smartmontools (obviously, but this cannot be helped), or your GUI/middleware. I know that tests length differs from tests types and drives models, but, I feel there should be some warning, at the very least, when two tests are supposed to be running at the same time. Or maybe queuing the SMART tests, since it is handled by your middleware. Especially since, like said above, these tests were set up like this by default, by the installer (IIRC, it was the TrueNAS-12.0-U3, for this machine).

Anyway, just to be sure, I will report back after the next long SMART test runs successfully (or not).

now I see what the issue is: both long and short tests are scheduled to run on midnight. smartmontools behave the following way (from man smartd.conf):

"As soon as a match is found, the test will be started and no additional matches will be sought for that device and that polling cycle."

So short test is started on every day, and on Sunday that prevents long test from being started. You can reschedule short test to run on all weekdays except Sundays and that'll fix the issue.

Since I had multiple HDDs and HDDs cable issues, there were indeed lots of reboots when trying to troubleshoot and fix the issues (as you can probably tell from the log on the main pool). It is still resilvering.

FYI, since I guess you will see it in the logs: I've also move multiple times the location of /var/log, and there were also other unplanned reboots to address other problems and maintenance tasks.

I've updated a new debug archive.

Edit: In case you would have/need the SMART logs from disks, the only other tests ran on them were done manually, as timestamps should show.