Impossible to clear SMART error on Scale 25.04.2

TrueNAS General
,
1

Hello everyone,

I'm running TrueNAS SCALE 25.04.2 "Fangtooth" (Community Edition) on a homemade, upcycled system designed to minimize cost by reusing old hardware.

🛠️ Hardware Setup:

  • Case: Fractal Design Define R5
  • Drives: 18 total
    • 2× Seagate ST3000DM001
    • 1× Seagate ST31500341AS

As you might guess, cramming 18 drives into an R5 Define pushed the cooling to its limits. During initial stress testing (theoretical max load), a few drives overheated slightly, which I suspect is why I'm now facing this issue.

⚠️ The Issue:

I'm getting the following repeating SMART error messages:


Device: /dev/sdb [SAT], Failed SMART usage Attribute: 190 Airflow_Temperature_Cel..
Device: /dev/sdn [SAT], Failed SMART usage Attribute: 190 Airflow_Temperature_Cel..
Device: /dev/sdd [SAT], Failed SMART usage Attribute: 190 Airflow_Temperature_Cel..

These errors:

  • Are persistently reported by the UI every time I log in
  • Are sent repeatedly via email alerts
  • Do not indicate current overheating — the temps are now under control
  • Do not need to be cleared from SMART (I want to keep the raw data)
  • Do not need to be flagged as critical or alert-worthy anymore

❓ What I Want:

I’m looking for a clean way to suppress this specific SMART attribute from triggering UI or email alerts, without wiping or ignoring the SMART data entirely.

Is there a way to:

  • Tell TrueNAS SCALE to ignore SMART Attribute 190 for specific drives?
  • Prevent middleware from flagging this attribute as a critical failure?
  • Customize or override alert thresholds for specific SMART attributes?

Any help or pointers (CLI tweaks, middleware overrides, etc.) would be hugely appreciated. I understand the risks and am monitoring drive temps now more actively.

Thanks in advance!

— Théo

2

I got a SMART error when I upgraded from Electric Eel to Fangtooth 25.04.2, and the only way I found to clear it was to delete all SMART tasks under the Data Protection tab, and then recreate the tasks. After that, SMART started without any errors. Perhaps the same thing would work for you.

4

Just got confirmation : tried to remove the SMART tasks, then create them again from scratch. No good, just got the error again, as soon as the test was run.

Issue is that the error lies within the SMART database of the disks. I need a way to either tell the middleware to ignore it when reporting alerts, or disable the alert for that specific error in the UI.

Thanks for your input though !