--- title: Read FMA's diagnosis before you clear it, and run fmadm repaired only after a repair area: fma impact: MEDIUM tags: [fma, fmadm, fmdump, fmstat, faults, hardware] verified: 2026-11-04 --- # Read FMA's diagnosis before you clear it, and run fmadm repaired only after a repair The fault manager, `fmd`, turns error telemetry into diagnosed faults. It can disable a faulty part to protect the system. `fmadm repaired` says a resource has been repaired, `replaced` that it has been replaced, and `acquit` that it is not a suspect or an event can be ignored. fmadm(8) says to use them "only at the direction of a documented repair procedure", so ask the user before running any of them. **Antipattern** ```sh # "make the warning go away" from a log line, with no diagnosis read and no repair done pfexec fmadm repaired pfexec fmadm reset # deletes all of the module's persistent state ``` **The Solnix way** ```sh pfexec fmadm faulty # resources fmd believes are faulty (-a: all cached, -s: one line each) pfexec fmdump # the fault log: TIME, UUID, SUNW-MSG-ID pfexec fmdump -v -u # one diagnosis in detail (-V: every field) pfexec fmdump -e # the error log: the telemetry behind the diagnoses pfexec fmstat # per-module statistics svcs -x # SMF's view; FMA hands service faults to SMF # Look up the SUNW-MSG-ID at http://illumos.org/msg/ and follow that article's repair steps. # only after the documented repair procedure, and after the user agrees: pfexec fmadm repaired # or: replaced ; acquit [uuid]; acquit ``` Before you run `repaired`, `replaced` or `acquit`, tell the user four things: which resource and UUID it clears; that the man page reserves it for a documented repair procedure; that fmd disables a `faulted` resource, which may need another command to come back into use; and which repair was done. Then ask them to confirm. **The illumos way** (OpenIndiana, OmniOS, SmartOS) ```sh pfexec fmadm faulty pfexec fmdump -v pfexec fmadm repaired # same rule: a documented repair procedure, and the user's yes ``` The OpenIndiana handbook's FMA section is a placeholder, so the man pages are the reference. **The difference.** Same as illumos. FMA comes from the gate, and Solnix does not replace it (handbook: illumos features, FMA). fmd's logs are in `/var/fm/fmd` (errlog, fltlog, infolog, infolog_hival: fmdump(8) FILES). Whether `/var/fm` survives a boot-environment rollback depends on the install: images from make-be keep `/var` inside the BE, and the shared `/var` layout is not yet proven on a real install (see Unverified). A pending OS-repo note plans to drop the FMA SNMP piece (`svc:/system/fm/snmp-notify`) and says fmd itself is unaffected. **Check.** `pfexec fmadm faulty` lists no resource for the fault you handled. (fmadm(8) calls its human-readable output not-an-interface, so read it; do not parse it.) **Unverified** - Whether `/var/fm` is on the shared `/var` datasets on a real install: design-var-state.md proves the layout on scratch pools only ("PLANNED (not yet run)"). - The exact output `fmadm faulty` prints after `repaired`. The man page lists the states ok, unknown, faulted and degraded, but does not show it. **Sources** - [fmadm(8)](https://solnix.io/docs/man/fmadm.8) (illumos, CDDL), DESCRIPTION (needs PRIV_SYS_ADMIN), SUBCOMMANDS acquit, faulty, repaired, replaced, reset; resource states - [fmdump(8)](https://solnix.io/docs/man/fmdump.8) (illumos, CDDL), DESCRIPTION, OPTIONS -e, -u, -v, -V - [fmstat(8)](https://solnix.io/docs/man/fmstat.8) (illumos, CDDL), DESCRIPTION - [fmd(8)](https://solnix.io/docs/man/fmd.8) (illumos, CDDL), NOTES (svc:/system/fmd:default) - [Handbook: Debugging](https://solnix.io/docs/handbook/debugging#hardware-and-diagnosed-faults-fma) (site 307b67f), Hardware and diagnosed faults (FMA) - [Handbook: illumos features](https://solnix.io/docs/handbook/illumos-features#fault-management-architecture-fma) (site 307b67f), Fault Management Architecture (FMA) - [docs/design-var-state.md](https://codeberg.org/solnix/solnix/src/commit/5a8e5ce75a33086d7be4410149847bdf7501b8fc/docs/design-var-state.md) (solnix 5a8e5ce), The layout (fm: fmd's errlog, fltlog, infolog_hival, shared); Who does what (solnix-install creates the datasets, make-be images do not) - [docs/pending/world-unresolved-needed.md](https://codeberg.org/solnix/solnix/src/commit/5a8e5ce75a33086d7be4410149847bdf7501b8fc/docs/pending/world-unresolved-needed.md) (solnix 5a8e5ce), group B (FMA SNMP) -> DROP, a pending proposal - [OpenIndiana handbook: System Administration](https://docs.openindiana.org/handbook/systems-administration/#fault-management-fma) (PDL), Fault management (FMA) (placeholder)