New server, 2 1T drives in RAID1, with mdraid, I have an error during boot for
mdmonitor:

Jun 05 17:12:47 valhalla systemd[454]: mdmonitor.service: Failed at step EXEC
spawning /usr/lib/systemd/scripts/mdadm_env.sh: No such file or directory

I've run into this before with mdadm, last time was due to not having MAILADDR
configured in /etc/mdadm.conf (that is not the case now)

# cat /etc/mdadm.conf
DEVICE partitions
ARRAY /dev/md0 metadata=1.2 name=archiso:0 
UUID=1b67f2d4:4911f2c5:469f9dcf:315814ce
ARRAY /dev/md1 metadata=1.2 name=archiso:1 
UUID=0542c5c9:3802b256:32e97884:a2e49f53
ARRAY /dev/md2 metadata=1.2 name=archiso:2 
UUID=812e8f85:0c4efbef:a0c02f49:215df35e
ARRAY /dev/md3 metadata=1.2 name=archiso:3 
UUID=80a3bf76:e6421b06:6edb2a88:741e8b6f
MAILADDR da...@mydomain.com
PROGRAM /usr/sbin/handle-mdadm-events

The problem very simply looks to be no /usr/lib/systemd/scripts/mdadm_env.sh
wanted by mdmonitor.service, e.g.

# cat /usr/lib/systemd/system/mdmonitor.service

#  This file is part of mdadm.
#
#  mdadm is free software; you can redistribute it and/or modify it
#  under the terms of the GNU General Public License as published by
#  the Free Software Foundation; either version 2 of the License, or
#  (at your option) any later version.

[Unit]
Description=MD array monitor
DefaultDependencies=no

[Service]
Environment=  MDADM_MONITOR_ARGS=--scan
EnvironmentFile=-/run/sysconfig/mdadm
ExecStartPre=-/usr/lib/systemd/scripts/mdadm_env.sh
ExecStart=/sbin/mdadm --monitor $MDADM_MONITOR_ARGS

There is no /usr/lib/systemd/scripts/mdadm_env.sh in the current mdadm package.
Is this a bug (which I'm happy to file), or me being stupid? (go easy if the 
latter)

-- 
David C. Rankin, J.D.,P.E.

Reply via email to