Alrighty! All good! Figured it was a Multi_Report problem since this is the first program I am using that utilizes SMTP, but turns out I was wrong. Thanks for the help!
At the moment, and just with the info provided, the only things come into my mind that can lead to receive double email like that are
- bad alias settings
- bad mailing list settings
So just a general advice where to look into your mail server.
Despite emails looks identical, i would be curious if the header Is the same. As if you change recipient in MR the email Is still doubled
FWIW, I recently upgraded to 25.10.2.1 and as part of the process rebooted the system.
Two things happened subsequently: the SATADOM that was unhappy dropped 20*C and the error it was dealing with (time since last scan) has also disappeared.
Anyone know a good priest? I feel as though my SATADOM might be possessed.
Maybe you actually own a SATANDOM? Always check the fine print.
5 Likes
That would explain so much. Thank you for the laugh.
A ĪŗĪ±ĪŗĪ±Ī³Ī³ĪĪ»Ī¹ĪæĪ½.
1 Like
Ī±į½Ļį½øĻ Ī³į½°Ļ į½ Ī£Ī±ĻĪ±Ī½į¾¶Ļ Ī¼ĪµĻĪ±ĻĻĪ·Ī¼Ī±ĻĪÆĪ¶ĪµĻĪ±Ī¹ Īµį¼°Ļ į¼Ī³Ī³ĪµĪ»ĪæĪ½ ĻĻĻĻĻ. 
1 Like
Hey folks, it has been a while!
I am running 25.04.1 (Fangtooth) and plan to update to latest (seems to be Goldeye 25.10?). My current script version is Multi-Report v3.24.
Anything I should know before updating? Ie pesky changes that broke the email reporting (iirc that was succesfully addressed thanks to @oxyde).
Thank you again for your splendid service @joeschmuck.
1 Like
Man how much time!
Actually MR have a webpage for generate the config file and a visual disk layout, here the toolsā¦ So update soon ahahah
Donāt know if you already realized, but on goldeye all the GUI part about smart has been removed (and the existing tasks converted to cron)
1 Like
You can continue to use v3.24 if you desire, there is not impact. In v3.28 we put out a Disk Layout feature, which is still very young and by far, not foolproof. Hopefully in time it will improve and become a solid performer. As @oxyde said, there is a website that allows you to configure this feature (move the drives into specific blocks to mimic your hardware layout).
I do have v3.29 which is a maintenance update (see, I can speak like a manager and not just call it a bug fix). Everytime I think itās ready to go out, another tiny problem crops up, and one happened this morning. That one should be an easy fix (yea, sure).
Thanks for the continued support. But I hope TrueNAS pulls in some of this kind of report generation so it become truly integrated. Iām curious how the new SMART changes are going to play out.
Iāve been using Multi-Report on three of my TrueNAS Scale systems for a few months and really like it!
But on one system, which has been having lots of hard drive issues - the drives have been changing VERY often. The script has been doing a good job scanning and reporting for on the changing drives, but the Disk Layout feature has not been reporting the locations or letting me update their drive bay locations.
Iāve used the Multi-Report Hub Disk Layout Editor to edit (or later create a new) disklayout_config.json file. When that didnāt work, I also ran multi_report.sh -config to write the new configuration files.
The disklayout_config.json in the script directory is properly configured to display the location in the custom case I created a few months ago and has been updated to have the current drive bay configuration. But the email report HTML file displays the custom case with the replaced drive bays as āEmptyā.
I see a file in the directory named ādisklayout_changes.logā, but right now itās not seeing the most recent disk changes (from yesterday), the time stamp for that file is several weeks old. How does the configuration for disk layout get updated and how does the ādisklayout_changes.logā get updated?
So - Iām not sure if Iām missing a step or if this is a bug in the new Disk Layout feature!
I thought Iād ask here before opening a bug, in case Iām missing a step that Iām unaware of.
Thanks!
@RobTheGob i think we have 2 different things to approach:
this should be @joeschmuck territory, i canāt help you much thereā¦ maybe start send him a dump of multi report with -dump email (i have read somewhere in the forum that he is probably away for some day) with refer of this message
this is happening in the web ui? If yes, can i ask you to DM me the actual config file (so i will try myself)
@RobTheGob Sorry you are having issues with the Disk Layout.
And thank you @oxyde for jumping in.
I really do not want to assume, but short of specific information, I will this time. I am assuming you are talking about the Drive ID (sda, sdb, sdcā¦) changes drives (by serial number). If this is the case, this is how Linux operates, and if you are shutting the system down or rebooting, those can change. It is a race to see who gets ready first and then gets assigned sda, sdbā¦
Now, if you are saying the Drive IDs remain the same but the location in the Disk Layout changes, then I would need more details. The Disk Layout is still not a 100% perfect piece (closer to 80%) of software. I am trying to Port Map each physical data connection and if you just have SATA drives (not SAS/SCSI/NVME) then it is easy. NVME isnāt terrible however there are some operator limitations to keep it working as it should.
Feel free to send me a PM (for us older folks) /DM (for the youngsters) and provide me hardware details and exactly what is going on. I have noticed a few people having issues with the Disk Layout and I have not gotten to the bottom of it. I do know the problem is in my software, not @oxyde which I will thank again for the very nice web tools he created.
I might need you to send me a dump, running the script from the CLI and using the switches -dump email. Then we will be able to converse via email. If the problem is my software, maybe your information will help me solve this problem.
With that all said @oxyde is correct, I am going out of town Monday morning and wonāt return until Saturday. I will have a laptop so I should be able to answer a few emails, but do not expect a rapid response during this time. I still have until Sunday evening to try and help before I depart.
Sorry - I wrote this post quickly this morning and thought it made more sense than it obviously doesā¦
When I said āthe drives have been changing VERY oftenā - I meant Iāve been changing the physical drives often, trying to track down an issue causing errors in my ZFS pool. So - serial numbers and model numbers having been changing every few days for several weeks.
The drives getting changed is fine in TrueNAS (Iāve been using TrueNAS since FreeNAS 0.6 days) and Multi-Report is properly reporting on the drives, before and after the physical drives are swapped. So - TrueNAS and Multi-Report are both working fine when the drives are being changed.
But what has been happening is the Drive Layout Visualization image (and HTML that is attached to the Multi-Report email) does not display the NEW drives. Instead of showing them as unassigned or the layout is missing/not configured - it shows the drive bays as Empty and the image itself has no mention of the new drives with new serial numbers. In my case - itās only been showing two of the drives that havenāt changed recently.
The disklayout_config.json DOES have the correct (new) drives and has them in the correct drive bay locations. But the Multi-Report email report does not appear to be picking up the changes.
Iām not sure if that is any more clear - but I can grab some logs and/or screenshots to help describe what Iām seeing.
Iāve not really needed this Drive Layout Visualization myself - but Iām introducing a new person to TrueNAS and thought it might help her see where the drives are located in the system.
I just thought since this was a new feature - there may be some value in trying to determine why this is happening.
Trust me, we all do that. This is why I try hard to be very clear. We have language barriers and knowledge barriers. I try to not assume anything.
As for the Disk Layout, if you do not desire to send me a dump, you can run one for yourself only, -dump and an email will be generated with a dump tar file. You could then open that up and PM me all the files in the DISK_LAYOUT folder, and the current disklayout_config.json.
But it is good to hear that the software is for the most part, tracking well.
Is it only a specific drive bays? Is it specific drives?
If you can provide me a few different samples of the disklayout_config.json file (before a swap, after a swap, that kind of thing), it could be helpful. And yes, Iām asking for a bit of information, Iād rather ask for what I think I will need vice doing it piece by piece which drags out the issue longer. That drives me crazy, hence the built in dump function. you will see, I gather a bit of data, but everything in there can help me understand what is happening and hopefully help me create a solution. Also, that data can be used in my simulator. It isnāt the same as the real hardware but I can locate most problems.