As the system scrub only takes a couple of minutes, why don't you just set it to 14 days and forget about it?
Mine is set to 5.
Thank you all for responding to my query. If there's one thing I've come to appreciate here, it's that there is always something new to learn and there is a wealth of knowledge in the collective.Brilliant! A big Thank You. Just one question. I note from your schedule that your boot scrub is scheduled for day 1 and 16. How have you managed that? I understand you can set an automatic scrub interval (default 35 days) , but I didn't think that specifying specific days was possible.
...there is a wealth of knowledge in the collective.
We are the Borg. You will be assimilated. Resistance is futile.
Let me know if anyone else has suggestions/requests.
Having upgraded a FreeNAS server from 9.10.2-U5 to 11.0 on the w/e, I noticed a slight change in the formatting of the report. Check out the Temperature column in the image below. I confirmed the change by running the report on a second server on 9.10.2-U5 and then re-running the report again after upgrading the second server to 11.0. Something in the latest version of FreeNAS has broken (slightly) the formatting of the report.Let me know if anyone else has suggestions/requests.
Are you able to send a test email from the GUI? Are you getting other system generated reports via email?I'm wondering if someone can give me a hint to why my smart report/backup cron job is not working.
I recently transferred my drives into a new system and imported the volume into a fresh install of freenas 11. this script was working just fine on the previous machine.
when I test the script via ssh it works just fine, I get one email with a report and a second with a confer backup.
but when I try to test the cron job using the "Run Now" button created the tmp file for the report email but doesn't send it.
the location of the script is "/mnt/Media/James/scripts/report.sh" and that is what is in the Command section of the cron job
any suggestions?
Curious...Under FreeNAS 11.0, if I run the report from ssh, there are no formatting errors. However, when submitted as a cron job, the formatting error appears. This behaviour did not exist in FreeNAS 9.10.2-U5. Wondering if 11.0 has introduced a bug that is highlighted by the scheduler?Having upgraded a FreeNAS server from 9.10.2-U5 to 11.0 on the w/e, I noticed a slight change in the formatting of the report. Check out the Temperature column in the image below. I confirmed the change by running the report on a second server runnning 9.10.2-U5 and then re-running the report again after upgrading the second server to 11.0. Something in the latest version of FreeNAS has broken (slightly) the formatting of the report.
View attachment 18984
Yes I receive normal system emails and sending the test email works.Are you able to send a test email from the GUI? Are you getting other system generated reports via email?
Sent from my Nexus 6P using Tapatalk
var/log/mailog may provide additional clues. Hint from an old bug report Mail from cron not workingYes I receive normal system emails and sending the test email works.
this is what was in the var/log/maillogvar/log/mailog may provide additional clues. Hint from an old bug report Mail from cron not working
root@FreeNAS:/var/log # more maillog Jun 19 00:00:00 FreeNAS newsyslog[48945]: logfile turned over Jun 19 03:01:02 FreeNAS /find_alias_for_smtplib.py[56491]: sending mail to rootTo: root Subject: FreeNAS.local daily security run output No /var/log/mount.today No /var/log/dmesg.today -- End of security output -- Jun 19 03:01:06 FreeNAS /find_alias_for_smtplib.py[56491]: sending mail to red.*********@gmail.comContent-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Subject: FreeNAS.local daily security run outp Jun 19 03:01:07 FreeNAS /find_alias_for_smtplib.py[56653]: sending mail to rootTo: root Subject: FreeNAS.local daily run output Local system status: 3:01AM up 11:21, 0 users, load averages: 1.59, 1.05, 0.87 -- End Jun 19 03:01:07 FreeNAS /find_alias_for_smtplib.py[56653]: sending mail to red.*********@gmail.comContent-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Subject: FreeNAS.local daily run output From: --More--(END)
Seems you have bigger issues than just the report. I note you worked from a fresh install of 11.0. I took an upgrade path from 9.10.2-U5 to 11.0. Not sure I have anything more to add at this stage. Unless someone with more experience has something to add, I'd be considering configuring a fresh install of 11.0. Alternatively, install and configure 9.10.2-U5, test that the report works and then upgrade to 11.0.when i click run now on the cron job this shows up as soon as I click it.
Oooo, I like that, should be pretty easy to do. I'll work on it later today and update the file on github :)@melp Thank you for your script. It looks great! I have a request. What would be the code to add another column listing the Power-On Hoursas yy mm dd? Is that possible?Code:Power_On_Hours/{onHours=$10} \
I use a spindown script for my hdd. Will it also be possible to add the state for each disc spinning/not spinning ?Oooo, I like that, should be pretty easy to do. I'll work on it later today and update the file on github :)
Updated version of the report here: https://github.com/edgarsuit/FreeNAS-Report
I added logic to auto-detect drives (omitting SSDs) and pools. I also played around with the columns a bit (added a SMART summary column and last test type column). Let me know if anyone else has suggestions/requests.