Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#40965 - [mdadm] Redundant mdadm.service file

Attached to Project: Arch Linux
Opened by Sander Jansen (GogglesGuy) - Tuesday, 24 June 2014, 16:32 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Tuesday, 19 May 2015, 15:18 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 9
Private No


The arch package of mdadm-3.3.1-2 adds a mdadm.service file for systemd. This seems to be redundant since mdadm already contains a mdmonitor.service file which is automatically actived by the included udev rule and does the same thing (--monitor --scan) as mdadm.service.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Tuesday, 19 May 2015, 15:18 GMT
Reason for closing:  Fixed
Comment by Dan Ziemba (zman0900) - Sunday, 15 February 2015, 08:04 GMT
This is still a problem. mdmonitor.service seems to have been enabled automatically whenever that became part of the package, and since I had mdadm.service enabled previously I now get errors from it on boot:

$ systemctl status mdadm mdmonitor
● mdadm.service - MDADM Event Monitor
Loaded: loaded (/usr/lib/systemd/system/mdadm.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2015-02-15 02:52:58 EST; 10min ago
Process: 402 ExecStart=/usr/bin/mdadm --monitor --scan (code=exited, status=1/FAILURE)
Main PID: 402 (code=exited, status=1/FAILURE)

Feb 15 02:52:58 nas mdadm[402]: mdadm: Only one autorebuild process allowed in scan mode, aborting
Feb 15 02:52:58 nas systemd[1]: mdadm.service: main process exited, code=exited, status=1/FAILURE
Feb 15 02:52:58 nas systemd[1]: Unit mdadm.service entered failed state.
Feb 15 02:52:58 nas systemd[1]: mdadm.service failed.

● mdmonitor.service - MD array monitor
Loaded: loaded (/usr/lib/systemd/system/mdmonitor.service; static; vendor preset: disabled)
Active: active (running) since Sun 2015-02-15 02:52:56 EST; 10min ago
Process: 299 ExecStartPre=/usr/lib/systemd/scripts/ (code=exited, status=203/EXEC)
Main PID: 303 (mdadm)
CGroup: /system.slice/mdmonitor.service
└─303 /sbin/mdadm --monitor --scan
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 11 May 2015, 19:41 GMT
@tpowa let's get this fixed quickly. It's annoying. I can do it if you like.