From a Fresh Install or recreating a New configuration file, those are the defaults. If a person is upgrading and has defined a preference in the older config file, that get carried through. It is a way to minimize all teh configuration work when a new version comes out.
And i am working on the Docker right now, I built a container, now what to do with it 
Ahh, I was not positive of the defaults on a new script install since I have been using the script for quite awhile.
Joe,
After updating the script, I’m getting an error in the Cron Job Report.
Exiting Joe's SMART Drive Self-test Script
Collecting Multi-Report Data...
Using mr_sendemail.py
python3: can't open file '//mr_sendemail.py': [Errno 2] No such file or directory
Sendemail had a problem. Check the file log at /sendmail_log
What is odd, is the script works perfectly if I run it manually from a terminal (elevated). So I deleted everything and started fresh.
(As root)
Created a new script directory.
Copied multi-report.sh to this dir
Copied multi-report-config.txt to this dir
Ran the script manually. It ran fine. Email sent successfully.
(In the Admin Console)
Edited the cron job (which runs as root) to point to the new script directory.
Manually ran the cron job, script ran, I get the error above.
All subsequent attempts to run the cron job fail with the error above. Python cannot find the mr_sendemail.py file. The file is in the script directory.
Everything in the script directory is owned by root. There should be no reason it cannot find this file. I can manually run python3 pointing to the py file and it finds the python script but is obviously missing parameters.
I recall seeing somewhere in your docs to put the script in /root. I tried that, same result.
I also edited your bash script to include the full path to the python script and I get a different error.
Sendemail had a problem. Check the file log at /sendmail_log
Current user doesn't have permission in the execution folder: /
Yet, if I run it as root from a terminal
Exiting Joe's SMART Drive Self-test Script
Collecting Multi-Report Data...
Using mr_sendemail.py
Email Sent
I’m stumped!
In cronjob, as mentioned in previous post, before call the script you must cd into the m.r. folder. Can you check?
That was it! Thanks!
So I’ve been using multi-report for many years now. I’m running it on TrueNAS core 13.0-U6.7 and it is started by cron at 8AM every morning.
After upgrading to the latest version of everything, with the new script to do SMART testing, I’ve found that the script never starts a test on my two NVMe drives. All other SMART testing is handled by the TrueNAS middleware, so I set Test_ONLY_NVMe_Drives=“true” in the multi-report configuration file.
The log file in DS_Logs shows:
Joe's SMART Drive Self-test Script - Run: 09 February 08:00:06 AM
Script Version: 1.03 (26 January 2025), TrueNAS Core 13.0-U6.7
Logging Enabled
Testing ONLY NVMe Drives
Short Test Mode:(1) "Short SMART Test on 1 Drive(s) Per Day", Running Week Option, Sorting by: DriveID
Authorized Test Days: Mon, Tue, Wed, Thu, Fri, Sat, Sun
Total Drives Recognized: 2
All Scheduled Drives Complete
Drive(s) previously scheduled to be tested: None
Drives scheduled for testing today: None
Long Test Mode:(1) "Long SMART Test on 1 Drive(s) Per Day", Running Month Option, Sorting by: Serial
Sorting Drive Test Order ...............
Authorized Test Days: Mon, Tue, Wed, Thu, Fri, Sat, Sun
Total Drives Recognized: 2
Drive(s) previously scheduled to be tested: nvme1 nvme0
0 Drive(s) testing today:
NO SHORT TESTS TO RUN
NO LONG TESTS TO RUN
08:00:07: Drive-Selftest Wrapping things up...
Elapsed Time: Program 0 minutes and 1 seconds elapsed.
Saving Log (file name: /mnt/freenas/Scripts/DS_Logs/drive_test_09.txt)
Exiting Joe's SMART Drive Self-test Script
Interestingly, the first time I tried setting this flag, the SMART test script still insisted on trying to test my SSDs and spinning rust drives and I had to add the serial numbers of those drives in the script itself in the Ignore_Drives_List variable to make the script leave them alone.
For now, I’ve simply added a cron job which runs:
nvmecontrol selftest -c 1 nvme0
nvmecontrol selftest -c 1 nvme1
every day at midnight just to avoid getting warnings from multi-report.
@unseen Unfortunately I’m on travel so I will have to wing it until I get home.
You need to set the Short tests to Mode 2, which is a daily test. The NVMe drives “should” get tested then.
The part about the HDD/SSD’s getting tested, Hum… I will look at the script to see what is going on. I have made some changes in version 1.04 of the Drive Selftest script but I don’t think I had that same issue.
Thanks for letting me know, I will address it more when I return home Tuesday.
Thanks, I’ll give that a try!
An update on 25.04 Beta1 with respect for NVMe testing.
The Beta1 is pretty nice and it looked promising for testing of the NVMe drives, the GUI looks good however there is not actual testing going on. I also tried this with Smartmontools pre-7.5 that I build today, it didn’t make any difference.
Hopefully the next release fixes it because right now it makes a person “think” tests will be performed, when they do not.
I have just uploaded to my Github repository both Multi-Report v3.15 and Drive Self-test v1.04.
If you are using Manual Updates (I personally prefer this), run the script with -update_all and you will be asked to update each item individually.
• Added Seagate Drive SCAM Check
• Updated -m switch to include Critical Alarms
• The SMR script is now pulled from my Github repository, for positive control
• Removed Partition Check/Backup from CORE due to security concern (there really wasn’t one but it is easy to remove)
I also inducted a new Drive Troubleshooting Flowchart in the resources which should help you quickly figure out what the problem is. It covers the most common things we see here. There is a small amount of ZFS troubleshooting but only enough to help you decide if it is a ZFS problem, of a Drive problem.
Updated mate, all went as expected. Thanks for your work!
One with a good result, crossing my fingers no one has an issue with the update.
Everything fine over here too. Thanks, Joe!
@Okedokey @awasb and anyone else who updated between yesterday and this posting…
Sorry to do this to you, please run a manual update using -update_all and allow it to update both multi report and drive selftest.
I found one tiny irritation in each file, both unrelated and not an operational i ssue, and you may never notice it or see it based on your settings, but it was a minor error in the SMR message and in the SCRUB message. As I said, irritations to me, not an operational issue. But if you run the update, you can download the updated versions. Not enough to push a full change.
As for other possible updates, one person reported that a USB interface was not allowing smartctl to access the drive. He did not blame the script however I am trying to make even USB connected drives function with the script, so I have asked for additional data. Not sure if this will be possible but I will try. But that change will come out as a full version change, if there is a solution.
I’ve updated the update and it worked flawlessly as ever. Thanks!
Updated without issues. Thanks again for the hard work!
The two servers appeared to have updated automatically (they are set to auto) this morning:
MULTI-REPORT UPDATE UPDATED: V 3.15 → V 3.15
DRIVE_SELFTEST UPDATE UPDATED: V1.04 → V1.04MULTI-REPORT UPDATE UPDATED: V 3.15 → V 3.15
Since the version did not change I figured it was something minor.
Thanks for the feedback.
That is an odd printout. I will need to check into it some, it should not have said V 3.15 → V 3.15 and the same thing for the second one. It should have said V 3.14 → V 3.15. Maybe I have something in the script off a bit and I did a typo on the version to display. But yes, 3.15 and 1.04 just came out late yesterday.
Damn, something else to test. What version of TrueNAS are you running? I prefer to test using the same software when I can.
Updated again. Still running strong! 
@joeschmuck What version of TrueNAS are you running? I prefer to test using the same software when I can.
Here is the email header from one of the servers. Both servers are running the same version of Truenas Scale and same version of Multi_Report
Multi-Report v3.14 dtd:2025-01-28 (TrueNAS Scale 24.10.2)
Report Run 23-Feb-2025 Sunday @ 00:00:08
Total Memory: 125Gi, Used Memory: 101Gi, Free Memory: 16Gi, Swap Used: 0B
System Uptime: 21 days, 18:57:06.834146
Script Execution Time: 3 Minutes : 13 Seconds
MULTI-REPORT UPDATE UPDATED: V 3.15 → V 3.15
DRIVE_SELFTEST UPDATE UPDATED: V1.04 → V1.04