Make the report run on scale too. #6
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
|
Downloaded v1.7 according to the script |
|
@aardvarkl unfortunately that would be a deal killer as |
Closed
* master: (53 commits) Remove the unused -o option from sendmail. List NVMe self tests. Grep out log preamble. Make sure to include the devstat log in the dumps. Update release notes. Add support for per drive overrides. Reorder to be more consistent. Add a file dump option for debugging. Account for scrubs of indeterminate and multi-day duration. Do not math non-numbers. Reduce the number of calls to smartctl. Use the extended test data if available. Fix some quotes. More heredoc conversions. Combine multiple echos into single heredocs. The last of the awk removal. Add more examples. Support multi-day reslivers. Add sections. Change to scrubDuration for better clarity and to avoid collisions. ...
The keyword here here is almost and a lack of docs never helps.
|
Date errors are gone: Prior output removed... |
|
@rbollar Is the (email) output now what you would expect given your layout and configuration? |
|
Actually, yes, as far as the status report summary goes -- the previous report I pasted was old. Well done! Now, how about the HDD SMART Status Report Summary? |
|
@rbollar what is the output of |
|
|
@rbollar |
|
@rbollar but if |
|
@rbollar having thought about some more, try: |
|
Here's that last command: And the help: |
|
@rbollar let me know how the latest version works for you. |
|
This version gives this error repeatedly: ending with: The report is populating, though I notice that capacity is missing from the NVMe and SSD drives: |
|
@rbollar check to make sure that all your drives are listed and then attach the dump file made when running the script with the |
|
The drives are all listed. Still have these errors (one for each drive, I guess?): Oops. Can't do a dump: |
|
@rbollar try |
|
|
@rbollar |
|
Okay -- but this is the current version in the Debian bullseye distribution: https://packages.debian.org/bullseye/bc Just noting this in the event that iX does add bc, it will only be 1.07.1 |
|
I will have to remember to note that in the ticket to have them add |
|
It looks like Debian uses I haven't found a .deb package for the Gavin Howard version -- and I don't know when I'll have the opportunity to compile and test his version. If you know of a .deb version, let me know and I'll pull it. |
|
I haven't looked at all of the instances where you've used bc, but |
|
Good news -- changing the four instances of
|
|
Excellent & added to my crontab. FYI, I turned on reporting and get the following errors. A configuration backup file is attached to the email, but I don't know if it's complete: |
|
Works great for me -- @dak180 thanks for doing the work to make this work on SCALE -- I've wanted this for a long time. |
|
@rbollar always easier when there is someone to test things; I just wish ix would go ahead and add bc to scale. |
|
A suggestion to document getting This script requires the EXAMPLE download and install from the TrueNAS SCALE command line as an administrator: |
|
Unfortunately, |
dak180
added a commit
that referenced
this pull request
Jun 26, 2023
This should survive updates. Refs #6.
@rbollar , dpkg-deb -i does not seem to be a valid command. Did you check that on your system? |
Hm. @symetryczny try this:
|
|
TrueNAS Scale 23 (aka Cobia) is based on Debian 12 (bookworm) I updated rbollar's code to install the Debian 12 version of bc: |
|
|
|
Yes, good point. |
|
It's not possible to write on
Can you clarify this suggestion?
Edit: I figured it out actually 😅 it's just to move the binary under |
|
That is because it is a read only location. @dak180 should be able to fix it. |
|
Thanks for this, this helped me get Scale and reporting working properly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Requires bc to be added to scale.
Fixes #5.