Welcome to the Linux Foundation Forum!

[mdmonitor] The unit files have no installation config

In chapter Raid p.4, the command sudo systemctl start mdmonitor goes well but then sudo systemctl enable mdmonitor returns:

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.

Did anything go wrong? The /etc/mdadm.conf file has:

  1. ARRAY /dev/md0 metadata=1.2 name=ip-a-b-c-d:0 UUID=c0e6f53c:4df9342f:bbbc4aca:dc47709e
  2. MAILADDR my@email.com

Comments

  • Also, the Raid disks are two losetup partitions, maybe there's a link

  • Posts: 916

    in general if you do systemctl enable foo.service you will get an error like Failed to enable unit: Unit file foo.service does not exist. Like wise with systemctl start foo.service. So I doubt anything went wrong

    If you have something which is not really a systemctl thing (like vmware) it defaults back to a system V service and tells you it did as well.

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training