The permissions issue is with smr-check.sh and it needs to be changed to chmod 755 smr-check.sh however I’m not sure why this is a special file. I don’t know if file permissions are transferred with the file on GitHub, I wouldn’t think so, but I don’t know.
Yes, the issue is indeed caused by smtp.qq.com; TrueNAS has this problem when sending mail, but switching to Gmail eliminates the error.
1 Like
Yes, the attachment was received. The email was indeed delivered correctly; it’s just that the QQ Mail error immediately triggers a “job failed” alert on TrueNAS.
Ok i have found the reason why the attachment ok count is not well displayed when sendemail treating the qq.mail exception, a small oversight my side, i will fix it in the next release. Many thanks for the “unwanted” debug 
Coming back to your main problem, have you already try to fix the permission on the smr check script as @joeschmuck suggested above?
1 Like
Yes, we debugged it in DMs and the issue is fixed.
1 Like
Reasons to use Markdown:
- PDFs aren’t optimized for search, making it more likely to miss something. Markdown is essentially a simplified text markup language similar to HTML, so search issues are almost nonexistent.
- Markdown is a very mature and popular format. Even if distributed locally, I believe most users will be able to find a way to access Markdown files. If you don’t need to view images, you can open Markdown files as regular text files.
- For non-native English speakers, translating PDFs is a disaster. PDFs wrap text between lines, which can affect translation software and cause serious formatting issues after translation.
- If necessary, Markdown files can be converted to PDF using GPL-licensed open-source software like Pandoc.
- Markdown also supports embedded images and has dozens of third-party tools (both free and paid) for editing.
- If a user doesn’t have access to GitHub, they won’t be able to initialize the script or obtain the automatically downloaded PDF file. If they’re using an already initialized script, the format of the packaged file doesn’t make much difference. If a user only has a Linux terminal without a desktop environment installed, they obviously won’t be able to view PDF files. However, they can use the simple cat command to view local Markdown files or curl to view online Markdown files. While the file content won’t be rendered and images won’t be visible, the Markdown format is still human-readable.
- The Markdown format facilitates online collaboration and modification. While you might not want users to submit pull requests, it makes it easier to provide feedback.
- I’ve used hundreds of open source software, but this is the first software (or script) I’ve encountered that distributes user documentation in PDF format. I have reason to believe this isn’t a good practice, especially for scripts running on Linux systems.
About the User Guide:
- The largest section in the guide is devoted to explanations of each command. These can be updated simultaneously with the comments in the script, potentially simplifying your work. If users use the “-h” option to obtain information as detailed as the manual, they might not have to go back and forth to find the documentation.
- Sections such as “What is Multi-Report?” in the user manual can be placed in the README file on GitHub. Sections such as “What’s New in version x.y” can be placed in separate changelog files, and sections such as “Setup” can be placed in separate setup files. Outside of business scenarios, I can’t see any benefit in putting all these sections in one file; it reduces user information retrieval efficiency. If there are no strong dependencies between sections, I recommend splitting them into separate files for maintenance.
- Only explain technical details, principles, or designs in the following situations, leaving the user to review the script code for the rest:
3.1 Calls to third-party tools, libraries, or interfaces, complicating debugging. For example, a script sends messages through the TrueNAS’s email interface. If the user hasn’t configured the SMTP server, username, and password on the TrueNAS, the script’s email functionality will be unavailable.
3.2 Involves complex logic and time settings. For example, configuring a SMART Long Test to occur weekly or monthly.
3.3 Involves dangerous operations or could significantly impact system performance. For example, SMART Long Test will be automatically circumvented during ZFS scrubs.
What does “last test age” mean? Every single one of my drives is orange in that column.
Last Test Age is the number of 24 hour periods (according to the drive power on hours) have passed since the last SMART test was run.
Orange means you have exceeded the threshold of XX days according to the multi_report_config.txt file. The default is 2 days. The number in that column is how many days it has been since the last test.
This single alarm was the entire purpose of this script when it was born, to let the user know that SMART testing was not happening as scheduled, because FreeNAS periodically after an update would stop SMART testing, it lost the settings.
@Apple
While I enjoy a good debate, at times, this isn’t one of them. We both have a difference of opinion, and I’m perfectly fine if someone doesn’t share my opinion. Everyone has one. I am also extremely comfortable using MS Word and MS PowerPoint which is my current choice of editors.
As for searchable PDFs, your statement can be true if the person generating the PDF doesn’t make it a searchable PDF and instead makes it nothing but images of pages. I very much dislike that practice, and when I get a PDF at work that is not searchable, I convert it into a searchable PDF and all my documents are technical and I will be searching it. I normally see those types of files when someone feeds the original document through a page scanner. My PDFs are searchable, give it a try.
If it needs to be in a different language, Google Translate will convert the entire PDF (minus the graphics) into another language. Yup, I tested it and while I can’t read Greek, it still looked Greek to me. 
Thanks for your comments, it is good to hear someone does read the documents. And hopefully they will improve with the next version.
4 Likes
So…what are my next steps? Two days ago, six of my eight drives were orange, yesterday they all were. However, they were all showing an in-progress test. None of this should be happening if it’s following the schedule I set up.
I didn’t get an email today as my internet was out overnight, so I’m not sure of the current status.
I very much agree. on the websites I manage, documents for download are all searchable .pdf files. If I receive a non-searchable pdf, (all pages are images) for inclusion on a site, I refuse it and ask the sender to make the pdf properly. If they need help, then I will help them. I have found over the many years that the pdf format is the least troublesome overall.
1 Like
Thank you for providing the excellent open-source script. I appreciate your reply and see that you noticed the issues with search and translation.
I know that PDFs converted from Word documents are searchable by default. However, a text search that takes a second in Word or a webpage takes a considerable amount of time in a PDF. Due to the limitations of the PDF file format, the more keywords are matched, the longer the search time. I’m using an AMD 7730U laptop, and indexing any keyword takes at least 10 seconds. If searching for a particularly frequent word, the indexing time can exceed 30 seconds. Even worse, I’ve encountered issues where a keyword I searched for in Word wasn’t searchable in the PDF, so I’m not confident in PDF searchability.
The images below illustrate some typographical errors. Worse still, the translation quality is low. For the same page of text, if the translation quality using the web version of Google Translate is 80/100, the quality of the PDF translation is only around 30 to 70/100.
@Apple
I have posted on GitHub the MS Word and MS PowerPoint files that the PDFs were generated from. Feel free to convert the files and then send them to me via email to joeschmuck2023@hotmail.com and I can review (what I will understand) and upload those to the repository.
I had to laugh, not making fun of you I remember days where computers only existed for major companies, where programming in 80 column Punch Cards was how things were done, and when computers became affordable for smaller companies, searching a document could take a few minutes to hours. Then when a better computers did become available for everyone, searching still took several minutes, sometimes long enough to take a coffee break.
We live in a world where everyone wants instant gratification. I will admit, I too like how fast things are these days, but periodically I still need to look at a physical document and page through it to find what I need. Oh the stories I could bore you with, but I will not.
Seriously, if you want to translate and generate the docs, I have no issues with it. As always, it’s my name and reputation on the script, I own any screw-ups, so my control is tight.
1 Like
As I recall, you always had several drives that were performing a Long test and in alarm status (Test Age Only) at any given moment.
The fix for your configuration is to increase the Test Age Threshold.
- Open the file
multi_report_config.txtwith a simple text editor. - Locate the line
TestWarnAge=2(around line 109) - Change it to
TestWarnAge=4or change to some higher value to when you really want to know that SMART testing has basically stopped happening to your drives. Some people choose a value of 7. - Save the text file.
- When you run the script, those specific alarms should now be gone and only occur again if your drives exceed 4 (or 7) days between a test completion.
That should do it.
a text search that takes a second in Word or a webpage takes a considerable amount of time in a PDF. … I’m using an AMD 7730U laptop, and indexing any keyword takes at least 10 seconds.
Which PDF reader are you using? I never see performance this bad when I search PDFs; I’m using Okular. Something seems wrong here.
1 Like
No, this is new. We spent a week going through and making sure test and scrub schedules made sense, and I’ve had no issues outside of temperature (which I’ve been too busy to tackle) in the weeks since.
Is there a way I can view the schedule?
There most certainly it. Run ./drive_selftest.sh -demo short will give you the Short test schedule, and ./drive_selftest.sh -demo long will give you a Long test schedule, using the values you have set in your config file.
If you would like to look at some other things, ./drive_selftest.sh -demo long month will show you what it would look like if you changed to a “month” schedule, or maybe you already are using a month schedule, then you can run ./drive_selftest.sh -demo long week for a weekly schedule.
Use ./drive_selftest.sh -h or use -help to show the help info and options.
This will not tell you if you have the system configured correctly, it is just a demo. Send me a dump so I can see what the system thinks it should be doing.
Multi-Report v 3.26 - (w/ Disk Layout Beta Testing SCALE ONLY)
Version 3.26 incorporated a few small fixes and now includes a Disk Layout tool in BETA and this new tool is only for SCALE (Linux).
For those who want to use the Disk Layout tool, you need to perform the following:
- Run Multi-Report v3.26 one time to obtain the updated config file.
- Open the multi_report_config.txt file and on lines 55 and 56 you should see:
###### Disk Layout ######
Disklayout="disable" # BETA TESTING ONLY
- You must manually change the value form “disable” to “enable”:
###### Disk Layout ######
Disklayout="enable" # BETA TESTING ONLY
-
Save the config file.
-
Run Multi-Report and you will see a new file attachment called Disk_Layout.html and
within the report, just below the CHARTS, you will see a set of blocks which represent
you drives.NOTE: Before visiting the GitHub site, you should know where your drives are physically located as it is needed for the one-time setup.
-
You must visit the GitHub webpage to configure your system. This is a one time only
configuration, unless you change the hardware locations for the data connectors. -
Replace the disklayout_config.json file into your script directory with the one you just downloaded.
-
Run Multi-Report.
That is it. Fairly simple actually.
Please report your results to joeschmuck2023@hotmail.com or send me a DM on the forum.
What would help me:
- Feedback on what works and what doesn’t work.
- If it doesn’t work, details please. And if it can be recreated, how to do that. And run the script
with-dump emailas well so I can collect the data that might be causing the issue. - If you have a problem with the Email HTML, please let me know which email client you are using.
MicroSoft Outlook does have a problem displaying certain HTML data. This is a work in progress.
However the attached HTML file should be correctly displayed. - If you have suggestions, please provide them, preferably with some detail.
- Test the viability of this tool, relocate your drives, see if the disk layout updates correctly.
This is a very important step as the more users we get to test this, the better our odds are
of fixing any problems. - If you have questions, please toss me a message or email.
2 Likes
Just a quick note of thanks. Got multi-report up and running after making sure the ACLs allowed root to write to the scripts directory (d’Oh!) Makes saving a config file a bit easier!
Basic config is running, will dive into the next layer of features as time allows. But most importantly, THANK YOU for an awesome script, your relentless dedication, and all the tech support you had given here. You are a model of community spirit.
5 Likes
Appreciate the kind words. It is a job, Oh Wait, I don’t get paid for this. Then it at least keeps my brain busy. It beats watching TV for hours a day.
5 Likes