Thank you for your extraordinary efforts, they are heavily appreciated.
3 Likes
Well, the fun never stops. I still plan to make it official on Saturday however if you are running 24.10.1, you will not get any emails if you run via CRON job. I and a few others have been unable to get it to run. 24.10.0.2 and below are able to run the scripts without issue.
Sorry for the bad news. But you can run it from the CLI in 24.10.1. Strange crap happening.
2 Likes
Heya @joeschmuck, I hope you are well.
Long time user of the Multi-Report. Today I received the following error on one of the long SMART tests:
# 1 Background long Failed in segment --> 110 31617 20607409912 [0x3 0x5d 0x1]
TrueNAS also emailed me an alert:
New alerts:
* Device: /dev/da4, Self-Test Log error count increased from 0 to 1.
In the Multi-Report email, I can’t specifically see any error counts increase in the SMART data…
Drive failed the smart test, time to swap it.
So the error messages came from TrueNAS?
If you were to run Multi-Report, it should indicate you have a failure. If it does not, please send me a -dump emailextra if you do not mind. I’d like to see where I missed the mark.
Just checking, 3.1 is not out yet, is it?
You can download it from GitHub but it’s still a Beta as it hasn’t been rolled out yet.
1 Like
You can download a better ‘Beta’ from here.
This is the current Beta for now, scroll to the bottom of the thread to find the most current version. Just so everyone knows, there are some folks still having email issues but I suspect these are unique situations.
However there is still an email problem which we are working to rectify that affects 24.10.1. Look for that to come out “soon”. Soon being I really hope by the end of this week, but don’t hold your breath. The Beta has all the features so if there are any problems, feel free to report them to me. If it is email based, don’t report those to me until after the email fix is done.
3 Likes
Easy, run smartctl -x /dev/da4 and post the output. There are almost always more factors to consider. This will provide all the data to recommend the next step.
Stupid question, I want to use your beta multi_report_v3.1_2025_01_03_BETA.txt, I´m now using v3.1. To use the new one do I change the name of the multi_report.sh to multi_report.sh.bak and the new multi_report_v3.1_2025_01_03_BETA.txt rename it multi_report.sh, editing first the username and password in the script? Do I need to run the configuration again?
1 Like
Not stupid. v3.1 is still in Beta as you see, and Beta 6 will be out today. This should bring back all the email functions/features we previously had.
The script name that you run should be multi_report.sh, so you will need to rename the Beta file to this name. You could use a different name however for simplicity it is nice to keep a standard name. As for the .bak files, if you don’t need them, delete them. All the current Multi-Report files are on github so a person can roll back to a previous version if they desire.
Thank you, do I have to run the configuration again?
No sir, no need to run the configuration again unless you wanted to make some changes to the new features. The main one is how the drives are now tested. I am likely to change some of the default values based on what I hear back from people testing the Beta out. If you open the file multi_report_config.txt and scroll to the bottom, you will see some new option for drive testing. This is helpful for those who would rather not let TrueNAS GUI configure when a drive is tested. Hopefully the notes in the config file are good to explain what is going on, but I do have a document which explains it in greater detail.
Here is the github link, look for the Drive Selftest User Guide.
Ok, so it doesn’t. I downloaded the beta 6 and it detected the configuration and its adjusting itself for the new script. It give an error in the end that the github missing for file sendmail.py, so I downloaded the mr_sendmail,py from github, rename it to sendmail.py and run again, see what happens.
My configuration is as follow,
Short Test Mode:(1) “Short SMART Test on 4 Drive(s) Per Day”, Running Week Option, Sorting by: Week
Long Test Mode:(2) “Long SMART Test All Drives”, Running Week Option, No Sorting
Is it ok to have the script run the smart tests or create a cron in truenas to run tests and use the script to send the data?
I just run the script again, no errors now, and I get the email. THANK YOU
1 Like
Hum, not sure what is happening here, I looked at the script, it looks like it should be working fine. I did have a few typo’s in an earlier version but the Beta6 I posted didn’t seem to have those issues. There was no “sendmail.py” words in the script.
I will change the link above to reflect just the thread vice a single posting since I am issuing many Betas. I am working Beta7 now, but it is a cleanup version and will not be out for a few days, no real changes from Beta6, except some automatic version checking on drive_selftest.sh and mr_sendemail.py. I will also be using @oxyde github account to pull the sendemail.py script since he is maintaining it.
Works fine if I run the script from the shell, From the cron I get the error below, my command is
cd /mnt/HDD/apps/scripts && ./multi-report/multi_report.sh
TrueNAS does not support sendmail function, using curl.
Multi-Report v3.1Beta6 dtd:2025-01-11 (TrueNAS Scale 24.10.1)
Checking for Updates
Current Version 3.1Beta6 – GitHub Version 3.0.7
No Update Required
Running Drive Self-test Script: /mnt/HDD/apps/scripts/multi-report/drive_selftest.shJoe’s SMART Drive Self-test Script - Run: 12 January 09:11:40 PM
Script Version: 1.0 (10 December 2024), TrueNAS Scale 24.10.1Logging Enabled
Using External Configuration FileShort Test Mode:(1) “Short SMART Test on 4 Drive(s) Per Day”, Running Week Option, Sorting by: Week
NO DRIVES TO TEST THIS PERIODLong Test Mode:(2) “Long SMART Test All Drives”, Running Week Option, No Sorting
21:11:44.40: Main Program End, Wrapping things up…
Elapsed Time: Program 0 minutes and 3.63 seconds elapsed.Your 130 Second Delay, Please Standby…
Saving Log (file name: /mnt/HDD/apps/scripts/multi-report/DS_Logs/drive_test_12.txt)
Exiting Joe’s SMART Drive Self-test Script
Collecting Report Data…
Downloading @oxyde’s sendemail.py script to send emails…
Sending Email Courtesy of @oxyde
sendemail.py was a reference of olds script we shared on the other thread, shouldn’t be mentioned in your code @joeschmuck, really strange behaviour.
@smic717394 do you have set root as account of the cronjob?
@smic717394 The portion you listed looks good, did you get an email as well?