Multi-Report

It should look something like this. Sections, such as HDD, can be turned off though in the config file so the answer to if it is working as intended is, it depends.

Sections, such as HDD, can be turned off though in the config file so the answer to if it is working as intended is, it depends.

OK, so SAS is turned off by default. Thatā€™sā€¦a choice, I guess.

After turning on SAS, the summary section does show up. All drives are reported, but as expected, the drives with whitespace break onto 2 lines within the cell. The only things that stand out are that the model field is blank for all drives, and the Last Test Age is showing hundreds of days for several of the drives. Iā€™m not sure how this value is calculated vs Multi-Report, but there seems to be a difference of opinion between the two reports.

SAS is currently off by default due to the combination of it not being well supported prior to smartmontools 7.3 and that I currently have no SAS drives to test with. That said if you are willing to make a ticket that includes a dump file (add -d to the invocation) I would be willing to see what can be improved.

Yeah, that is likely due to the overall length; I have some drives that do this for the model.

Dump file sent to github. No need to work on SAS on my behalf. Multi-Report is working well for me now, so Iā€™ll be sticking with it for the time being.

Hey @joeschmuck, so I canā€™t have nvme self-tests because Iā€™m still on SCALE 22.12. and Iā€™ve disabled autom. tests via the scripts config.

Yet, there is a warning about Last Test Age is beyond threshold. Is there a way to turn this off? I havenā€™t found anything in the config about that.

Bildschirmfoto 2024-07-02 um 12.11.33

Why not? You need to -config and ā†’ A ā†’ N ā†’ At the second question enable the Smartmontools v7.4 override, it does not use the term override but this should be ā€œenableā€. And answer the rest of the questions to turn on SMART testing for the NVMe via the script.

Absolutely there is. You will need to run -config, ā†’ A ā†’ S ā†’ Now read the questions and give them and answer. Of course you will only want to adjust for the two NVMe drives in question. Right after the ā€œTest Age (2)ā€ will be "Ignore Test Age=(0) (0=No, 1=Yes). Select 1.

Finish going through all your drives. Do not forget to Write the config file before exiting.

If this is confusing, send me a -dump email and I can quickly re-configure your config file and send it back to you.

1 Like

huh, I was under the impression, that nvme self-testing is only available with version 7.4 of Smartmontools.
Nonetheless, thanks for your comment, I changed the config and now nvme selftest magically are working.

Smartmontools v7.4 and above supports NVMe testing using smartctl, below that and of course they do not, however using the nvme utilities that are native to FreeBSD and Linux, the self-tests run just fine. And even when smartmontools v7.4 is present, the TrueNAS GUI does not allow you to select NVMe drives to be tested. Once TrueNAS has this stuff worked out, I may remove this feature from the script as it should not be required anymore and it will reduce the number of options to make it a little less confusing.

Glad that worked for you.

Hi!

After the update, I keep getting messages like this in the mail:

NVMe status: Invalid Log Page: The log page indicated is invalid(0x2109)
NVMe status: Invalid Log Page: The log page indicated is invalid(0x2109)
NVMe status: Invalid Log Page: The log page indicated is invalid(0x2109)

How can this be fixed?

What update?
Where is this error message being displayed? The email report from Multi-Report, TrueNAS GUI, or TrueNAS email?

Can you run the script with the switches -dump emailextra and this will send me the drive information I need to figure out what is going on.

Hey joe, it has been a while since this feature was introducedā€¦ yet my reports show always the same value for Total Data Read / Written and 30-Day Read / Written (it increases with time, but they do not diverge).

Do you need me to dump?

@Davvo send me a dump and let me know specifically does not seem to be working properly. Maybe i goofed in the math? Maybe it works. Eh, we will find out. If this is a problem then it is good timing, i have an update to push in the next week or so. Nothing critical but i have made a few updates for folks and i should publish eventually.

1 Like

Dump on the way. My impression is that the 30-day counter does not reset.

Thank you for your contributions to this community joe!

Hello Joe

A minor typo (which has caught me out twice in a row because I forgot to pay attention the first and second time when I copied and pasted from the document!):

page three on the PDF shows

image

and it says

As a privileged user, open a shell/SSH window and change
directory ā€˜cdā€™ to cd/mnt/pool/scripts

whereas we can see it ought to say

As a privileged user, open a shell/SSH window and change
directory ā€˜cdā€™ to /mnt/pool/scripts

EB

1 Like

Thanks. Keep searching, Iā€™m 100% certain there are more. Also, the quick start guide, any suggestions are welcome. I understand what I mean however that does not always translate to someone else. The goal was to make something that a person could use without NEEDING to reference the User Guide, and explain the output they should see.

October 1st, retirement day. With some good luck, I will be able to start learning to use Python a bit better. Okay, a LOT better. My configuration program will make it significantly easier for a person to configure Multi-Report. Check a box and it does something, check a few boxes and it can calculate the correct configuration changes.

Iā€™m hoping to make it smart enough that a person can enter a scenario they have and an option comes up. Okay, and AI is something I will not be making :slight_smile:

3 Likes

Yesterday evening (or was it first thing this morning, I canā€™t remember) I had my first Multi-Report sent to me via the cronjob, complete with attached config and it is very much a valued script!

The notion that I will always have an up-to-date config is extremely reassuring, especially at the moment whilst I fiddle with my TN setup. Itā€™s great how flexible TN is and itā€™s a relief that there are talented people in this community who help support and develop the products as part of a hobby interest and/or as part of their job.

EB

3 Likes

Multi-report is running perfectly and I receive an email with an attached config.tar once a week.

At the same time, I do get a CronTask Run" email from TN which tells me this:

Multi-Report v3.0.7 dtd:2024-06-08 (TrueNAS Scale 24.04.2)
Checking for Updates
Current Version 3.0.7 ā€“ GitHub Version 3.0.7
No Update Required
Polling nvme test statusā€¦ (Maximum Test Time before Abort = 3 minutes 0 seconds)
cp: cannot create regular file ā€˜/mainraid/scripts/truenas_Config_24.04.2_2024-08-02.tarā€™: No such file or directory

Indeed, it doesnā€™t appear in the directory (perhaps because it gets deleted after it is created and sent?):

but clearly it can create that file because I receive it as an attachment.

What have I misunderstood or done wrong?

I think I see the error. You may be the only person storing a copy of the backup config file. Give me a little time, I will get back to you.

To get rid of the error for now, go into the multi_report_config.txt file and change
TrueNASConfigBackupSave=ā€œtrueā€ to TrueNASConfigBackupSave=ā€œfalseā€

The error will cause no harm but you will not have that backup copy of course except in your email attachment. I want to blame it on the hardening that came with 24.04.

Yes, I think you have. Thankfully you sent me a dump last week which contains the data I need to help troubleshoot problems. The path you have used is not the ā€œwholeā€ path. I think it will work using /mnt/mainraid/scripts as right now you do not have /mnt at the beginning. Let me know how it works out.

1 Like

Ahh yes, I see it in multi_report_config.txt

TrueNASConfigBackupLocation="/mainraid/scripts/"

changed to say

TrueNASConfigBackupLocation="/mnt/mainraid/scripts/"

Tested and working OK now. A silly mistake, like most of mine always are (apart from the serious ones). Thanks for your help again!

EB