SMART reporting null

TrueNAS General
1

The command:

midclt call disk.smart_test LONG ’{serial_lunid}WPV077HZ_50xcccx", “{serial_lunid}WPV077RD_50xcccv”, "{serial_lunid}ZAD02S2L_50xcccv”, “{serial_lunid}ZAD54T3Q_50xcccv”, “{serial_lunid}ZAD54V66_50xcccv”, “{serial_lunid}ZAD7L00Q_50xccccv”]’

Produced the following output:

null

I received the above email alert from my TrueNAS box this morning.

I’ve got that as a cron job running a short test weekly and a long test monthly.

Under 25.10, with the changes in smart reporting, I’m now getting the above output. Should I just ignore the null message, and assume the tests are still being run and reported through my scrutiny instance?

2

Never assume anything. Verify the Power On Hours match the time stamp for the SMART tests. That is how you will know if tests are being performed.

If the tests are being performed, then you can ignore.

Do you have Hide STDOUT checked? After verification, check that box.

1 Like
3

Agreed!

How do I check time stamps in Scrutiny? The “last updated” time it shows is simply when I just restarted the app (having added a Timezone environment variable). My cron job ran at midnight last night.

4

I don’t think you can. You can view the power on hours, but I don’t think you can view the SMART tests performed.

5

Hmmm. I can’t find anything anywhere. My drives have been powered on for “2 years” according to scrutiny…not exactly precise information!

I find it surprising that Scrutiny doesn’t show when the SMART data is it displaying so prettily is from. Well, maybe it sort of does. Under details > history, it does give the time it’s reporting against.

But that’s much more regularly than my SHORT and LONG tests, so I don’t think it’s reporting those results.

Perhaps SHORT & LONG tests aren’t needed with Scrutiny?

6

That isn’t the way SMART works. I believe Scrutiny only “monitors”, I do not think it does any testing. TrueNAS Goldeye “monitors” as well, it just doesn’t show you the data in a GUI, but it emails you and puts notification in the GUI alert section when if detects an error from smartd