It is the script when running the '-config' switch. You must save your changes (Write) in order to save the multi_report_config.txt with the alterations the user just made. The script does not alter the TrueNAS configuration file.
Let me guess, you were not renaming the script to 'multi_report.sh' and that was the issue? Sorry about that but it really couldn't be helped. I could have made the script use the renamed file but that left the window open for upgrade failures. From here forward, the script needs to be renamed to 'multi_report.sh'. During the update this file 'multi_report.sh' will be updated with the new changes.(If one uses the right script to update.)
Did you receive any error messages during the initial upgrade? Did you run the script from the directory where it resides? The new script should fix any problems with running from another directory but only on the 'next' update. You will likely need to manually
chmod +x multi_report.sh per the user guide. Hopefully the next time around it will not be an issue. If it is, please let me know.
This was the third time I've had to fix the perms after -update
-conf dialogue. Now everything works as expected.
The current version has hopefully the corrections so you do not see that again, but previous versions might of course. And if you were to run -update right now, which would just reload the script, if the problem still happens then it's not fixed.
That is odd, I'm not sure why you would need to do that as the means it's running bash in a bash shell. I'd like to try to replicate the problem. Maybe when you have some time, toss me an email or PM me with information like permissions for the directory, how CRON is setup, if you are not running as root, then the privileges of the user. And is it Core or Scale.
Thanks for the feedback. You didn't have to do anything special to make the script work, other than configure it using the -config switch, or by using a pre-existing multi_report_config.txt file? I'm just trying to figure out what the issue is. I'm almost positive it's a permissions issue, it always is.
./multi_report.sh -config (in script dir).
putting bash before the script simply invokes the script in bash instead of the script invoking bash itself via the #! at the top.
I did not know that, thanks for the information.
Well I knew someday someone would find this out. I've known this would be a problem but fixing it is a bit more involved so I placed it on the very back burner and waited for someone to call me out on it. It may take me a little time to come up with the proper fix that works on both Core and Scale. Once I have it, can I contact you to test it out? I do not actually have that many drives so I can only simulate that number of drives, so it's not a true test.TrueNAS-SCALE-22.12.2 with 39 spinning rust and 2 mirrored ssds for boot pool. Total of 41 disks. It appears that when the sd devices go beyond 26 and start using designations such as sdaa, sdab, sdac, etc. the reports truncate to sda and just give the same reports on sda instead of sdaa, sdab, etc. Does anyone else see this issue. It is a great script tool otherwise. Thanks.
I would be happy to assist you. I am glad I said something!
Me too. I try to promote feedback, good or bad. My goal is to just make a product that works properly for everyone so don't be shy, if you see something wrong please report it.
Fairly sure that TrueNAS Report would not have that issue if it helps any.
You are correct. I had to bend the rules a little and install bc. However, it did not have the problem. All 41 drives reported. I am not sure what will break on the next update since I had to install a non supported utility. Oh well, wouldn't be the first time I trashed the boot and had to restore it.
