Odd, the header says v3.14. Hum… Interesting and makes me ask a few more questions.
The intended process:
Run v3.14 → Detects a new version is available.
Grab the new version and update.
Finish running the New script and generate reports.
I’m sure it will work fine the next time it runs, I just wasn’t expecting this. Maybe it’s been like this for a while and I never noticed it.
So that is 2 things to look into now. All minor but I will keep thinking about them until I fix them to do my will.
Oh, you know what? I think you had me manually change the version when we were testing the email stuff. That might be why it says 3.14 in one place and 3.15 in another, I did run the manual update and I shows the same output after it checks and updates.
I can ssh in and see if the config file reflects that.
Edit:
In the config file for multi_report_v3.15_2025_02_22_config.txt
is the line # Multi-Report v3.13 dtd:2025-01-22 (TrueNAS Scale 24.10.1)
The actual associated multi_report_v3.15_2025_02_22.txt (script file) shows 3.15 as the version as does the actual script that runs.
The config file should have automatically updated but as you said, I did give you a different version to try out. Running the -config and writing the file again recreates it with all the new parameters, you absolutely did the correct thing. And I will not try to second guess this issue. All should be fine for 99.9% of the people out there.
Hey Joe,
Quick question, script running great. the new Scam check is working great. it had identified some of my drives as scam drives which wasn’t really a surprise to me, but great to confirm.
My question is, now that its confirmed how can i turn off just the scam check? I still want to track the number of hours I have run the drive in this system, just not the f.a.r.m. comparison.
I have ran through the -config but i didn’t see anything jumping out at me to disable just the scam check. Thanks in advance.
First of all I need to apologize, I used the wrong compare in the script for the SCAM section. I used -gt vice -ge. Seems small until you get false positives.
Please ignore any positive you get until version 3.16 is released later today. I have already fixed that issue.
As for turning off the SCAM check, I placed that setting is a bizarre location and I moved it yesterday to a much more appropriate section. It will be under Advanced then option “t” for SMR, Partition, and now introducing Seagate SCAM.
I have also added another setting that allows you to choose how different the power on hours are between SMART and FARM. Before I had it strict so they had to match always. Now due to some additional information it looks like there can be a valid reason for a difference between the two values. The most obvious is if a drive has been refurbished. As I understand it, FARM data remains from cradle to grave, never being reset, unlike SMART with does get reset for a refurbished drive.
With all that said, I chose a value of 6 hours decrepancy before a warning alarm is initiated. For those who have new drives, this should be reasonable. For those who have refurbished drives, you can change the value in the -config section and/or enable/disable the feature. As I am typing this, if I see people having issues with a mixture of drives, new and refurbished, I could add this discrepancy value to the Custom Drive List and have it ignore that particular drive. But we will see.
If you see any other issues, please let me know immediately. I don’t mind putting out a few different minor versions but if I can fix a problem in fewer version, that would be nice.
@joeschmuck heya mate, maybe a silly question. Does this version now schedule drive tests automatically? I already has these set, but I think they’ve been adjusted?
Multi-Report has been broken down into two separate scripts, Multi-Report which generates the email (table and results), and Drive Selftest which run SMART testing on all your drives.
Drive Selftest will (by default) not test drives upon it’s first installation. You need to update the multi_report_config.txt file to tell the script to run tests. In your situation it looks like you have Test Mode 2 for Short tests which means test all drives. Test Mode 1 is to test XX drives per day over a period of time, and generally Test Mode 1 is used for Long tests.
As you can see, the script will adjust how many drives it will test for the given periodicity, in your case it is to test all drives once a week over a 7 day period of time.
Of course all this can be disabled.
I noticed an error message, this will be fixed in version 1.05 of Drive Selftest, currently being tested. Yes, I found some flaws which are being fixed. I have also added the ability to test USB attached drives, well some right now and if people find it does not test their USB attached drives, they need to contact me so I can try to adjust the script to compensate for it.
My goal is to remove SMART testing once TrueNAS fully support all SMART testing for all drives. NVMe is not supported, yet. This script does support it.
Now to answer your specific question… Once you have setup the script, it will not automatically change anything. If drives change, that would be due to you including or removing drives on your system.
Hello folks,
Week ago, I started to get the report with WARNING… Somehow the Information of the disks power on is not match or correct.
anybody face something like that?
h-t-t-ps://i.postimg.cc/0PDNMSW-n/Screenshot-2025-03-12-160625.png
WARNING LOG FILE
Drive: sda Power On Hours Does NOT Match ... ### S.M.A.R.T.: 1687 ### ... ### F.A.R.M.:22798 ###
Drive: sdb Power On Hours Does NOT Match ... ### S.M.A.R.T.: 1687 ### ... ### F.A.R.M.:22798 ###
Drive: sdc Power On Hours Does NOT Match ... ### S.M.A.R.T.: 1687 ### ... ### F.A.R.M.:22798 ###
Drive: sdd Power On Hours Does NOT Match ... ### S.M.A.R.T.: 1687 ### ... ### F.A.R.M.:22898 ###
This means that you have a refurbished drive or have been scammed. This check was installed because of the scam going on with large capacity hard drives. Now that you are aware, you can turn that feature off. In the next version of Multi-Report, you can leave the check on and just ignore the drives you already know about, but that won’t be out for several weeks, if that fast.
To disable the feature, run the script with the -config switch, go into the Advanced Configuration Settings, to option “T” and use Enter to page to the Seagate Drive Scam Check page. Here you want to Disable the feature. Press Enter until you return to the Advanced Configuration Settings main page. You must hit “W” to write your changes to the config file. And then “X” to exit out. Now the check is disabled.
Sorry for the late reply and appreciate your help here.
Those drive are brand new from store that sell only new stuff. More than that Those drive run in my lab couple months now when active them in the first time there was 1 hour of use, so I don’t believe this is used drives.
The warning start when I updated the script to the last version, something changed and I have no idea what.
Thanks for the tip of disabling the Seagate Drive Scam Check.
You should run the command smartctl -l farm /dev/sdb and smartctl -a /dev/sdb then compare the power on hours and the LBAs Read/Written. While we are now seeing some of the FARM data being changed, I have not heard of the effort to change all the data to match. A small discrepancy is fine, less than 10 hours I’d say, but you have substantially more. And check the serial numbers as well. If things seem fishy, check the warranty or reach out to Seagate and tell them what you have found, or possibly the vendor, I’m fairly certain they have heard of this issue.
Unfortunately the used drives from China were introduced into the retail market in the distribution chain so any vendor could have a used drive that is all boxed up and looks like a new drive.
I hope your drives are not part of this issue but cover your rear, check.
You are right.
I compared the data and I can see big different in the power on hours.
Power on Hours: farm 22903 vs 1793
S/N is identical.
So just to understand, any kind of software or settings that set incorrect can cause this different? or it’s crystal clear that this drive or board were use before… ?
