Comment 27 for bug 1852747

I enabled -proposed and installed the package:

# dpkg -l mdadm | grep mdadm
ii mdadm 4.1-5ubuntu1.1 amd64 tool to administer Linux MD arrays (software RAID)

# dpkg -L mdadm | grep -i mdcheck
/lib/systemd/system/mdcheck_continue.service
/lib/systemd/system/mdcheck_continue.timer
/lib/systemd/system/mdcheck_start.service
/lib/systemd/system/mdcheck_start.timer
/usr/share/mdadm/mdcheck

# ls -altr /usr/share/mdadm/mdcheck
-rwxr-xr-x 1 root root 3884 Sep 24 18:54 /usr/share/mdadm/mdcheck

Original bug is fixed now.

But I see another problem with systemd files - mdcheck_continue.timer is misconfigured and will never be started:

# systemctl status mdcheck_continue.timer
● mdcheck_continue.timer - MD array scrubbing - continuation
     Loaded: loaded (/lib/systemd/system/mdcheck_continue.timer; static; vendor preset: enabled)
     Active: inactive (dead)
    Trigger: n/a
   Triggers: ● mdcheck_continue.service

# systemctl enable mdcheck_continue.timer
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.

Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

I suppose, that I need to create another bug.