{% extends "layout.html" %} {% block title %}TrueNAS Burn-In — Settings{% endblock %} {% block content %}

Settings

API Docs

Changes take effect immediately. Settings marked restart required are saved but need a container restart to fully apply.

Email (SMTP) {% if smtp_enabled %} Enabled {% else %} Disabled — set Host to enable {% endif %}
Timeout
Webhook
POST JSON on burnin_passed / burnin_failed. ntfy.sh, Slack, Discord, n8n. Leave blank to disable.
SSH (TrueNAS Direct) {% if ssh_configured %} Configured {% else %} Not configured — using REST API / mock {% endif %}

When configured, burn-in stages run smartctl and badblocks directly on TrueNAS over SSH, enabling SMART attribute monitoring and real bad-block detection. Leave Host empty to use the TrueNAS REST API (mock / dev mode).

Either password or key auth. Key takes precedence if both are set. Key is stored securely in /data/settings_overrides.json.
Notifications
Daily Report
Full drive status email each day
Alert on Failure
Immediate email when a burn-in fails
Alert on Pass
Immediate email when a burn-in passes
Burn-In Behavior
How many jobs can run at the same time
⚠ Running many simultaneous surface scans may saturate your storage controller and produce unreliable results. Recommended: 2–4.
Jobs running longer than this → auto-marked unknown
Show orange above this temperature
Show red + block burn-in start above this temperature
Max bad blocks before surface validate fails (Stage 7)
System restart required to apply
Comma-separated IPs/CIDRs. Empty = allow all.
{% endblock %}