fix(nixos): smartd self-gates on the hardware — the doctor was right, smartd wasn't
Some checks failed
Check / eval (push) Has been cancelled

BACKLOG #118. Bernardo booted the live ISO and the Waybar health icon was red,
reporting smartd. Everything downstream turned out to be working correctly,
which is the part worth recording: smartd's config is DEVICESCAN, and where no
drive answers SMART it exits 17 ("Unable to monitor any SMART enabled
devices"), systemd marks the unit failed, nomarchy-doctor faithfully reports a
failed system unit, and Waybar paints @bad. The doctor was telling the truth.
smartd was the bug.

Scope was never live-only, which is why this sat in NOW rather than as a live
nit: services.smartd.enable mkDefaults true on every machine and QEMU virtio
exposes no SMART, so every VM install has been booting to a health warning
about a daemon with nothing to do — and every V2 run had been showing it as
noise.

Fixed with the distro's own self-gate convention: an ExecCondition running
`smartctl --scan`, which prints nothing exactly when smartd would find nothing.
A failed condition leaves the unit inactive rather than failed. Deliberately
NOT SuccessExitStatus = 17: that would also swallow exit 17 from a machine that
does have drives, which is the entire reason the daemon ships.

V2. checks.smartd-gate boots the REAL distro module rather than a restatement
of it (its nixpkgs.config needs mkForce to yield to the test's pkgs) and
asserts both halves, because they pull in opposite directions: a gate that
never skips leaves the red icon, and a gate that always skips silently disables
drive-health monitoring on real hardware — the failure nobody notices until a
disk dies quietly. So the no-SMART node must go ActiveState=inactive, unfailed,
and absent from `systemctl --failed` (what the doctor actually reads); and the
gate's logic is driven against a scan that DOES find a device, since QEMU
cannot answer SMART honestly and pretending otherwise would test nothing. The
check was proved to fail by unwiring the condition. flake check, doctor,
hardware-toggles, live-baseline-apps, option-docs and state-bridges pass.

V3 pending: that smartd still RUNS where drives have SMART (dev box, real
NVMe). Queued with an explicit fail-condition — if it skips there, revert the
gate rather than tune it.

Also swept: #120's size table said the duplicate chromium was gone; #121 was
reverted, so it is back and the table says so.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
2026-07-14 17:38:58 +01:00
parent 0727ba6d44
commit 19ba4e2b12
6 changed files with 162 additions and 51 deletions

View File

@@ -168,6 +168,27 @@ in
notifications.x11.enable = lib.mkDefault true;
notifications.wall.enable = lib.mkDefault true;
};
# Self-gate on the hardware, like every other conditional bit of the
# distro. smartd's config is DEVICESCAN, and where no drive answers SMART
# it exits **17** ("Unable to monitor any SMART enabled devices") — which
# systemd records as a FAILED unit, nomarchy-doctor faithfully reports as
# a failed system unit, and Waybar renders as a red health icon. That is
# every QEMU guest (virtio exposes no SMART), most live USB sticks, and
# some eMMC — so a plain VM install greeted the user with a health warning
# about a daemon that had nothing to do (Bernardo, live ISO 2026-07-14).
#
# ExecCondition is the right lever, not SuccessExitStatus = 17: a failed
# *condition* leaves the unit **inactive** and unfailed, while exit 17
# from a machine that DOES have drives still fails loudly — which is the
# entire reason the daemon is here. `smartctl --scan` prints nothing
# exactly when smartd would find nothing, so it is the same question
# asked before the daemon can fail it.
systemd.services.smartd.serviceConfig.ExecCondition =
lib.mkIf config.services.smartd.enable
(lib.mkDefault "${pkgs.writeShellScript "smartd-any-smart-device" ''
[ -n "$(${pkgs.smartmontools}/bin/smartctl --scan)" ]
''}");
# Core security: enable AppArmor to confine desktop apps and services.
security.apparmor.enable = true;
security.apparmor.killUnconfinedConfinables = false;