If systemctl start mdmonitor appears to work but systemctl enable mdmonitor reports “The unit files have no installation config,” systemd has found no installation instructions for enabling that service directly. The warning does not, by itself, mean the start failed or that your RAID array is broken. Check the service’s runtime state and your distribution’s intended activation method separately.
Why can mdmonitor start but not enable?
Starting and enabling are separate systemd operations. start activates a unit now; enable uses installation metadata—principally relationships in the unit’s [Install] section—to create symlinks that configure activation through a target or another installation location. The systemd systemctl manual describes these operations as orthogonal: a unit can be started without being enabled, or enabled without being started.
As an Amazon Associate I earn from qualifying purchases.
When a unit has no applicable installation configuration, systemd cannot create the usual enablement links for it. The warning text reproduced in a Linux Foundation course forum report explains that such units are not meant to be enabled with systemctl. Possible reasons include that another unit pulls in the service, it is a helper, an activation mechanism starts it, or it is a template that needs a named instance. Those are possibilities, not a diagnosis of which arrangement your system uses.
Does this warning mean RAID monitoring is broken?
No. The enablement warning is about systemd’s installation configuration; it does not establish whether mdmonitor is currently running, whether mdadm is monitoring an array, or whether alerts are configured. Check those questions independently. A historical Ubuntu report describes an mdmonitor unit without an [Install] section, illustrating why instructions for one distribution may not apply to another. The unit packaged on your machine is the relevant one.
#1 Best Overall
Inspect the installed unit and its state
Use these read-only commands first. They show the local unit, its visible drop-ins, its systemd state, and related units without changing enablement:
systemctl status mdmonitor.service— check whether the unit is loaded, active, inactive, or failed.systemctl cat mdmonitor.service— inspect the unit definition and visible drop-ins, including whether an[Install]section is present.systemctl is-enabled mdmonitor.service— check systemd’s enablement classification.systemctl list-dependencies mdmonitor.service— see units this service depends on or pulls in.systemctl list-dependencies --reverse mdmonitor.service— look for units that depend on or pull in mdmonitor.
Review the complete local unit and drop-in configuration before changing anything. An unrelated systemd issue describes a drop-in for a truncated unit name complicating enablement; it is an edge case, but a reminder that the effective configuration can involve more than the main unit file.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to do next
If mdmonitor is active or starts successfully
Check your distribution’s mdadm documentation or the unit dependencies to determine how mdmonitor is intended to be activated there. If another target, service, or activation path owns that job, enabling mdmonitor directly may not be appropriate. Do not add an [Install] section or create an enablement symlink merely to suppress the warning; doing so without confirming the distribution’s intended boot behavior could change how the service starts.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →If the start command failed
Treat the runtime failure as a separate problem. Read systemctl status mdmonitor.service, inspect the journal for the service’s error, and follow the message from mdadm. A Garuda Linux community discussion reports mdadm output saying “No mail address or alert command – not monitoring.” That example shows that alerting configuration can be a distinct issue; it does not establish that every mdmonitor setup requires a mail address.
If you deliberately create links manually
The systemd manual documents enablement through links based on [Install] metadata and notes that administrators can create links manually. Manual links are not a substitute for confirming the unit’s intended activation model; after changing unit configuration or links, reload systemd’s configuration as appropriate.
Quick Recap
Best Value
- New
- Mint Condition
- Dispatch same day for order received before 12 noon
- Guaranteed packaging
- No quibbles returns
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
