FS#41718 - [mdadm] mdmonitor.service fails
Attached to Project:
Arch Linux
Opened by Soup (Soup) - Wednesday, 27 August 2014, 15:34 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 09 July 2016, 12:11 GMT
Opened by Soup (Soup) - Wednesday, 27 August 2014, 15:34 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 09 July 2016, 12:11 GMT
|
Details
Description: mdmonitor.service fails
Aug 27 17:13:14 host systemd[325]: Failed at step EXEC spawning /usr/lib/systemd/scripts/mdadm_env.sh: No such file or directory Aug 27 17:13:16 host mdadm[456]: mdadm: Only one autorebuild process allowed in scan mode, aborting Aug 27 17:13:17 host systemd[1]: mdadm.service: main process exited, code=exited, status=1/FAILURE Aug 27 17:13:17 host systemd[1]: Unit mdadm.service entered failed state. pacman -Q mdadm systemd mdadm 3.3.1-2 systemd 216-1 systemctl list-unit-files|grep "md[am]" mdadm-last-resort@.service static mdadm.service enabled mdmon@.service static mdmonitor.service static mdadm-last-resort@.timer static grep -r mdadm_env.sh /usr/lib/systemd/ /usr/lib/systemd/system/mdmonitor.service:ExecStartPre=-/usr/lib/systemd/scripts/mdadm_env.sh |
This task depends upon
Comment by Samantha McVey (samcv) -
Thursday, 09 June 2016, 10:02 GMT
Comment by Samantha McVey (samcv) -
Saturday, 09 July 2016, 11:09 GMT
I tested this with systemd 230-4 and mdadm 3.4-1 and did not
receive any failed status and the process started successfully.
Can the original bug reporter please reply back and report if this
is still an issue?
No response in the last month, this should be closed.