Getting this bounce message from trying to forward on my 3.16 report:
----- Transcript of session follows -----
... while talking to hotmail-com.olc.protection.outlook.com.:
>>> RCPT To:<joeshcmuck2023@hotmail.com>
<<< 550 5.5.0 Requested action not taken: mailbox unavailable (S2017062302). [SJ5PEPF000001E9.namprd05.prod.outlook.com 2025-06-12T17:39:02.498Z 08DDA94C5AEADD60]
550 5.1.1 <joeshcmuck2023@hotmail.com>... User unknown
Cheers.
I canāt type. joeschmuck2023@hotmail.com
I transposed two letters.
EDIT: The -dump email already knows the email address, and you will get the same email I get, so you know what I am looking at.
Ha, I was looking at the mail address inside the script, but my brain re-transposed the letters, so it looked the same to me. 
Re-sent.
Cheers.
@EddieA I also need you to run the script from the command line, ./multi_report.sh -dump email so I can get a copy of all the debug files for version 3.18.
I did get the v3.16 copy, thank you.
That was run before my original reply to you.
How exactly are you sending that mail, because if it appears to come directly from my IP, then the vast majority of mail servers (including hotmail) will bounce it because of the Spanhaus PBL blocking.
Cheers.
Let me reconfigure TrueNAS settings to use my external ISP mail server.
Cheers.
Hello!
I seem to have come across a few issues with the ānewestā version (3.18), mainly where the table on the email misses a few drives and the spinning rust header/Device ID is as wide as the entirety of the SSD table (making the whole thing ridiculously wide).
I reinstalled the script from scratch, and then the -config flag wasnāt creating a new multi_report_config.txt file.
I used an old version of the config file (from 3.16) on 9th June 2025 when it was still working fine (with all drives shown)
So it looks like 3.18 broke the table 
and the 3.18 new install breaks the config creation, AND the table.
(for some reason I canāt include links nor screenshots eitherā¦)
Any tips?
You have a classic failure, unknown yet as to what has caused this.
Please run the script from the command line, logged in as root and run ./multi_report.sh -dump email and this will collect data about the script and what is going on and send it to me. You will also see a copy as well. Once I have the data I can analyze it to see what is going on.
Hey! Scripts run flawlessly, but I get an additional
sudo: process 13297 unexpected status 0x57f
mail, even with hide standard error flagged. Any insight?
I run this as root on my SCALE system.
@Davvo sudo ???
This is a first. Strange that sudo would pop up. I do not use sudo at all in the scripts.
Did this just start to happen with v3.18? After a reboot of TrueNAS, does it still happen? Only reboot TrueNAS when the time works for you. Iām not insinuating it is TrueNAS at fault, this action just clears any temporary files created by the scripts.
Stupid question: Are you sure this sudo message is related to Multi-Report?
Had the same this morning - following the cron job:
cd /path-to-multi_report && ./multi_report.sh
I donāt know since itās the first time I am running the script on SCALE; I am using the GitHub version.
Yes to all other questions; I migrated to SCALE from CORE, and I hold control over the legacy root account.
I hate to say it, I had the /tmp/memory_free.txt error message this morning as well, only on my SCALE system, but never had it before and Iāve been running the same script for over a month. I ran the script again via CRON Job, no issue, rebooted and tried again, and no issue.
Was there a sun spot that got us all?
Very strange. I am curious if there is something going on with BASH, could I be asking too much. Maybe it is time to roll this script into Python? Or just roll back to v3.16.
@Halfang @Davvo
Could you both look in your GUI - Running Jobs (the thing that looks like a notepad top of the GUI, to the left of the Bell icon)
Goto Jobs Page ā now look for the time the CRON job ran, open the drop down. Examine it, does it show you the error message? If yes, please use the Copy button (lower right corner of the window) and then send me a message including that data. Iām looking for commonality and maybe a clue as to what is happening.
Do you know if the error is repeatable?
And an update as I was typing this response. The FARM checks may be failing and causing the issue. If you disable the FARM checks, all might be good again. I still donāt understand how it relates to these errors but I will keep digging.
The easy way to disable FARM checks:
./multi_report.sh -configa Advanced ā t SMR Drive, GPT Partitions, Seagate FARM Checkd or enter disable and press Enter.w to Write your changes, then any key, and x to exit.It is, I installed the script a few days ago and every time the script was run by cronjob I got the error.
Executed CronTask - cd /mnt/NVMe/scripts/ && ./multi_report.sh > /dev/null 2> /dev/null: sudo: process 13297 unexpected status 0x57f
@Davvo Just to clarify how you are running the script:
Here is mine from TrueNAS 25.04.1, your Command line should be cd /mnt/NVMe/scripts && ./multi_report.sh and if it is different, then that is likely the problem. It is different from the CORE command.
Tried it because I miss my report from Core. Followed the instructions, it wonāt write out its config file but it does everything else including emailing me.
Run it the second time, according to the docs, errors out because thereās no config file. 3.18. Itās like it forgets.
Hahah I wish I would have scrolled up and saw this before I blindly launched into 3.18 and hit the brick wall with the config file. Iāll roll back and try again. Glad you posted this.
Sorry for the headaches. I plan to have a fix out soon, meaning unfortunately v3.19, ARG!
Take your time, we know 3.16 works lol.
