RAID Status Check Reference

All parameters, thresholds, and configuration options for the RAID status check in octoja.

Written By Erdinc Akay

Last updated 26 days ago

The RAID status check monitors RAID arrays and alerts when an array is degraded or failed. It covers Linux mdadm software RAID and ZFS pools, and Windows Storage Spaces and hardware/firmware RAID. In the check catalog it appears as RAID Status (DE: RAID-Status); by default it runs every 60 minutes.

Configuration fields

FieldTypeRequiredDefaultDescription
Check Linux software RAIDbooleanNoYesMonitor Linux mdadm RAID arrays
Check Windows Storage SpacesbooleanNoYesMonitor Windows Storage Spaces pools
Check Windows hardware/firmware RAIDbooleanNoYesDetect controller and Intel RST/VROC RAID volumes (Bus type RAID) via Get-PhysicalDisk
Check Linux ZFS poolsbooleanNoYesMonitor ZFS pool health via zpool status; skipped when ZFS is not installed

Metrics collected

  • Array name (per array)
  • Array status (healthy, degraded, unhealthy, unknown, or rebuilding — with the rebuild percent shown while an array is resyncing)
  • Array level (e.g. raid1, raid5, Storage Spaces, ZFS, RAID for Windows hardware/controller volumes)
  • Number of active and total disks per array
  • Per-array result severity

Platform support

PlatformSupportedTechnology
WindowsYesStorage Spaces + hardware/firmware RAID (Intel RST/VROC and controllers via Get-PhysicalDisk, Bus type RAID)
LinuxYesmdadm + ZFS
macOSNo—

Severity mapping

ConditionResulting severity
An array is rebuilding, resyncing, or servicing (redundancy reduced but recovering)Warning
Linux: degraded mdadm arrayCritical
Linux: array is inactive or failed to assemble (redundancy gone)Critical
Linux: active array with all members up and no redundancy line (e.g. raid0/linear)Success (no alert)
Windows: Storage Spaces pool not healthy — HealthStatus = Warning, any other non-healthy value, or OperationalStatus not OKCritical
Windows: controller/firmware RAID volume whose health is not exposed (Unknown)Success (no alert)
Linux: /proc/mdstat missingNo result emitted (no alert)
Unexpected error while running the checkError (check reports a failure)

Notes

  • The check reads RAID state from the operating system. On Linux it reads mdadm arrays via /proc/mdstat and ZFS pools via zpool status (skipped when ZFS is not installed). On Windows it reads Storage Spaces via the built-in storage management interface and controller/firmware RAID volumes (including Intel RST/VROC) via Get-PhysicalDisk, where a RAID volume surfaces as a single disk with bus type RAID. Primordial (unconfigured) Storage Spaces pools are excluded, so only pools you have created are reported.
  • Controller/firmware RAID reports overall volume health only; the controller hides the individual member disks, so member counts are not shown for those volumes. For per-disk health, use the SMART check.

See also: Configure a RAID Status Check