SystemStatus
True whenever any disk hoservad expects is currently missing by identity — including once the user has acknowledged the degraded state through POST /array/degraded/acknowledge. It clears only once the missing disk actually reappears; arrayDegradedAcknowledged is what distinguishes an acknowledged degraded array from one still waiting on the user.
True once the user has acknowledged the current degraded state (hoserva array acknowledge-degraded) — only meaningful while arrayDegraded is also true. It resets the moment the missing disk reappears, the same way the acknowledgement itself does. It can be true while storageServicesReleased is still false: the acknowledgement stands even when the transition it triggers does not actually start anything (maintenance mode, or a mount failure, array_services_not_started) — a client must never read this field alone as "services are running".
True once hoservad's storage-target gate has actually released Samba, NFS, Docker and libvirt — read live from the runtime flag hoservad itself sets only after mounting and confirming the pool — and the array is not currently in maintenance mode. This is the field a client checks before ever telling the user services are running; arrayDegradedAcknowledged alone only reports the acknowledgement, not whether it took effect. It goes false again the moment array stop enters maintenance mode, even while the runtime flag from an earlier acknowledgement is still set — an explicit stop takes those services back down, so a standing acknowledgement must never be read as "still running".
{
"healthy": true,
"summary": "string",
"maintenanceMode": true,
"arrayDegraded": true,
"arrayDegradedAcknowledged": true,
"storageServicesReleased": true,
"parityBlocked": true,
"activeJobs": 0
}